Carrying SID Algorithm information in PCE-based Networks.

A PCE can compute SR-TE paths using prefix SIDs with different Algorithms depending on the use-case, constraints, etc. While this information is available on the PCE, there is no method of conveying this information to the headend router. Similarly, the headend can also compute SR-TE paths using different Algorithms, and this information also needs to be conveyed to the PCE for collection or troubleshooting purposes. In addition, in the case of multiple (redundant) PCEs, when the headend receives a path from the primary PCE, it needs to be able to report the complete path information - including the Algorithm - to the backup PCE so that in HA scenarios, the backup PCE can verify the prefix SIDs appropriately. An operator may also want to constrain the path computed by the PCE to a specific SID Algorithm, for example, in order to only use SID Algorithms for a low-latency path. A new TLV is introduced for this purpose. Refer to and for details about the prefix SID Algorithm. This document introduces two new NAI types for the SR-ERO subobject, which is defined in . A new TLV for signalling SID Algorithm constraint to the PCE is also introduced, to be carried inside the LSPA object, which is defined in . The mechanisms described in this document are equally applicable to both SR-MPLS and SRv6.

The following terminologies are used in this document: Explicit Route Object Interior Gateway Protocol Node or Adjacency Identifier. Path Computation Element Path Computation Element Protocol. Segment Identifier. Segment Routing. Segment Routing Traffic Engineering. Label Switched Path. Label Switched Path Attributes.

The SR-ERO subobject encoding is extended with additional NAI types. The following new NAI types (NT) are defined: NT=TBD1: The NAI is an IPv4 node ID with Algorithm. NT=TBD2: The NAI is an IPv6 node ID with Algorithm. This document defines the following NAIs: is specified as an IPv4 address and Algorithm identifier. In this case, the NT value is TBD1 and the NAI field length is 8 octets.

is specified as an IPv6 address and Algorithm identifier. In this case, the NT value is TBD2 and the NAI field length is 20 octets.

A new TLV for the LSPA Object with TLV type=TBD3 is introduced to carry the SID Algorithm constraint. This TLV SHOULD only be used when PST (Path Setup type) = SR or SRv6. The format of the SID Algorithm TLV is as follows:

The code point for the TLV type is TBD3. The TLV length is 4 octets. The 32-bit value is formatted as follows. MUST be set to zero by the sender and MUST be ignored by the receiver. This document defines the following flag bits. The other bits MUST be set to zero by the sender and MUST be ignored by the receiver. L (Loose): If set to 1, the PCE MAY insert prefix SIDs with a different Algorithm, but it MUST prefer the specified Algorithm whenever possible. SID Algorithm the PCE MUST take into acount while computing a path for the LSP.

IPv4 prefix SIDs used by SR-TE paths with an associated Algorithm SHOULD be encoded with 'IPv4 Node ID with Algorithm' NAI. IPv6 prefix SIDs used by SR-TE paths with an associated Algorithm SHOULD be encoded with 'IPv6 Node ID with Algorithm' NAI.

In order to signal a specific SID Algorithm constraint to the PCE, the headend MUST encode the SID ALGORITHM TLV inside the LSPA object. When the PCE receives a SID Algorithm constraint, it MUST only take prefix SIDs with the specified Algorithm into account during path computation. However, if the L flag is set in the SID Algorithm TLV, the PCE MAY insert prefix SIDs with a different Algorithm in order to successfully compute a path. If the PCE is unable to find a path with the given SID Algorithm constraint, it MUST bring the LSP down. SID Algorithm does not replace the Objective Function defined in . The SID Algorithm constraint acts as a filter, restricting which SIDs may be used as a result of the path computation function.

No additional security measure is required.

IANA is requested to allocate new SR-ERO NAI types for the new NAI types specified in this document. Value Description Reference TBD1IPv4 Node ID with AlgorithmThis document TBD2IPv6 Node ID with AlgorithmThis document

IANA is requested to allocate a new TLV type for the new LSPA TLV specified in this document. Value Description Reference TBD3SID AlgorithmThis document

Mike Koldychev Cisco Systems Kanata, Ontario Canada EMail: mkoldych@cisco.com