Hi Sandy, Paul, all, We've updated the registry to reflect the changes in the diff and fixed the typos, as noted by Paul (thank you for pointing these out):
https://www.iana.org/assignments/ipfix Let us know if any other changes are needed. Thanks, Sabrina On Wed Feb 19 19:48:34 2025, sgin...@staff.rfc-editor.org wrote: > Hi Paul, Sabrina, Authors, > > I removed the two instances of '(previously the "X" registry)’. I > also changed the citation tags for [RFC768] and [RFC791] (removed the > leading zeros). > > > > Also, RFC9710 is not listed in the "Reference" column for any of the > > changes. Whether that's an oversight in the RFC, or an expectation > > that IANA will automatically add it; I believe it should be listed > > against each modified element. > > Rather than add a reference for each entry, I added a statement in > section 9. Please review and let us know if this addresses your > concern. Thank you for pointing out - we missed adding mention of > this change. > > The current files are here: > https://www.rfc-editor.org/authors/rfc9710.xml > https://www.rfc-editor.org/authors/rfc9710.txt > https://www.rfc-editor.org/authors/rfc9710.pdf > https://www.rfc-editor.org/authors/rfc9710.html > > Diffs highlighting only the updates described above: > https://www.rfc-editor.org/authors/rfc9710-lastdiff.html > https://www.rfc-editor.org/authors/rfc9710-lastrfcdiff.html (side by > side) > > AUTH48 diffs: > https://www.rfc-editor.org/authors/rfc9710-auth48diff.html > https://www.rfc-editor.org/authors/rfc9710-auth48rfcdiff.html (side > by side) > > Comprehensive diffs: > https://www.rfc-editor.org/authors/rfc9710-diff.html > https://www.rfc-editor.org/authors/rfc9710-rfcdiff.html (side by > side) > > > Please review and let us know if any further updates are needed. > > Thank you, > RFC Editor/sg > > > > > On Feb 19, 2025, at 6:56 AM, Aitken, Paul <pait...@ciena.com> wrote: > > > > Sabrina, there are still some discrepancies between the RFC-to-be and > > the registry. I've checked sections 4, 5, and 7 of the RFC-to-be, but > > not yet section 6. > > > > Also, RFC9710 is not listed in the "Reference" column for any of the > > changes. Whether that's an oversight in the RFC, or an expectation > > that IANA will automatically add it; I believe it should be listed > > against each modified element. > > > > > > 4.1.2. NEW / sourceTransportPort > > 4.2.2. NEW / destinationTransportPort > > 4.4.2. NEW / collectorTransportPort > > 4.5.2. NEW / exporterTransportPort > > The RFC says "See [RFC0768]" while the registry says "See [RFC768]". > > > > 262 messageMD5Checksum > > > > "messageScope Information lement" should be "messageScope Information > > Element" > > > > 285 anonymizationFlags > > > > The text is correct, but the right-hand edge of the table is wonky. > > > > 340 informationElementDescription > > > > "with its ownlanguage tag" should be "with its own language tag". > > > > > > P. -- auth48archive mailing list -- auth48archive@rfc-editor.org To unsubscribe send an email to auth48archive-le...@rfc-editor.org
