Hi Luis, Great thanks for your comments. Please see my answers inline.
Thanks, Jensen On Tue, Apr 4, 2023 at 3:39 AM LUIS MIGUEL CONTRERAS MURILLO < luismiguel.contrerasmuri...@telefonica.com> wrote: > Hi all, > > > > My apologies for answering late to this WGLC. > > > > I do support the progress of this document. > > > > I have some few comments: > > - Figure 1: it is not clear the direction of the arrows, specially > where “report” is written, probably missing some “+” symbol. Please, review > and clarify if needed. > > That is a very good point. We will add a paragraph to explain every potential interaction (arrow) in the figure. Hopefully, this will be helpful. > - Stats parameters of ALTO. There are some global stat values, but > there is no reference for the time in which those values have been > collected (the total time in which the ALTO server is being up and > running). Note that for the “last-stats” the time reference is 5 min, but > for the absolute stats there is no time reference. > > Good catch. I believe it is related to these two GitHub issues that we are working on: - https://github.com/ietf-wg-alto/draft-ietf-alto-oam-yang/issues/19 - https://github.com/ietf-wg-alto/draft-ietf-alto-oam-yang/issues/25 We will add the time reference of each stat value in the next revision. > - Question. Regarding the number of PIDs I understand it is possible > to retrieve the total number of PIDs in ALTO. Not sure if it would be > meaningful to have the number of PIDs for filtered maps. Not sure if this > can be relevant, maybe yes. > > Yes, the filtered maps should not provide the number of PIDs. Right now, the filtered maps are coupled with their dependent full maps. So the number of PIDs is actually for the full map. We will clarify this in the node description. > > > Thanks so much and apologies again for the time taken in answering (IETF > absorbed most of my time before and during IETF week). > > > > Best regards > > > > Luis > > > > *De:* alto <alto-boun...@ietf.org> *En nombre de * > mohamed.boucad...@orange.com > *Enviado el:* martes, 21 de marzo de 2023 15:30 > *Para:* alto@ietf.org; draft-ietf-alto-oam-y...@ietf.org > *CC:* alto-cha...@ietf.org > *Asunto:* Re: [alto] WGLC for draft-ietf-alto-oam-yang (Ends 26/03/2023) > > > > Hi all, > > > > This is a gentle reminder that this WGLC is still running. > > > > Silence does not mean that the document is in good shape. So, please > review and share your comments. If you are happy with the current version, > that’s also a good feedback we would like to hear. > > > > FWIW, there are: > > > > - 5 Closed WGLC PRs: > > https://github.com/ietf-wg-alto/draft-ietf-alto-oam-yang/pulls?q=is%3Apr+is%3Aclosed+label%3AWGLC > - 2 Closed WGLC Issues: > > https://github.com/ietf-wg-alto/draft-ietf-alto-oam-yang/issues?q=is%3Aissue+is%3Aclosed+label%3AWGLC > - 9 Open WGLC Issues: > > https://github.com/ietf-wg-alto/draft-ietf-alto-oam-yang/issues?q=is%3Aissue+is%3Aopen+label%3AWGLC > > > > Thank you. > > > > Cheers, > > Qin & Med > > > > *De :* BOUCADAIR Mohamed INNOV/NET > *Envoyé :* dimanche 12 mars 2023 19:42 > *À :* 'alto@ietf.org' <alto@ietf.org>; 'draft-ietf-alto-oam-y...@ietf.org' > <draft-ietf-alto-oam-y...@ietf.org> > *Cc :* 'alto-cha...@ietf.org' <alto-cha...@ietf.org> > *Objet :* RE: WGLC for draft-ietf-alto-oam-yang (Ends 26/03/2023) > > > > Re-, > > > > FWIW, issues/PRs may be also raised using the github repo. Please use > “WGLC” label when entering your items. > > > > The current active WGLC comments can be seen at: > https://github.com/ietf-wg-alto/draft-ietf-alto-oam-yang/issues?q=is%3Aissue+is%3Aopen+label%3AWGLC > > > > Cheers, > > Med > > > > *De :* BOUCADAIR Mohamed INNOV/NET > *Envoyé :* dimanche 12 mars 2023 19:23 > *À :* alto@ietf.org; 'draft-ietf-alto-oam-y...@ietf.org' < > draft-ietf-alto-oam-y...@ietf.org> > *Cc :* alto-cha...@ietf.org > *Objet :* WGLC for draft-ietf-alto-oam-yang (Ends 26/03/2023) > > > > Hi all, > > > > This message starts the WGLC for > https://datatracker.ietf.org/doc/html/draft-ietf-alto-oam-yang-06. The > call ends: 26/03/2023. > > > > Please review and indicate your support or objection to proceed with the > publication of this document. > > > > Thank you. > > > > Cheers, > > Qin & Med > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete > this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > > Thank you. > > > ------------------------------ > > Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, > puede contener información privilegiada o confidencial y es para uso > exclusivo de la persona o entidad de destino. Si no es usted. el > destinatario indicado, queda notificado de que la lectura, utilización, > divulgación y/o copia sin autorización puede estar prohibida en virtud de > la legislación vigente. Si ha recibido este mensaje por error, le rogamos > que nos lo comunique inmediatamente por esta misma vía y proceda a su > destrucción. > > The information contained in this transmission is confidential and > privileged information intended only for the use of the individual or > entity named above. If the reader of this message is not the intended > recipient, you are hereby notified that any dissemination, distribution or > copying of this communication is strictly prohibited. If you have received > this transmission in error, do not read it. Please immediately reply to the > sender that you have received this communication in error and then delete > it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, > pode conter informação privilegiada ou confidencial e é para uso exclusivo > da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário > indicado, fica notificado de que a leitura, utilização, divulgação e/ou > cópia sem autorização pode estar proibida em virtude da legislação vigente. > Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique > imediatamente por esta mesma via e proceda a sua destruição >
_______________________________________________ alto mailing list alto@ietf.org https://www.ietf.org/mailman/listinfo/alto
