Hi, This early allocation for draft-ietf-pce-sr-bidir-path has been completed!
Thanks! Dhruv & Julien ---------- Forwarded message --------- From: Amanda Baber via RT <[email protected]> Date: Fri, Dec 1, 2023 at 3:03 AM Subject: [IANA #1290605] Early Code Point Allocation for draft-ietf-pce-sr-bidir-path To: <[email protected]> Cc: <[email protected]>, <[email protected]>, < [email protected]>, <[email protected]>, <[email protected]>, < [email protected]>, <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]>, <[email protected]> Hi all, We've made the following early allocation in the ASSOCIATION Type Field registry: Type: 8 Name: Double-Sided Bidirectional with Reverse LSP Association (TEMPORARY - registered 2023-11-30, expires 2024-11-30) Reference: [draft-ietf-pce-sr-bidir-path-12] Please see https://www.iana.org/assignments/pcep If the document hasn't been approved for publication by October, we'll contact the chairs and AD about approving an extension. Also, authors: could you make the following terminology change in the IANA Considerations section? OLD: the "ASSOCIATION Type Field" subregistry [RFC8697] within the "Path Computation Element Protocol (PCEP) Numbers" registry NEW: the "ASSOCIATION Type Field" registry [RFC8697] within the "Path Computation Element Protocol (PCEP) Numbers" registry group thanks, Amanda Baber IANA Operations Manager On Thu Nov 30 14:16:49 2023, [email protected] wrote: > Hi IANA, > > Following the procedure for early allocation as per RFC 7120, we would > like to request early allocation for the following code point defined > in > https://www.ietf.org/archive/id/draft-ietf-pce-sr-bidir-path- > 12.html#name-association-type > > You can find below the AD's approval. > > Thank you, > > Dhruv & Julien, PCE WG co-chairs > > > -------- Forwarded Message -------- > Date: Mon, 13 Nov 2023 11:47:58 +0000 > From: John Scudder <[email protected]> > > > > Approved. > > —John > > > On Nov 9, 2023, at 11:31 AM, [email protected] wrote: > > > > > > [External Email. Be cautious of content] > > > > Hi John, > > > > The authors of draft-ietf-pce-sr-bidir-path have requested for the > > early allocation of the codepoint specified in: > > > > https://datatracker.ietf.org/doc/html/draft-ietf-pce-sr-bidir-path- > > 12#name-iana-considerations > > > > We polled the WG and there were no objections. According to the > > chairs’ review, the RFC 7120 criteria is met. > > As per the process in the RFC, we now request your approval before > > reaching out to the IANA for the early allocation. > > > > Thanks! > > > > Dhruv & Julien > > > > > > -------- Forwarded Message -------- > > Date: Thu, 9 Nov 2023 17:10:42 +0100 > > From: Julien Meuric <[email protected]> > > > > > > Hi all, > > > > No concerns have been expressed about this early allocation. We'll > > thus proceed to the next step. > > > > Thanks, > > > > Dhruv & Julien > > > > > > On 28/07/2023 15:58, Julien Meuric wrote: > >> Hi WG, > >> > >> We have received a request from the authors of > >> draft-ietf-pce-sr-bidir-path for an early code point allocation on > >> the association type referred to in > >> https://datatracker.ietf.org/doc/html/draft-ietf-pce-sr-bidir-path- > >> 11#name-iana-considerations > >> > >> RFC 7120 requires 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 Monday August 21st, we will kick > >> off the early allocation request. > >> > >> Thanks! > >> > >> Dhruv & Julien > >> > > > > ____________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > > confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous > > avez recu ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les > > messages electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, > > deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or > > privileged information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender > > and delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have > > been modified, changed or falsified. > > Thank you. > ____________________________________________________________________________________________________________ > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez > recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les > messages electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, > deforme ou falsifie. Merci. > > This message and its attachments may contain confidential or > privileged information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and > delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have > been modified, changed or falsified. > Thank you.
_______________________________________________ Pce mailing list [email protected] https://www.ietf.org/mailman/listinfo/pce
