Hi Dirk, Thank you for the review.
Good catches. Fixed them all in https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-tcpo-v6eh/06/. Cheers, Med > -----Message d'origine----- > De : Dirk Von Hugo via Datatracker <nore...@ietf.org> > Envoyé : samedi 13 janvier 2024 18:01 > À : int-...@ietf.org > Cc : draft-ietf-opsawg-ipfix-tcpo-v6eh....@ietf.org; > opsawg@ietf.org > Objet : Intdir early review of draft-ietf-opsawg-ipfix-tcpo-v6eh- > 05 > > Reviewer: Dirk Von Hugo > Review result: Ready with Nits > > Hello, > I am an assigned INT directorate reviewer for draft-ietf-opsawg- > ipfix-tcpo-v6eh. These comments were written primarily for the > benefit of the Internet Area Directors. Document editors and > shepherd(s) should treat these comments just like they would > treat comments from any other IETF contributors and resolve them > along with any other Last Call comments that have been received. > For more details on the INT Directorate, see > <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F% > 2Fdatatracker.ietf.org%2Fgroup%2Fintdir%2Fabout%2F&data=05%7C02%7 > Cmohamed.boucadair%40orange.com%7C818705eb97284073dff308dc14592b4 > 9%7C90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638407620411748177 > %7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB > TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=aFw9qowQ89HdxibD > TCB0X164wIDYxZ9%2BSBtCSOzOBaQ%3D&reserved=0> Based on my review, > if I was on the IESG I would ballot this document as NO > OBJECTION. > > Although not being an expert on OPSAWG I agrre that the document > is helpful forhandling IPv6 extension headers and TCP options. I > agree with prior reviewers that IPFIX RFCs should be referenced > already in sect. 1 as well as maybe the corresponding draft > draft-ietf-opsawg-ipfix-fixes on further details on the described > issues, if I understood it correctly. In addition the following > very minor nits should be corrected: > > p.3: > Cover the full extension headers range => Cover the full > extension headers' > range which do no correspond => which do not correspond > > p.4: > these limitations can't be addressed these limitations cannot be > addressed > > p.5: > packet of this Flow contained the respective => packet of this > Flow contains the respective > > p.8: > these limitations can't be addressed => these limitations cannot > be addressed > > p.10: > that it does no support, => that it does not support, > > p.12: > Let's consider a TCP Flow => Let us consider a TCP Flow > > Thanks and best regards > Dirk > ____________________________________________________________________________________________________________ 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
