rfc9756v1.txt   rfc9756.txt 
Internet Engineering Task Force (IETF) D. Dhody Internet Engineering Task Force (IETF) D. Dhody
Request for Comments: 9756 Huawei Request for Comments: 9756 Huawei
Updates: 5440, 8231, 8233, 8281, 8623, 8664, A. Farrel Updates: 5440, 8231, 8233, 8281, 8623, 8664, A. Farrel
8685, 8697, 8733, 8745, 8779, 8780, Old Dog Consulting 8685, 8697, 8733, 8745, 8779, 8780, Old Dog Consulting
8800, 8934, 9050, 9059, 9168, 9357, February 2025 8800, 8934, 9050, 9059, 9168, 9357, March 2025
9504, 9603, 9604 9504, 9603, 9604
Category: Standards Track Category: Standards Track
ISSN: 2070-1721 ISSN: 2070-1721
Update to the IANA PCE Communication Protocol (PCEP) Registration Update to the IANA Path Communication Element Protocol (PCEP) Numbers
Procedures and Allowing Experimental Error Codes Registration Procedures and the Allowance of Experimental Error Codes
Abstract Abstract
This document updates the registration procedure within the IANA This document updates the registration procedure within the IANA
"Path Computation Element Protocol (PCEP) Numbers" registry group. "Path Computation Element Protocol (PCEP) Numbers" registry group.
This specification changes some of the registries with Standards This specification changes some of the registries with Standards
Action to IETF Review as defined in RFC 8126 and thus updates RFCs Action to IETF Review as defined in RFC 8126 and thus updates RFCs
8231, 8233, 8281, 8623, 8664, 8685, 8697, 8733, 8745, 8779, 8780, 8231, 8233, 8281, 8623, 8664, 8685, 8697, 8733, 8745, 8779, 8780,
8800, 8934, 9050, 9059, 9168, 9357, 9504, 9603, and 9604. 8800, 8934, 9050, 9059, 9168, 9357, 9504, 9603, and 9604.
skipping to change at line 99 skipping to change at line 99
under the IETF Stream to make the allocation request. under the IETF Stream to make the allocation request.
Further, in Section 9 of [RFC5440], IANA assigns values to the PCEP Further, in Section 9 of [RFC5440], IANA assigns values to the PCEP
parameters. The allocation policy for each of these parameters parameters. The allocation policy for each of these parameters
specified in [RFC5440] is IETF Review [RFC8126]. In consideration of specified in [RFC5440] is IETF Review [RFC8126]. In consideration of
the benefits of conducting experiments with PCEP and the utility of the benefits of conducting experiments with PCEP and the utility of
experimental codepoints [RFC3692], codepoint ranges for PCEP experimental codepoints [RFC3692], codepoint ranges for PCEP
messages, objects, and TLV types for Experimental Use [RFC8126] are messages, objects, and TLV types for Experimental Use [RFC8126] are
designated in [RFC8356]. However, protocol experiments may also need designated in [RFC8356]. However, protocol experiments may also need
to return protocol error messages indicating experiment-specific to return protocol error messages indicating experiment-specific
error cases. It will often be the case that previously assigned error cases. It will often be that previously assigned error codes
error codes (in the "PCEP-ERROR Object Error Types and Values" (in the "PCEP-ERROR Object Error Types and Values" registry) can be
registry) can be used to indicate the error cases within an used to indicate the error cases within an experiment, but there may
experiment, but there may also be cases where new, experimental error also be instances where new, experimental error codes are needed. In
codes are needed. In order to run experiments, it is important that order to run experiments, it is important that the codepoint values
the codepoint values used in the experiments do not collide with used in the experiments do not collide with existing codepoints or
existing codepoints or any future allocations. This document updates any future allocations. This document updates [RFC5440] by changing
[RFC5440] by changing the allocation policy for the registry of PCEP the allocation policy for the registry of PCEP Error-Types to mark
Error-Types to mark some of the codepoints as assigned for some of the codepoints as assigned for Experimental Use. As stated
Experimental Use. As stated in [RFC3692], experiments using these in [RFC3692], experiments using these codepoints are not intended to
codepoints are not intended to be used in general deployments, and be used in general deployments, and due care must be taken to ensure
due care must be taken to ensure that two experiments using the same that two experiments using the same codepoints are not run in the
codepoints are not run in the same environment. same environment.
2. Standards Action PCEP Registries Affected 2. Standards Action PCEP Registries Affected
The following table lists the registries under the "Path Computation The following table lists the registries under the "Path Computation
Element Protocol (PCEP) Numbers" registry group whose registration Element Protocol (PCEP) Numbers" registry group whose registration
policies have been changed from Standards Action to IETF Review. The policies have been changed from Standards Action to IETF Review. The
affected registries list this document as an additional reference. affected registries list this document as an additional reference.
Where this change has been applied to a specific range of values Where this change has been applied to a specific range of values
within the particular registry, that range is given in the Remarks within the particular registry, that range is given in the Remarks
column. column.
skipping to change at line 215 skipping to change at line 215
3. Experimental Error-Types 3. Experimental Error-Types
Per this document, IANA has designated four PCEP Error-Type Per this document, IANA has designated four PCEP Error-Type
codepoints (252-255) for Experimental Use. codepoints (252-255) for Experimental Use.
IANA maintains the "PCEP-ERROR Object Error Types and Values" IANA maintains the "PCEP-ERROR Object Error Types and Values"
registry under the "Path Computation Element Protocol (PCEP) Numbers" registry under the "Path Computation Element Protocol (PCEP) Numbers"
registry group. IANA has changed the assignment policy for the registry group. IANA has changed the assignment policy for the
"PCEP-ERROR Object Error Types and Values" registry as follows: "PCEP-ERROR Object Error Types and Values" registry as follows:
* Error-Types: +=========+==============+=====================================+
| Range | Registration | Note |
0-251: IETF Review | | Procedures | |
+=========+==============+=====================================+
252-255: Experimental Use | 0-251 | IETF Review | The IETF Review procedure applies |
| | | to all Error-values (0-255) for |
* Error-values: | | | Error-Types in this range. |
+---------+--------------+-------------------------------------+
For all IETF Review Error-Types: IETF Review | 252-255 | Experimental | The Experimental Use policy applies |
| | Use | to all Error-values (0-255) for |
| | | Error-Types in this range. |
+---------+--------------+-------------------------------------+
For all Experimental Use Error-Types: Experimental Use Table 2: PCEP-ERROR Object Error Types and Values Registry
Assignment Policy
Furthermore, IANA has added the following entry to the registry: Furthermore, IANA has added the following entry to the registry:
+============+==================+=====================+===========+ +============+==================+=====================+===========+
| Error-Type | Meaning | Error-value | Reference | | Error-Type | Meaning | Error-value | Reference |
+============+==================+=====================+===========+ +============+==================+=====================+===========+
| 252-255 | Reserved for | 0-255: Reserved for | RFC 9756 | | 252-255 | Reserved for | 0-255: Reserved for | RFC 9756 |
| | Experimental Use | Experimental Use | | | | Experimental Use | Experimental Use | |
+------------+------------------+---------------------+-----------+ +------------+------------------+---------------------+-----------+
Table 2: PCEP-ERROR Object Error Types and Values Registry Table 3: PCEP-ERROR Object Error Types and Values Registry
3.1. Advice on Experimentation 3.1. Advice on Experimentation
An experiment that wishes to return experimental error codes should An experiment that wishes to return experimental error codes should
use one of the experimental Error-Type values as defined in this use one of the experimental Error-Type values as defined in this
document. The experiment should agree on, between all participating document. The experiment should agree on, between all participating
parties, which Error-Type to use and which Error-values to use within parties, which Error-Type to use and which Error-values to use within
that Error-Type. The experiment will describe what the meanings of that Error-Type. The experiment will describe what the meanings of
those Error-Type/Error-value pairs are. Those Error-Types and Error- those Error-Type/Error-value pairs are. Those Error-Types and Error-
values should not be recorded in any public (especially any IETF) values should not be recorded in any public (especially any IETF)
 End of changes. 6 change blocks. 
27 lines changed or deleted 31 lines changed or added

This html diff was produced by rfcdiff 1.48.