| RFC 9357 | LSP Object Flag Extension | February 2023 |
| Xiong | Standards Track | [Page] |
RFC 8231 describes a set of extensions to the Path Computation Element Communication Protocol (PCEP) to enable stateful control of MPLS-TE and GMPLS Label Switched Paths (LSPs) via PCEP. One of the extensions is the LSP object, which includes a Flag field with a length of 12 bits. However, all bits of the Flag field have already been assigned.¶
This document defines a new LSP-EXTENDED-FLAG TLV for the LSP object for an extended Flag field.¶
This is an Internet Standards Track document.¶
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.¶
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained athttps://www.rfc-editor.org/info/rfc9357.¶
Copyright (c) 2023 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.¶
[RFC5440] describes the Path Computation Element Communication Protocol (PCEP), which is used between a PCE and a Path Computation Client (PCC) (or other PCE) to enable computation of Multi-protocol Label Switching for Traffic Engineering (MPLS-TE) Label Switched Paths (LSPs).¶
PCEP Extensions for the Stateful PCE Model[RFC8231] describes a set of extensions to PCEP to enable active control of MPLS-TE and Generalized MPLS (GMPLS) tunnels. One of the extensions is the LSP object, which contains a Flag field; bits in the Flag field are used to indicate delegation, synchronization, removal, etc.¶
As defined in[RFC8231], the length of the Flag field is 12 bits, and all of the bits have already been defined as shown inTable 1. This document extends the Flag field of the LSP object for other use by defining a new LSP-EXTENDED-FLAG TLV for an extended Flag field in the LSP object (seeSection 3.1).¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14[RFC2119][RFC8174] when, and only when, they appear in all capitals, as shown here.¶
The LSP object is defined inSection 7.3 of [RFC8231]. This document defines a new LSP-EXTENDED-FLAG TLV for an extended Flag field in the LSP object.¶
The format of the LSP-EXTENDED-FLAG TLV shown inFigure 1 follows the format of all PCEP TLVs, as defined in[RFC5440].¶
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| Type=64 | Length |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| |// LSP Extended Flags //| |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
As an example of usage of the LSP-EXTENDED-FLAG TLV, the E-flag is requested for entropy label configuration, as proposed in[PCEP-ENTROPY-LABEL].¶
The LSP Extended Flags field is an array of units of 32 flags that are allocated starting from the most significant bit. The bits of the LSP Extended Flags field will be assigned by future documents. This document does not define any flags. Flags that an implementation is not supportingMUST be set to zero on transmission. Implementations that do not understand any particular flagMUST ignore the flag.¶
Note that PCEP peersMUST handle varying lengths of the LSP-EXTENDED-FLAG TLV.¶
If a PCEP speaker receives the LSP-EXTENDED-FLAG TLV of a length more than it currently supports or understands, itMUST ignore the bits beyond that length.¶
If a PCEP speaker receives the LSP-EXTENDED-FLAG TLV of a length less than the one supported by the implementation, itMUST act as if the bits beyond the length were not set.¶
Following the model provided inSection 3.1 of [RFC8786], we provide the following advice for new specifications that define additional flags. Each such specification is expected to describe the interaction between these new flags and any existing flags. In particular, new specifications are expected to explain how to handle the cases when both new and preexisting flags are set. They are also expected to discuss any security implications of the additional flags (if any) and their interactions with existing flags.¶
The LSP-EXTENDED-FLAG TLV defined in this document does not introduce any backward compatibility issues. An implementation that does not understand or support the LSP-EXTENDED-FLAG TLVMUST ignore the TLV, as per[RFC5440]. Future documents that define bits in the LSP-EXTENDED-FLAG TLV are expected to also define the error handling required for cases in which the LSP-EXTENDED-FLAG TLV is missing when itMUST be present.¶
Further, any additional bits in the LSP-EXTENDED-FLAG TLV that are not understood by an implementationMUST be ignored. It is expected that future documents that define bits in the LSP-EXTENDED-FLAG TLV will take that into consideration.¶
IANA has allocated the following TLV Type Indicator value within the "PCEP TLV Type Indicators" registry of the "Path Computation Element Protocol (PCEP) Numbers" registry:¶
| Value | Description | Reference |
|---|---|---|
| 64 | LSP-EXTENDED-FLAG | RFC 9357 |
IANA has created the "LSP-EXTENDED-FLAG TLV Flag Field" registry within the "Path Computation Element Protocol (PCEP) Numbers" registry to manage the LSP Extended Flags field of the LSP-EXTENDED-FLAG TLV. New values are assigned by Standards Action[RFC8126]. Each bit should be tracked with the following qualities:¶
No values are currently defined. Bits 0-31 are initially marked as "Unassigned". Bits with a higher ordinal than 31 will be added to the registry in future documents if necessary.¶
Implementations receiving set LSP Extended Flags that they do not recognizeMAY log this. That could be helpful for diagnosing backward compatibility issues with future features that utilize those flags.¶
[RFC8231] sets out security considerations for PCEP when used for communication with a stateful PCE. This document does not change those considerations. For LSP object processing, see[RFC8231].¶
The flags for the LSP object and their associated security considerations are specified in[RFC8231],[RFC8281],[RFC8623], and[BIND-LABEL-SID].¶
This document provides for the future addition of flags in the LSP object. Any future document that specifies new flags must also discuss any associated security implications. No additional security issues are raised in this document beyond those that exist in the referenced documents. Note that[RFC8231] recommends that the stateful PCEP extension be authenticated and encrypted using Transport Layer Security (TLS)[RFC8253][PCEPS-TLS1.3], as per the recommendations and best current practices in[RFC9325]. Assuming that the recommendation is followed, then the flags will be protected by TLS.¶
The working group discussed the idea of a fixed length (with 32 bits) for the LSP-EXTENDED-FLAG TLV. Though 32 bits would be sufficient for quite a while, the use of variable length with a multiple of 32 bits allows for future extensibility where we would never run out of flags and there would not be a need to define yet another TLV in the future. Further, note that[RFC5088] and[RFC5089] use the same approach for the PCE-CAP-FLAGS sub-TLV and are found to be useful.¶
The authors would like to thankLoa Andersson,Adrian Farrel,Aijun Wang, andGyan Mishra for their reviews, suggestions, and comments for this document.¶
The following people have substantially contributed to this document:¶