Roman Danyliw has entered the following ballot position for draft-ietf-pce-pcep-extension-native-ip-34: Discuss
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-pce-pcep-extension-native-ip/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- ** Section 14.2. 14.2. PCECC-CAPABILITY sub-TLV's Flag field [RFC9050] created a sub-registry within the "Path Computation Element Protocol (PCEP) Numbers" registry to manage the value of the PCECC- CAPABILITY sub-TLV's 32-bit Flag field. IANA is requested to allocate a new bit position within this registry, as follows: The registration policy of PCECC-CAPABILITY sub-TLV (https://www.iana.org/assignments/pcep/pcep.xhtml#pcecc-capability) is “Standards Action”. This document has experimental status and does not qualify for registration. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you to Mallory Knodel for the GENART review. ** This document has been submitted with “experimental” status. What is the nature of the experiment in question here? _______________________________________________ Pce mailing list -- pce@ietf.org To unsubscribe send an email to pce-le...@ietf.org
