Dear Med, Many thanks for the comprehensive review. Much appreciated. We merged all your input to the upcoming -01 release. https://raw.githubusercontent.com/graf3net/draft-tgraf-opsawg-ipfix-srv6-srh/main/draft-ietf-opsawg-ipfix-srv6-srh-01.txt
The diff to the current -00 version can be found here: https://www.ietf.org/rfcdiff?url1=https://www.ietf.org/archive/id/draft-ietf-opsawg-ipfix-srv6-srh-00.txt&url2=https://raw.githubusercontent.com/graf3net/draft-tgraf-opsawg-ipfix-srv6-srh/main/draft-ietf-opsawg-ipfix-srv6-srh-01.txt For some we need further clarifications if we addressed them correctly. I would appreciate if you could clarify the following three points: Med> Section 2, remark: "Why do we need three IE, srhSegmentIPv6ListSection, srhSegmentIPv6BasicList and srhSectionIPv6, to expose SRH Segment List Thomas> Section 5.1 should provide the answer. If that should not be sufficient, please suggest how this could be better expressed. Med> Section 2: remark: "as series of n octets" is not clearly comprehensible. Thomas> Extended to "as series of n octets in IPFIX". Does that makes it clearer? Med> Section 4.11, remark: "Do you really need to define a new registry here?" Thomas> The registry could potentially be used (and updated) by non IPFIX people. Best wishes Thomas From: OPSAWG <opsawg-boun...@ietf.org> On Behalf Of mohamed.boucad...@orange.com Sent: Tuesday, September 6, 2022 10:19 AM To: Joe Clarke (jclarke) <jclarke=40cisco....@dmarc.ietf.org>; opsawg@ietf.org Subject: Re: [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh Hi all, I support. FWIW, the authors may found some quick comments at: * pdf: https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-tgraf-opsawg-ipfix-srv6-srh-05-rev%20Med.pdf<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fboucadair%2FIETF-Drafts-Reviews%2Fraw%2Fmaster%2Fdraft-tgraf-opsawg-ipfix-srv6-srh-05-rev%2520Med.pdf&data=05%7C01%7CThomas.Graf%40swisscom.com%7C9b7f1961451f468f5ed208da8fe08358%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637980491680499647%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GmDWAcd71AYy6N%2BWx5469KaEjcmDCLJ%2FDsVv3LINv88%3D&reserved=0> * doc: https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-tgraf-opsawg-ipfix-srv6-srh-05-rev%20Med.doc<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fboucadair%2FIETF-Drafts-Reviews%2Fraw%2Fmaster%2Fdraft-tgraf-opsawg-ipfix-srv6-srh-05-rev%2520Med.doc&data=05%7C01%7CThomas.Graf%40swisscom.com%7C9b7f1961451f468f5ed208da8fe08358%7C364e5b87c1c7420d9beec35d19b557a1%7C0%7C0%7C637980491680499647%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RCDJoUkBTJ%2Fooe%2BvJEOTagdDY64LIVvfrH4RhyBsAKI%3D&reserved=0> Cheers, Med De : OPSAWG <opsawg-boun...@ietf.org<mailto:opsawg-boun...@ietf.org>> De la part de Joe Clarke (jclarke) Envoyé : jeudi 18 août 2022 22:14 À : opsawg@ietf.org<mailto:opsawg@ietf.org> Objet : [OPSAWG] CALL FOR ADOPTION: draft-tgraf-opsawg-ipfix-srv6-srh Hello, WG. We'd like to begin a two week call for adoption of this work. Even as an individual draft it has already received some reviews and has iterated quite a bit. Based on IETF 114 there does seem to be interest in adopting this in opsawg, but we need a formal adoption poll. Please review and provide your adoption thoughts no later than September 1, 2022. Thanks. Joe _________________________________________________________________________________________________________________________ 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.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
