A new Request for Comments is now available in online RFC libraries.

        
        RFC 9756

        Title:      Update to the IANA Path Communication Element 
                    Protocol (PCEP) Numbers Registration Procedures 
                    and the Allowance of Experimental Error Codes 
        Author:     D. Dhody,
                    A. Farrel
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2025
        Mailbox:    dhruv.i...@gmail.com,
                    adr...@olddog.co.uk
        Pages:      11
        Updates:    RFC 5440, RFC 8231, RFC 8233, RFC 8281, 
                    RFC 8623, RFC 8664, RFC 8685, RFC 8697, 
                    RFC 8733, RFC 8745, RFC 8779, RFC 8780, 
                    RFC 8800, RFC 8934, RFC 9050, RFC 9059, 
                    RFC 9168, RFC 9357, RFC 9504, RFC 9603, 
                    RFC 9604
        I-D Tag:    draft-ietf-pce-iana-update-03.txt

        URL:        https://www.rfc-editor.org/info/rfc9756

        DOI:        10.17487/RFC9756

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

Designating "experimental use" sub-ranges within codepoint 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.

This document is a product of the Path Computation Element Working Group of the 
IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-edi...@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team

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

Reply via email to