To add to what Dhruv wrote, On Aug 20, 2024, at 1:16 PM, Dhruv Dhody <d...@dhruvdhody.com> wrote:
---------------------------------------------------------------------- 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<https://urldefense.com/v3/__https://www.iana.org/assignments/pcep/pcep.xhtml*pcecc-capability__;Iw!!NEt6yMaO-gk!B5PLFQZKBPmXYlwyMLc8dKsZAHy4c44OJGkxvAvngU6q_uyvvDK6tLmHr5iCB7dAiMekXL_kprM$>) is “Standards Action”. This document has experimental status and does not qualify for registration. Dhruv: We have a document in the PCE WG to fix it - https://datatracker.ietf.org/doc/draft-ietf-pce-iana-update/<https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-pce-iana-update/__;!!NEt6yMaO-gk!B5PLFQZKBPmXYlwyMLc8dKsZAHy4c44OJGkxvAvngU6q_uyvvDK6tLmHr5iCB7dAiMekFueWoGw$> The document is being fast tracked by the WG. Note that this code point has already been allocated through the temporary allocation process and doesn’t expire until 2025-08-14. I anticipate that draft-ietf-pce-iana-update will have been progressed well before then, at which point the code point can be made permanent. —John
_______________________________________________ Pce mailing list -- pce@ietf.org To unsubscribe send an email to pce-le...@ietf.org
