Hi Behcet, Thank you for the review.
Please see inline. Cheers, Med > -----Message d'origine----- > De : Behcet Sarikaya via Datatracker <[email protected]> > Envoyé : lundi 8 janvier 2024 18:13 > À : [email protected] > Cc : [email protected]; [email protected]; > [email protected] > Objet : Genart early review of draft-ietf-opsawg-ipfix-fixes-03 > > Reviewer: Behcet Sarikaya > Review result: Almost Ready > > I am the assigned Gen-ART reviewer for this draft for an early > review. The General Area Review Team (Gen-ART) reviews all IETF > documents being processed by the IESG for the IETF Chair. Please > treat these comments just like any other last call comments. > > For more information, please see the FAQ at > > <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F% > 2Fwiki.ietf.org%2Fen%2Fgroup%2Fgen%2FGenArtFAQ&data=05%7C02%7Cmoh > amed.boucadair%40orange.com%7C1a4a4647ce0747d945cf08dc106d0e52%7C > 90c7a20af34b40bfbc48b9253b6f5d20%7C0%7C0%7C638403307773898326%7CU > nknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6 > Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=rSEMoxVhDknJ7VjmP8Xj > OO%2FoH2v7e4bJRrMu3Tta8LE%3D&reserved=0>. > > Document:draft-ietf-opsawg-ipfix-fixes-03 > Reviewer:Behcet Sarikaya > Review Date:2024-01-08 > IETF LC End Date:NA > IESG Telechat date: (if known) > > Summary: > This document provides simple fixes to the IANA IP Flow > Information Export > (IPFIX) registry. It provides a summary of previous work on the > fixes. It updates to ensure a consistent structure when calling > an existing IANA registry and many other updates. Major issues: > > Minor issues: > > Nits/editorial comments: > In my view the history presented needs to mention that the origin > of this work is RFC 5101 which defines IPFIX protocol between > exporting process and collecting process and the accompanying RFC > 5102 defining IPFIX IEs. [Med] We are not mentioning 5102 because RFC7012 says the following: [IANA-IPFIX] is now the normative reference for IPFIX Information Elements. When [RFC5102] was published, it defined, in its Section 5, the initial contents of that registry. As a historical note, Information Elements (IEs) were organized into categories in [RFC5102] according to their semantics and their applicability; these categories were not carried forward into [IANA-IPFIX] as an organizing principle. The categories (with example IEs) were: Running an idnits on the draft shows > many issues. Here is one I want to emphasize: Section > 4.1.2 on updates to ipv6ExtensionHeaders Description has this > line: > 12, MOB 135 IPv6 mobility [RFC3775] [Med] This is actually what is currently in the registry. The OLD text is correct. > which needs to be updated with: > 12, MOB 135 IPv6 mobility [RFC6275] > > Also maybe all RFC references should be listed as idnits tool > indicates. > [Med] Noted. Fixed as appropriate. ____________________________________________________________________________________________________________ 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. _______________________________________________ Gen-art mailing list [email protected] https://www.ietf.org/mailman/listinfo/gen-art
