Re: [OPSAWG] Zaheduzzaman Sarker's No Objection on draft-ietf-opsawg-sap-14: (with COMMENT)
Super!! Thanks. //Zahed From: mohamed.boucad...@orange.com Sent: Wednesday, January 18, 2023 10:47:26 PM To: Zaheduzzaman Sarker ; The IESG Cc: draft-ietf-opsawg-...@ietf.org ; opsawg-cha...@ietf.org ; opsawg@ietf.org ; adr...@olddog.co.uk Subject: RE: Zaheduzzaman Sarker's No Objection on draft-ietf-opsawg-sap-14: (with COMMENT) Hi Zahed, Please see inline. Cheers, Med > -Message d'origine- > De : Zaheduzzaman Sarker via Datatracker > Envoyé : mercredi 18 janvier 2023 22:03 > À : The IESG > Cc : draft-ietf-opsawg-...@ietf.org; opsawg-cha...@ietf.org; > opsawg@ietf.org; adr...@olddog.co.uk; adr...@olddog.co.uk > Objet : Zaheduzzaman Sarker's No Objection on draft-ietf-opsawg- > sap-14: (with COMMENT) > > Zaheduzzaman Sarker has entered the following ballot position for > draft-ietf-opsawg-sap-14: No Objection > > When responding, please keep the subject line intact and reply to > all email addresses included in the To and CC lines. (Feel free to > cut this introductory paragraph, however.) > > > Please refer to > https://www.ietf.org/about/groups/iesg/statements/handling-ballot- > positions/ > for more information about how to handle DISCUSS and COMMENT > positions. > > > The document, along with other ballot positions, can be found > here: > https://datatracker.ietf.org/doc/draft-ietf-opsawg-sap/ > > > > -- > > COMMENT: > -- > > > Thanks for working on this specification. > > I must say, without the right context and knowledge about network > topology in > this context it is very hard to follow figure 3. A description of > the figure or > reference of the document one should read to understand the > topology would be a > great help. > [Med] Added this NEW text right after Figure 1: NEW: The reader may refer to Section 5 of [RFC4026] for an overview of the building blocks that are usually invoked when characterizing a network. _ 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. ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
Re: [OPSAWG] Zaheduzzaman Sarker's No Objection on draft-ietf-opsawg-sap-14: (with COMMENT)
Hi Zahed, Please see inline. Cheers, Med > -Message d'origine- > De : Zaheduzzaman Sarker via Datatracker > Envoyé : mercredi 18 janvier 2023 22:03 > À : The IESG > Cc : draft-ietf-opsawg-...@ietf.org; opsawg-cha...@ietf.org; > opsawg@ietf.org; adr...@olddog.co.uk; adr...@olddog.co.uk > Objet : Zaheduzzaman Sarker's No Objection on draft-ietf-opsawg- > sap-14: (with COMMENT) > > Zaheduzzaman Sarker has entered the following ballot position for > draft-ietf-opsawg-sap-14: No Objection > > When responding, please keep the subject line intact and reply to > all email addresses included in the To and CC lines. (Feel free to > cut this introductory paragraph, however.) > > > Please refer to > https://www.ietf.org/about/groups/iesg/statements/handling-ballot- > positions/ > for more information about how to handle DISCUSS and COMMENT > positions. > > > The document, along with other ballot positions, can be found > here: > https://datatracker.ietf.org/doc/draft-ietf-opsawg-sap/ > > > > -- > > COMMENT: > -- > > > Thanks for working on this specification. > > I must say, without the right context and knowledge about network > topology in > this context it is very hard to follow figure 3. A description of > the figure or > reference of the document one should read to understand the > topology would be a > great help. > [Med] Added this NEW text right after Figure 1: NEW: The reader may refer to Section 5 of [RFC4026] for an overview of the building blocks that are usually invoked when characterizing a network. _ 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. ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
[OPSAWG] Zaheduzzaman Sarker's No Objection on draft-ietf-opsawg-sap-14: (with COMMENT)
Zaheduzzaman Sarker has entered the following ballot position for draft-ietf-opsawg-sap-14: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-opsawg-sap/ -- COMMENT: -- Thanks for working on this specification. I must say, without the right context and knowledge about network topology in this context it is very hard to follow figure 3. A description of the figure or reference of the document one should read to understand the topology would be a great help. ___ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
