Hi Dhruv, Sure, I’ll take note and update in -14 version.
Thanks, Mike. From: Dhruv Dhody <d...@dhruvdhody.com> Sent: Wednesday, January 24, 2024 12:59 AM To: Mike Koldychev (mkoldych) <mkold...@cisco.com> Cc: draft-ietf-pce-segment-routing-policy...@ietf.org; pce@ietf.org Subject: Fwd: Early code point allocation for draft-ietf-pce-segment-routing-policy-cp-12 Hi Mike, https://www.ietf.org/archive/id/draft-ietf-pce-segment-routing-policy-cp-13.html#section-6.2 Can the TBD4 SR-POLICY-CAPABILITY be changed to SRPOLICY-CAPABILITY to match the naming style for other TLVs? Thanks! Dhruv ---------- Forwarded message --------- From: Dhruv Dhody <d...@dhruvdhody.com<mailto:d...@dhruvdhody.com>> Date: Wed, Jan 24, 2024 at 11:21 AM Subject: Re: Early code point allocation for draft-ietf-pce-segment-routing-policy-cp-12 To: <pce@ietf.org<mailto:pce@ietf.org>> Cc: <draft-ietf-pce-segment-routing-policy...@ietf.org<mailto:draft-ietf-pce-segment-routing-policy...@ietf.org>>, pce-chairs <pce-cha...@ietf.org<mailto:pce-cha...@ietf.org>> Hi WG, We received no objections and thus will be going ahead with the early allocation process. Thanks! Dhruv & Julien On Wed, Jan 10, 2024 at 6:53 PM Dhruv Dhody <d...@dhruvdhody.com<mailto:d...@dhruvdhody.com>> wrote: Hi WG, We have received a request from the authors of draft-ietf-pce-segment-routing-policy-cp for an early code point allocation for the codepoints listed in - https://www.ietf.org/archive/id/draft-ietf-pce-segment-routing-policy-cp-12.html#section-6.2 (TBD1-4) https://www.ietf.org/archive/id/draft-ietf-pce-segment-routing-policy-cp-12.html#section-6.3 (TBD6-8) https://www.ietf.org/archive/id/draft-ietf-pce-segment-routing-policy-cp-12.html#section-6.4 (TBD9) Note that there was an earlier allocation request where some codepoints were already allocated by IANA - https://mailarchive.ietf.org/arch/msg/pce/8GtjtxNWeA9MxpySx6J7XZKmlUc/ Note that the draft is also undergoing a parallel WGLC - https://mailarchive.ietf.org/arch/msg/pce/ert_k7k5iYq3LWbaTc-aMwRRAbs/ RFC 7120 requires one to meet the following criteria to proceed: b. The format, semantics, processing, and other rules related to handling the protocol entities defined by the code points (henceforth called "specifications") must be adequately described in an Internet-Draft. c. The specifications of these code points must be stable; i.e., if there is a change, implementations based on the earlier and later specifications must be seamlessly interoperable. If anyone believes that the draft does not meet these criteria or believes that early allocation is not appropriate for any other reason, please send an email to the PCE mailing list explaining why. If the chairs hear no objections by Wednesday, Jan 24th, we will kick off the early allocation request. Thanks! Dhruv & Julien
_______________________________________________ Pce mailing list Pce@ietf.org https://www.ietf.org/mailman/listinfo/pce
