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.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-tcpo-v6eh/ ---------------------------------------------------------------------- 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.) _______________________________________________ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
