Re: [Pce] Early code point allocation for draft-ietf-pce-segment-routing-policy-cp-12

[Dhruv Dhody <[e-mail]>]

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 <[e-mail]> 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
>