Hi! From: John Scudder <j...@juniper.net> Sent: Wednesday, August 21, 2024 8:37 PM To: Dhruv Dhody <d...@dhruvdhody.com>; Roman Danyliw <r...@cert.org> Cc: The IESG <i...@ietf.org>; draft-ietf-pce-pcep-extension-native...@ietf.org; pce-chairs <pce-cha...@ietf.org>; pce@ietf.org Subject: Re: [Pce] Roman Danyliw's Discuss on draft-ietf-pce-pcep-extension-native-ip-34: (with DISCUSS and COMMENT)
Warning: External Sender - do not click links or open attachments unless you recognize the sender and know the content is safe. Hi All, On Aug 20, 2024, at 3:21 PM, John Scudder <j...@juniper.net<mailto:j...@juniper.net>> wrote: To add to what Dhruv wrote, On Aug 20, 2024, at 1:16 PM, Dhruv Dhody <d...@dhruvdhody.com<mailto: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. It subsequently occurred to me that if draft-ietf-pce-pcep-extension-native-ip adds a normative reference to draft-ietf-pce-iana-update then we should be all set — draft-ietf-pce-pcep-extension-native-ip can enter the RFC Editor's queue and they can start work on it, but those concerned about the registration policy issue can rest assured that it won’t be issued as an RFC until draft-ietf-pce-iana-update is also published (it’ll be a cluster, because of the normative ref). Q.E.D., the problem will be resolved by or before the time the RFC is issued. Work for everyone? [Roman] Yes. That works for me. Roman
_______________________________________________ Pce mailing list -- pce@ietf.org To unsubscribe send an email to pce-le...@ietf.org
