Internet-Draft | PCEP-IANA | July 2024 |
Dhody | Expires 24 January 2025 | [Page] |
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, and 9504.¶
This note is to be removed before publishing as an RFC.¶
Discussion of this document takes place on the Path Computation Element Working Group mailing list (pce@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/pce/.¶
Source for this draft and an issue tracker can be found at https://github.com/dhruvdhody/draft-dhody-pce-iana-update.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 24 January 2025.¶
Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
The IANA "Path Computation Element Protocol (PCEP) Numbers" registry was populated by several RFCs produced by the Path Computation Element (PCE) working group. Most of the registries include the "IETF Review" [RFC8126] as registration procedures. There are a few registries that use "Standards Action". Thus the values in those registries can be assigned only through Standards Track or Best Current Practice RFCs in the IETF Stream. This memo changes the policy from Standards Action to IETF Review to allow any type of RFC under the IETF stream to make the allocation request.¶
The following table lists the "Path Computation Element Protocol (PCEP) Numbers" registries whose registration policy has changed from Standards Action to IETF Review. Affected registries now list this document as a reference. Where this change is applied to a specific range of values within the particular registry, that range is given in the Remarks column.¶
Registry | RFC | Remarks |
---|---|---|
BU Object Type Field | [RFC8233] | |
LSP Object Flag Field | [RFC8231] | |
STATEFUL-PCE-CAPABILITY TLV Flag Field | [RFC8231] | |
LSP-ERROR-CODE TLV Error Code Field | [RFC8231] | |
SRP Object Flag Field | [RFC8281] | |
SR-ERO Flag Field | [RFC8664] | |
PATH-SETUP-TYPE-CAPABILITY Sub-TLV Type Indicators | [RFC8664] | |
SR Capability Flag Field | [RFC8664] | |
WA Object Flag Field | [RFC8780] | |
Wavelength Restriction Constraint TLV Action Values | [RFC8780] | |
Wavelength Allocation TLV Flag Field | [RFC8780] | |
S2LS Object Flag Field | [RFC8623] | |
H-PCE-CAPABILITY TLV Flag Field | [RFC8685] | |
H-PCE-FLAG TLV Flag Field | [RFC8685] | |
ASSOCIATION Flag Field | [RFC8697] | |
ASSOCIATION Type Field | [RFC8697] | |
AUTO-BANDWIDTH-CAPABILITY TLV Flag Field | [RFC8733] | |
Path Protection Association Group TLV Flag Field | [RFC8745] | |
Generalized Endpoint Types | [RFC8779] | 0-244 |
GMPLS-CAPABILITY TLV Flag Field | [RFC8779] | |
DISJOINTNESS-CONFIGURATION TLV Flag Field | [RFC8800] | |
SCHED-PD-LSP-ATTRIBUTE TLV Opt Field | [RFC8934] | |
Schedule TLVs Flag Field | [RFC8934] | |
FLOWSPEC Object Flag Field | [RFC9168] | |
Bidirectional LSP Association Group TLV Flag Field | [RFC9059] | |
PCECC-CAPABILITY sub-TLV | [RFC9050] | |
CCI Object Flag Field for MPLS Label | [RFC9050] | |
TE-PATH-BINDING TLV BT Field | [RFC9050] | |
TE-PATH-BINDING TLV Flag Field | [I-D.ietf-pce-binding-label-sid] | |
LSP-EXTENDED-FLAG TLV Flag Field | [RFC9357] | |
LSP Exclusion Subobject Flag Field | [RFC9504] | |
SRv6-ERO Flag Field | [I-D.ietf-pce-segment-routing-ipv6] | |
SRv6 Capability Flag Field | [I-D.ietf-pce-segment-routing-ipv6] |
Question to the WG: The current document updates all the registries. Should we keep "Standards Action" for some of them such as flag fields with limited bits?¶
This memo does not change the Security Considerations for any of the updated RFCs.¶
This memo is entirely about updating the IANA "Path Computation Element Protocol (PCEP) Numbers" registry.¶
Thanks to John Scudder for the initial discussion behind this document.¶