Hi John, That's a fair observation.
The reason why no "update" was added to 5102 is that rfc7012#section-5 (which obsoletes 5102) 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. Cheers, Med > -----Message d'origine----- > De : John Scudder via Datatracker <nore...@ietf.org> > Envoyé : mardi 9 juillet 2024 23:05 > À : The IESG <i...@ietf.org> > Cc : draft-ietf-opsawg-ipfix-tcpo-v...@ietf.org; opsawg- > cha...@ietf.org; opsawg@ietf.org; thomas.g...@swisscom.com; > thomas.g...@swisscom.com > Objet : John Scudder's No Objection on draft-ietf-opsawg-ipfix- > tcpo-v6eh-17: (with COMMENT) > > > John Scudder has entered the following ballot position for > draft-ietf-opsawg-ipfix-tcpo-v6eh-17: 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.) > > > > ----------------------------------------------------------------- > COMMENT: > ----------------------------------------------------------------- > > Thanks for this document. I have one suggestion -- even though > the update to > the IANA registry is sufficient to deprecate ipv6ExtensionHeaders > and > tcpOptions, it seems to me it would be a courtesy to future users > of RFC 5102 > if you also used the Updates: header to indicate that 5102 is > updated to > deprecate these elements, instead of requiring them to discover > this (perhaps > late in their journey) by examining the registry. > > (Now that I look at this a little harder, I see that although the > registry > points to 5102, that RFC is obsoleted by 7012, so the chain of > pointers is > already messy. It would still be nice to use Updates: but > presumably pointing > to 7012... and I wonder if the registry should be updated to > reference 5102 > throughout, the note at the top of it notwithstanding. But that > is a problem > for another day.) > > ____________________________________________________________________________________________________________ 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 To unsubscribe send an email to opsawg-le...@ietf.org
