File formats:

Also available: XML file for editing

 

Status:

PROPOSED STANDARD

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

Authors:

D. Dhody
A. Farrel

Stream:

IETF

Source:

pce (rtg)

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC9756

Discuss this RFC: Send questions or comments to the mailing list pce@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 9756

Abstract

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.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.