| Internet-Draft | PCE Controlled ID Space | October 2024 |
| Li, et al. | Expires 23 April 2025 | [Page] |
The Path Computation Element Communication Protocol (PCEP) provides a mechanism for the Path Computation Elements (PCEs) to perform path computations in response to Path Computation Clients (PCCs) requests. The Stateful PCE extensions allow stateful control of Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Label Switched Paths (LSPs) using PCEP. Furthermore, PCE can be used for computing paths in the SR networks.¶
Stateful PCE provides active control of MPLS-TE LSPs via PCEP, for a model where the PCC delegates control over one or more locally configured LSPs to the PCE. Further, stateful PCE could also create and remove PCE-initiated LSPs by itself. A PCE-based Central Controller (PCECC) simplify the processing of a distributed control plane by integrating with elements of Software-Defined Networking (SDN).¶
In some use cases, such as PCECC provisioning or Binding Segment Identifier (SID) for Segment Routing (SR) allocation, there are requirements for a stateful PCE to make allocation of labels, SIDs, etc. These use cases require PCE to be aware of various identifier spaces from where to make allocations on behalf of a PCC. This document defines a generic mechanism by which a PCC can inform the PCE of the identifier space set aside for the PCE control via PCEP. The identifier could be an MPLS label, a SID, or any other identifier that can be allocated and managed by the PCE.¶
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 23 April 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.¶
[RFC5440] defines the stateless Path Computation Element Communication Protocol (PCEP) for the Path Computation Elements (PCEs) to perform path computation in response to Path Computation Clients (PCCs) requests. For supporting stateful operations, [RFC8231] specifies a set of extensions to PCEP that enable the stateful control of LSPs within and across PCEP sessions, in accordance with [RFC4657]. Furthermore, [RFC8281] defines the setup, maintenance, and teardown of PCE-initiated LSPs under the stateful PCE model, without the need for local configuration on the PCC, enabling a dynamically controlled network that is centrally controlled and deployed.¶
[RFC8283] introduces the architecture for PCE as a central controller, it examines the motivations and applicability for PCEP as a control protocol in this environment, and introduces the implications for the protocol. Also, [RFC9050] specifies the procedures and PCEP extensions for using the PCE as a Central Controller (PCECC), where LSPs are calculated/set up/initiated and label forwarding entries are downloaded through extending PCEP. However, the document assumes that label range to be used by a PCE is known and set on both PCEP peers. This document adds the capability to advertise the label range via a PCEP extension. It does so in a generic fashion to allow various other ID space apart from the MPLS label can also be advertised.¶
Similarly, [RFC9050] specifies the procedures and PCEP extensions when a PCE-based controller is also responsible for configuring the forwarding actions on the routers (SR SID distribution in this case), in addition to computing the paths for packet flows in a segment routing network and telling the edge routers what instructions to attach to packets as they enter the network. However, the document assumes that label range to be used by a PCE is known and set on both PCEP peers. This document adds the capability to advertise the range from Segment Routing Global Block (SRGB) or Segement Routing Local Block (SRLB) of the node via a PCEP extension.¶
In addition, [I-D.ietf-pce-pcep-extension-pce-controller-srv6] specifies the procedures and PCEP extensions of PCECC for SRv6. An SRv6 SID is represented as LOC:FUNCT:ARG ([RFC8986]) where LOC is the L most significant bits and FUNCT is the 128-L least significant bits. The FUNCT part of the SID is an opaque identification of a local function bound to the SID. This document adds the capability to advertise the range of Function ID (FUNCT part) via a PCEP extension.¶
Once the PCC/node has given control over an ID space (for example labels), the PCC/node MUST NOT allocate the ID from this ID space. For example, a PCC/node MUST NOT use these labels from the PCE-controlled label space to make allocation for VPN Prefix distributed via BGP or labels used for LDP/RSVP-TE signaling. This is done to make sure that the PCE control over ID space does not conflict with the existing node allocation.¶
The use cases are described in Section 3. The ID space range information can be advertised via the TLVs in the Open message. The detailed procedures are described in Section 4, and the TLV format is specified in Section 5.¶
This memo makes use of the terms defined in [RFC5440], [RFC8231], [RFC8283] and [RFC8402].¶
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.¶
A PCE-based Central Controller (PCECC) can simplify the processing of a distributed control plane by integrating with elements of SDN. Thus, the LSP/SR path can be calculated/set up/initiated and the label/SID forwarding entries can also be downloaded through a centralized PCE server to each network devices along the path while leveraging the existing PCE technologies as much as possible.¶
[RFC9050] describes a mode where LSPs are provisioned as explicit label instructions at each hop on the end-to-end path. Each router along the path must be told what label forwarding instructions to program and what resources to reserve. The controller uses PCEP to communicate with each router along the path of the end-to-end LSP. For this to work, the PCE-based controller will take responsibility for managing some part of the MPLS label space for each router that it controls as described in section 3.1.2. of [RFC8283]. A mechanism for a PCC to inform the PCE of such a label space to control is needed within PCEP.¶
[RFC8664] specifies extensions to PCEP that allow a stateful PCE to compute, update or initiate SR-TE paths. [RFC9050] describes the mechanism for PCECC to allocate and distribute the node/prefix/adjacency label (SID) via PCEP. To make such allocation, PCE needs to be aware of the label space from SRGB or SRLB [RFC8402] of the node that it can control. A mechanism for a PCC to inform the PCE of such label space to control is needed within PCEP. The full SRGB/SRLB of a node could be learned via existing IGP or BGP-LS mechanism.¶
[I-D.ietf-pce-pcep-extension-pce-controller-srv6] describes the mechanism for PCECC to allocate and provision the SRv6 SID via PCEP. An SRv6 SID is represented as LOC:FUNCT:ARG ([RFC8986]) where LOC is the L most significant bits, followed by F bits of function (FUNCT) and A bits of arguments (ARG). The FUNCT part of the SID is an opaque identification of a local function bound to the SID. To make such allocation, PCE needs to be aware of the Function ID space (FUNCT part) of the node that it controls. A mechanism for a PCC to inform the PCE of such a Function ID space to control is needed within PCEP.¶
The headend of an SR Policy binds a Binding SID (BSID) [RFC9604] to its policy [RFC9256]. The instantiation of which may involve a list of SIDs. The Binding SID can be allocated by the node as described in [RFC9604], but there is an inherent advantage in the Binding SID to be allocated by a PCE to allow SR policies to be dynamically created, updated according to the network status and operations. This is described in [RFC9050]. Therefore, a PCE needs to obtain the authority and control to allocate Binding SID actively from the PCC's label space as described in the above use case.¶
This is applicable for all binding segment irrespective of the path setup type (PST).¶
During PCEP Initialization Phase [RFC5440], Open messages are exchanged between the PCCs and the PCEs. The OPEN object may also contain a set of TLVs used to convey the capabilities in the Open message. The term 'ID' in this document, could be a MPLS label, SRv6 Function ID or any other future ID space for PCE to control and allocate from. A PCC MAY include a corresponding ID-CONTROL-SPACE TLVs in the OPEN Object to inform the corresponding ID space information that it wants the PCE to control. This TLV MUST NOT be included by the PCE and MUST be ignored on receipt by a PCC. This is an optional TLV, the PCE MAY also be aware of the ID space via some other means outside of PCEP.¶
For delegating multiple types of ID space, multiple TLVs corresponding to each ID type MUST be included in an Open message. The ID type can be MPLS label or other type of ID. The following ID-CONTROL-SPACE TLV is defined in this document -¶
LABEL-CONTROL-SPACE TLV - for MPLS Labels (including for SR-MPLS)¶
FUNCTION-ID-CONTROL-SPACE TLV - for SRv6 SID Function ID¶
The procedure of ID space control to PCE is shown below:¶
+-+-+ +-+-+ |PCC| |PCE| +-+-+ +-+-+ | | | Open msg (LABEL-CONTROL-SPACE,etc) | | | |-------- | | \ Open msg | | \ -----------------------------| | \/ | | /\ | | / ---------------------------->| | / | |<------- Keepalive | | -----------------------------| |Keepalive / | |-------- / | | \/ | | /\ | |<------- ------------------------------>| | |
If the ID space control procedure is successful, the PCE will return a KeepAlive message to the PCC. If there is an error in processing the corresponding TLV, an Error (PCErr) message will be sent to the PCC with Error-Type=1 (PCEP session establishment failure) and Error-value=TBD3 (ID space control failure).¶
After this process, a stateful PCE can learn the PCE-controlled ID spaces of a node (PCC) under its control. A PCE can then allocate IDs within the controlled-ID space. For example, a PCE can actively allocate labels and download forwarding instructions for the PCECC LSP as described in [RFC9050]. A PCE can also allocate labels from the PCE-controlled portion of the SRGB/SRLB for PCECC-SR [RFC9050]. The full SRGB/SRLB of a node could be learned via the existing IGP or BGP-LS mechanism.¶
The procedure for handling the FUNCTION-ID-CONTROL-SPACE TLV is the same as above.¶
Note that this information is advertised at the session initialization phase and thus if there is a change in ID space, the session needs to be restarted.¶
For advertising the PCE-controlled ID space to a PCE, this document defines several TLVs within the OPEN object.¶
For a PCC to inform the label space under the PCE control, this document defines a new LABEL-CONTROL-SPACE TLV.¶
The LABEL-CONTROL-SPACE TLV is an optional TLV in the OPEN object, and its format is shown in the following figure:¶
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=TBD1 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Num of Block | Flags | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Start_1 | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Range_1 | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Start_n | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Range_n | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The type (16 bits) of the TLV is TBD1. The length field (16 bits) has a variable value.¶
Num of Block (8 bits): the number of ID blocks. The range of a block is described by a start field and a range field.¶
Flags (24 bits): No flag is currently defined. The unassigned bits of the Flags field MUST be set to 0 on transmission and MUST be ignored on receipt.¶
Start_i (24 bits): indicates the beginning of the label block i.¶
Range_i (24 bits): indicates the range of the label block i.¶
Reserved: MUST be set to 0 on transmission and MUST be ignored on reception.¶
LABEL-CONTROL-SPACE TLV SHOULD be included only once in an Open Message. On receipt, only the first instance is processed and others MUST be ignored.¶
A stateful PCE can actively allocate labels and download forwarding instructions for the PCECC LSP as described in [RFC9050]. A PCE can also allocate labels from SRGB/SRLB for PCECC-SR [I-D.ietf-pce-pcep-extension-pce-controller-sr]. The Binding Segments can also be selected for the PCE-controlled space [RFC9050].¶
For a PCC to inform the SRv6 SID Function ID space under the PCE control, this document defines a new FUNCT-ID-CONTROL-SPACE TLV.¶
The FUNCT-ID-CONTROL-SPACE TLV is an optional TLV for use in the OPEN object, and its format is shown in the following figure:¶
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=TBD2 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Block | Flags |L| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SID | | Structure | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Start_1 (variable) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Range_1 (variable) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ...... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Start_n (variable) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Range_n (variable) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Loc Size | Locator_1 (variable)... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Locator_n (variable)... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The type (16 bits) of the TLV is TBD2. The length field (16 bits) has a variable value.¶
Block(8 bits): the number of ID blocks. The range of a block is described by a start field and a range field.¶
Flags (24 bits): Following flags are currently defined¶
L-flag: Locator flag, set when the locator information is included in this TLV. If L-flag is unset, Loc Size and variable Locator field MUST NOT be included in this TLV, and the Function ID spaces apply to all Locators.¶
The unassigned bits of Flags field MUST be set to 0 on transmission and MUST be ignored on receipt.¶
SID Structure: 64-bit field formatted as per "SID Structure" in [RFC9603].¶
Start_i (variable length): indicates the beginning of the Function ID block i. The length is specified in the Fun. Length field of SID Structure (SRv6 SID Function length in bits).¶
Range_i (variable length): indicates the range of the Function ID block i. The length is specified in the Fun. Length field of SID Structure.¶
Loc size (8 bits): indicates the number of Locator. Appears only when the L-flag is set.¶
Locator (variable length): the value of a Locator. The Function ID spaces specified in this TLV are associated with this locator. The length equals to LB length + LN length in the SID Structure where LB Length is the SRv6 SID Locator Block length in bits and LN Length is the SRv6 SID Locator Node length in bits. Note that there may exists multiple locator sharing the same FUNC ID space.¶
As per [RFC5440], the value portion of the PCEP TLV needs to be 4-bytes aligned, so a FUNCT-ID-CONTROL-SPACE TLV is padded with trailing zeros to a 4-byte boundary.¶
Multiple FUNCT-ID-CONTROL-SPACE TLVs MAY be included in an OPEN object to specify Function ID space specific to each locator.¶
A stateful PCE can actively allocate SRv6 SID and download SIDs for the PCECC-SRv6 as described in [I-D.ietf-pce-pcep-extension-pce-controller-srv6].¶
Note that SRv6 SID allocation involves LOC:FUNCT:ARG; the LOC is assumed to be known at PCE and FUNCT is allocated from the PCE-controlled Function ID block.¶
In case of multiple PCEs, a PCC MAY decide to give control over different ID space to each instance of the PCE. In case a PCC includes the same ID space to multiple PCEs, the PCE MUST use synchronization mechanism between PCEs to avoid issues described in [I-D.ietf-pce-state-sync].¶
The PCE would allocate ID from the PCE controlled ID space. The PCC would not allocate ID by itself from this space as long as it has an active PCEP session to a PCE to which it has given control over the ID space.¶
Note that if there is any change in the ID space, the PCC needs to bring the session down and re-establish the session with new TLVs. A future specification could specify a mechanism to update this information without bringing down the session. During state synchronization the PCE would need to consider the new ID space into consideration and needs to re-establish the LSP/SR-paths if needed.¶
The PCC can regain control of the ID space by closing the PCEP session and require new session without ID space TLVs specified in this document.¶
IANA maintains the "Path Computation Element Protocol (PCEP) Numbers" registry group. This document requests IANA actions to allocate code points for the protocol elements defined in this document.¶
IANA maintains a registry called "PCEP TLV Type Indicators". IANA is requested to make an assignment from this registry as follows:¶
Value | Meaning | Reference --------+------------------------------+------------- TBD1 | LABEL-CONTROL-SPACE TLV | [This.I-D] TBD2 | FUNCT-ID-CONTROL-SPACE TLV | [This.I-D]¶
This document defines the LABEL-CONTROL-SPACE TLV and requests that IANA to create a new registry to manage the value of the LABEL-CONTROL-SPACE TLV's 24-bits Flag field. New values are to be assigned by IETF Review [RFC8126]. Each bit should be tracked with the following qualities:¶
Currently, there is no allocation in this registry.¶
Bit | Name | Reference --------+------------------------------+------------- 0-23 | Unassigned | [This.I-D]¶
This document defines the FUNCT-ID-CONTROL-SPACE TLV and requests that IANA to create a new registry to manage the value of the FUNCT-ID-CONTROL-SPACE TLV's 24-bits Flag field. New values are to be assigned by IETF Review [RFC8126]. Each bit should be tracked with the following qualities:¶
Currently, there is no allocation in this registry.¶
Bit | Name | Reference --------+------------------------------+------------- 23 | L-Bit | [This.I-D] 0-22 | Unassigned | [This.I-D]¶
IANA is requested to allocate a error values within the "PCEP- ERROR Object Error Types and Values" registry:¶
Error-Type | Meaning |Error-value | Reference
------------+----------------+--------------+----------
1 | PCEP session | TBD3: ID | [This.I-D]
| establishment | space control|
| failure | failure |
¶
The security considerations described in [RFC9050], [I-D.ietf-pce-pcep-extension-pce-controller-sr], and [I-D.ietf-pce-pcep-extension-pce-controller-srv6] and apply to the extensions described in this document.¶
As per [RFC8231], it is RECOMMENDED that these PCEP extensions only be activated on authenticated and encrypted sessions across PCEs and PCCs belonging to the same administrative authority, using Transport Layer Security (TLS) [RFC8253] as per the recommendations and best current practices in [RFC9325] (unless explicitly set aside in [RFC8253]).¶
Thanks to Adrian Farrel, Ran Chen, Shengnan Yue, Boris Hassanov, Samuel Sidor, and Gyan Mishra for review comments.¶
During the WG adoption process, concerns were raised about using the Open message to convey the PCE-controlled ID-Space from the PCC to the PCE. These concerns were discussed during the IETF 120 meeting, and it was concluded that the Open message would continue to be used to encode the PCE-controlled ID space. It was also suggested that a generic notification mechanism could be developed to update parameters exchanged during the Open message, which would fall outside the scope of this document. One such proposal is outlined in [I-D.stone-pce-update-open].¶
Should there be separate TLV for SRGB and SRLB? - No, the SRGB and SRLB configurations of the node is done independently, it is advertised independently via IGP/BGP-LS. The label range that is set aside is orthogonal to it.¶
Dhruv Dhody Huawei India EMail: [email protected] Mach Chen Huawei Technologies China EMail: [email protected] Zhenbin Li Huawei Technologies Huawei Campus, No. 156 Beiqing Rd. Beijing 100095 China EMail: [email protected] Jie Dong Huawei Technologies Huawei Campus, No. 156 Beiqing Rd. Beijing 100095 China EMail: [email protected]¶