The IESG has received a request from the Path Computation Element WG (pce) to
consider the following document: - 'Update to the IANA PCE Communication
Protocol (PCEP) Registration
   Procedures and Allowing Experimental Error Codes'
  <draft-ietf-pce-iana-update-02.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-c...@ietf.org mailing lists by 2024-11-01. Exceptionally, comments may
be sent to i...@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This document updates the registration procedure within the IANA
   "Path Computation Element Protocol (PCEP) Numbers" group of
   registries.  This specification changes some of the registries with
   Standards Action to IETF Review as defined in RFC 8126.  This memo
   updates RFCs 8231, 8233, 8281, 8623, 8664, 8685, 8697, 8733, 8745,
   8779, 8780, 8800, 8934, 9050, 9059, 9168, 9357, 9504, 9603, and 9604
   for the same.

   Designating "experimental use" sub-ranges within code point
   registries is often beneficial for protocol experimentation in
   controlled environments.  Although the registries for PCEP messages,
   objects, and TLV types have sub-ranges assigned for Experimental Use,
   the registry for PCEP Error-Types and Error-values currently does
   not.  This document updates RFC 5440 by designating a specific range
   of PCEP Error-Types for Experimental Use.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-pce-iana-update/



No IPR declarations have been submitted directly on this I-D.





_______________________________________________
Pce mailing list -- pce@ietf.org
To unsubscribe send an email to pce-le...@ietf.org

Reply via email to