Label Switched Path Ping for Segment Routing Path Segment Identifier with MPLS Data Plane

Label Switched Path Ping for Segment Routing Path Segment Identifier with MPLS Data Plane ZTE Corp.

Nanjing China +86 18061680168 xiao.min2@zte.com.cn

ZTE Corp.

Nanjing China peng.shaofu@zte.com.cn

China Mobile

Beijing China gongliyan@chinamobile.com

Cisco Systems, Inc.

Canada rgandhi@cisco.com

Blue Fern Consulting

United States of America carlos@bluefern.consulting

RTG mpls Segment Routing (SR) leverages source routing to steer packets through an ordered list of instructions called "segments". SR can be instantiated over the MPLS data plane. Path Segment Identifiers (PSIDs) are used to identify and correlate bidirectional or end-to-end paths in SR networks. This document defines procedures (i.e., six new Target Forwarding Equivalence Class (FEC) Stack sub-TLVs) for the use of LSP Ping to support connectivity verification and fault isolation for SR paths that include PSIDs. The mechanisms described enable the validation and tracing of SR paths with Path SIDs in MPLS networks, complementing existing SR-MPLS Operations, Administration, and Maintenance (OAM) capabilities.

Status of This Memo 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 at .

Copyright Notice Copyright (c) 2025 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 () 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.

Table of Contents

. Introduction
. Conventions
- . Requirements Language
- . Terminology
. Path Segment ID Sub-TLVs
- . SR Policy Associated PSID - IPv4 Sub-TLV
- . SR Candidate Path Associated PSID - IPv4 Sub-TLV
- . SR Segment List Associated PSID - IPv4 Sub-TLV
- . SR Policy Associated PSID - IPv6 Sub-TLV
- . SR Candidate Path Associated PSID - IPv6 Sub-TLV
- . SR Segment List Associated PSID - IPv6 Sub-TLV
. PSID FEC Validation
- . PSID FEC Validation Rules
. Security Considerations
. IANA Considerations
. References
- . Normative References
- . Informative References
Acknowledgements
Authors' Addresses

Introduction A Path Segment is a local segment that uniquely identifies an SR path on the egress node. A Path Segment Identifier (PSID) is a single label that is assigned from the SR Local Block (SRLB) of the egress node of an SR path. As specified in , PSID is a single label inserted by the ingress node of the SR path and then processed by the egress node of the SR path. The PSID is placed within the MPLS label stack as a label immediately following the last label of the SR path. The egress node pops the PSID. The procedure for LSP Ping as defined in is also applicable to PSID; this document appends the existing step 4a with a new step 4b specific to PSID. Concretely, LSP Ping can be used to check the correct operation of a PSID and verify the PSID against the control plane. Checking correct operation means that an initiator can use LSP Ping to check whether a PSID reached the intended node and got processed by that node correctly. Moreover, verifying a PSID against the control plane means that the initiator can use LSP Ping to verify the SR path context (segment-list, candidate path, or SR Policy) associated with the PSID as signaled or provisioned at the egress node. To that end, this document specifies six new Target Forwarding Equivalence Class (FEC) Stack sub-TLVs for such PSID checks. LSP Traceroute is left out of this document because transit nodes are not involved in PSID processing.

Conventions

Requirements Language 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 when, and only when, they appear in all capitals, as shown here.

Terminology This document uses the terminology defined in , , , and ; readers are expected to be familiar with the terms in those documents. This document introduces the following additional term:

Segment-List-ID: The Segment-List-ID field is a 4-octet identifier that uniquely identifies a segment list within the context of the candidate path of an SR Policy. Although not defined in , the Segment-List-ID is the same identifier as the one that can be signaled through control plane protocols including Border Gateway Protocol (BGP) (, Path Computation Element Communication Protocol (PCEP) (), and Border Gateway Protocol - Link State (BGP-LS) ().

Path Segment ID Sub-TLVs Analogous to what's defined in and , six new sub-TLVs are defined for the Target FEC Stack TLV (Type 1), the Reverse-Path Target FEC Stack TLV (Type 16), and the Reply Path TLV (Type 21). Note that the structures of the six new sub-TLVs follow the TLV's structure defined in . Sub-TLVs for PSID Checks

Sub-Type	Sub-TLV Name
49	SR Policy Associated PSID - IPv4
50	SR Candidate Path Associated PSID - IPv4
51	SR Segment List Associated PSID - IPv4
52	SR Policy Associated PSID - IPv6
53	SR Candidate Path Associated PSID - IPv6
54	SR Segment List Associated PSID - IPv6

As specified in , a PSID is used to identify the following:

a single segment list, some segment lists, or all segment lists in a candidate path of an SR Policy,
some segment lists across multiple candidate paths of an SR Policy, or
all segment lists in all candidate paths of an SR Policy.

Therefore, six different Target FEC Stack sub-TLVs need to be defined for PSID. The ordered list of selection rules for the six Target FEC Stack sub-TLVs are defined as follows:

When a PSID is used to identify all segment lists in an SR Policy, the Target FEC Stack sub-TLV of the type "SR Policy Associated PSID" (for IPv4 or IPv6) MUST be used for PSID checks.
When a PSID is used to identify all segment lists in an SR Candidate Path, the Target FEC Stack sub-TLV of the type "SR Candidate Path Associated PSID" (for IPv4 or IPv6) MUST be used for PSID checks.
When a PSID is used to identify a single segment list, the Target FEC Stack sub-TLV of the type "SR Segment List Associated PSID" (for IPv4 or IPv6) MUST be used for PSID checks.
When a PSID is used to identify some segment lists in a candidate path or an SR Policy, the Target FEC Stack sub-TLV of the type "SR Segment List Associated PSID" (for IPv4 or IPv6) MUST be used for PSID checks. In this case, multiple LSP Ping messages MUST be sent, and one Target FEC Stack sub-TLV of the type "SR Segment List Associated PSID" (for IPv4 or IPv6) MUST be carried in each LSP Ping message.

These six new Target FEC Stack sub-TLVs are not expected to be present in the same message. If more than one of these sub-TLVs are present in a message, only the first sub-TLV will be processed, per the validation rules in .

SR Policy Associated PSID - IPv4 Sub-TLV The SR Policy Associated PSID - IPv4 sub-TLV is defined as follows:

SR Policy Associated PSID - IPv4 Sub-TLV Format 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 = 49 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Headend (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Color (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Endpoint (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Type (length: 2 octets): The Type field identifies the sub-TLV as an SR Policy Associated PSID - IPv4 sub-TLV. The value is set to 49.
Length (length: 2 octets): The Length field indicates the length of the sub-TLV in octets, excluding the first 4 octets (Type and Length fields). The value MUST be set to 12.
Headend (length: 4 octets): The Headend field encodes the headend IPv4 address of the SR Policy. This field is defined in .
Color (length: 4 octets): The Color field identifies the color (i.e., policy identifier) of the SR Policy and is encoded as defined in .
Endpoint (length: 4 octets): The Endpoint field encodes the endpoint IPv4 address of the SR Policy. This field is defined in .

SR Candidate Path Associated PSID - IPv4 Sub-TLV The SR Candidate Path Associated PSID - IPv4 sub-TLV is defined as follows:

SR Candidate Path Associated PSID - IPv4 Sub-TLV Format 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 = 50 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Headend (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Color (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Endpoint (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Protocol-Origin| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | | | Originator (20 octets) | | | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Discriminator (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Type (length: 2 octets): The Type field identifies the sub-TLV as an SR Candidate Path Associated PSID - IPv4 sub-TLV. The value is set to 50.
Length (length: 2 octets): The Length field indicates the length of the sub-TLV in octets, excluding the first 4 octets (Type and Length fields). The value MUST be set to 40.
Headend (length: 4 octets): The Headend field encodes the headend IPv4 address of the SR Candidate Path. This field is defined in .
Color (length: 4 octets): The Color field identifies the policy color and is defined in .
Endpoint (length: 4 octets): The Endpoint field encodes the endpoint IPv4 address of the SR Candidate Path. This field is defined in .
Protocol-Origin (length: 1 octet): The Protocol-Origin field indicates the protocol that originated the SR Candidate Path. It is defined in and takes values from the IANA registry . If an unsupported value is used, validation at the responder MUST fail.
Reserved (length: 3 octets): The Reserved field is reserved for future use. It MUST be set to zero when sent and MUST be ignored upon receipt.
Originator (length: 20 octets): The Originator field identifies the originator of the SR Candidate Path and is encoded as defined in .
Discriminator (length: 4 octets): The Discriminator field uniquely identifies the SR Candidate Path within the context of the Headend, Color, and Endpoint fields. This field is defined in .

SR Segment List Associated PSID - IPv4 Sub-TLV The SR Segment List Associated PSID - IPv4 sub-TLV is used to identify a specific segment list within the context of a candidate path of an SR Policy. The format of this sub-TLV is shown in .

SR Segment List Associated PSID - IPv4 Sub-TLV Format 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 = 51 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Headend (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Color (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Endpoint (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Protocol-Origin| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | | | Originator (20 octets) | | | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Discriminator (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Segment-List-ID (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Type (length: 2 octets): The Type field identifies the sub-TLV as an SR Segment List Associated PSID - IPv4 sub-TLV. The value is set to 51.
Length (length: 2 octets): The Length field indicates the length of the sub-TLV in octets, excluding the first 4 octets (Type and Length fields). The value MUST be set to 44.
Headend (length: 4 octets): The Headend field encodes the headend IPv4 address of the SR Policy. This field is defined in .
Color (length: 4 octets): The Color field identifies the color of the SR Policy and is encoded as specified in .
Endpoint (length: 4 octets): The Endpoint field specifies the endpoint IPv4 address of the SR Policy, as defined in .
Protocol-Origin (length: 1 octet): The Protocol-Origin field indicates the protocol that originated the SR Candidate Path. It is defined in and takes values from the IANA registry . If an unsupported value is used, validation at the responder MUST fail.
Reserved (length: 3 octets): The Reserved field is reserved for future use. It MUST be set to zero when transmitted and MUST be ignored upon receipt.
Originator (length: 20 octets): The Originator field identifies the originator of the SR Candidate Path and is defined in .
Discriminator (length: 4 octets): The Discriminator field uniquely identifies the SR Candidate Path within the context of the Headend, Color, and Endpoint fields. This field is defined in .
Segment-List-ID (length: 4 octets): The Segment-List-ID field is a 4-octet identifier that uniquely identifies a segment list within the context of the candidate path of an SR Policy. This field is defined in .

SR Policy Associated PSID - IPv6 Sub-TLV The SR Policy Associated PSID - IPv6 sub-TLV is defined as follows:

SR Policy Associated PSID - IPv6 Sub-TLV Format 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 = 52 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | Headend (16 octets) | | | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Color (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | Endpoint (16 octets) | | | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Type (length: 2 octets): The Type field identifies the sub-TLV as an SR Policy Associated PSID - IPv6 sub-TLV. The value is set to 52.
Length (length: 2 octets): The Length field indicates the length of the sub-TLV in octets, excluding the first 4 octets (Type and Length fields). The value MUST be set to 36.
Headend (length: 16 octets): The Headend field encodes the headend IPv6 address of the SR Policy. This field is defined in .
Color (length: 4 octets): The Color field identifies the color (i.e., policy identifier) of the SR Policy and is encoded as defined in .
Endpoint (length: 16 octets): The Endpoint field encodes the endpoint IPv6 address of the SR Policy. This field is defined in .

SR Candidate Path Associated PSID - IPv6 Sub-TLV The SR Candidate Path Associated PSID - IPv6 sub-TLV is defined as follows:

SR Candidate Path Associated PSID - IPv6 Sub-TLV Format 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 = 53 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | Headend (16 octets) | | | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Color (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | Endpoint (16 octets) | | | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Protocol-Origin| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | | | Originator (20 octets) | | | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Discriminator (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Type (length: 2 octets): The Type field identifies the sub-TLV as an SR Candidate Path Associated PSID - IPv6 sub-TLV. The value is set to 53.
Length (length: 2 octets): The Length field indicates the length of the sub-TLV in octets, excluding the first 4 octets (Type and Length fields). The value MUST be set to 64.
Headend (length: 16 octets): The Headend field encodes the headend IPv6 address of the SR Candidate Path. This field is defined in .
Color (length: 4 octets): The Color field identifies the policy color and is defined in .
Endpoint (length: 16 octets): The Endpoint field encodes the endpoint IPv6 address of the SR Candidate Path. This field is defined in .
Protocol-Origin (length: 1 octet): The Protocol-Origin field indicates the protocol that originated the SR Candidate Path. It is defined in and takes values from the IANA registry . If an unsupported value is used, validation at the responder MUST fail.
Reserved (length: 3 octets): The Reserved field is reserved for future use. It MUST be set to zero when sent and MUST be ignored upon receipt.
Originator (length: 20 octets): The Originator field identifies the originator of the SR Candidate Path and is encoded as defined in .
Discriminator (length: 4 octets): The Discriminator field uniquely identifies the SR Candidate Path within the context of the Headend, Color, and Endpoint fields. This field is defined in .

SR Segment List Associated PSID - IPv6 Sub-TLV The SR Segment List Associated PSID - IPv6 sub-TLV is used to identify a specific segment list within the context of a candidate path of an SR Policy. The format of this sub-TLV is shown in .

SR Segment List Associated PSID - IPv6 Sub-TLV Format 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 = 54 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | Headend (16 octets) | | | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Color (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | Endpoint (16 octets) | | | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Protocol-Origin| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | | | Originator (20 octets) | | | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Discriminator (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Segment-List-ID (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Type (length: 2 octets): The Type field identifies the sub-TLV as an SR Segment List Associated PSID - IPv6 sub-TLV. The value is set to 54.
Length (length: 2 octets): The Length field indicates the length of the sub-TLV in octets, excluding the first 4 octets (Type and Length fields). The value MUST be set to 68.
Headend (length: 16 octets): The Headend field encodes the headend IPv6 address of the SR Policy. This field is defined in .
Color (length: 4 octets): The Color field identifies the color of the SR Policy and is encoded as specified in .
Endpoint (length: 16 octets): The Endpoint field specifies the endpoint IPv6 address of the SR Policy, as defined in .
Protocol-Origin (length: 1 octet): The Protocol-Origin field indicates the protocol that originated the SR Candidate Path. It is defined in and takes values from the IANA registry . If an unsupported value is used, validation at the responder MUST fail.
Reserved (length: 3 octets): The Reserved field is reserved for future use. It MUST be set to zero when transmitted and MUST be ignored upon receipt.
Originator (length: 20 octets): The Originator field identifies the originator of the SR Candidate Path and is defined in .
Discriminator (length: 4 octets): The Discriminator field uniquely identifies the SR Candidate Path within the context of the Headend, Color, and Endpoint fields. This field is defined in .
Segment-List-ID (length: 4 octets): The Segment-List-ID field is a 4-octet identifier that uniquely identifies a segment list within the context of the candidate path of an SR Policy. This field is defined in .

PSID FEC Validation The MPLS LSP Ping procedures may be initiated by the headend of the SR path or a centralized topology-aware data plane monitoring system as described in . For the PSID, the responder nodes that receive an echo request and send an echo reply MUST be the endpoint of the SR path. When an endpoint receives the LSP echo request packet with the top FEC being the PSID, it MUST perform validity checks on the content of the PSID Target FEC Stack sub-TLV. If a malformed Target FEC Stack sub-TLV is received, then a return code of 1, "Malformed echo request received" as defined in MUST be sent. The section below is appended to step 4a of .

PSID FEC Validation Rules 4b. Segment Routing PSID Validation: If the Label-stack-depth is 1 and the Target FEC Stack sub-TLV at FEC-stack-depth is 49 (SR Policy Associated PSID - IPv4 sub-TLV), { Set the Best-return-code to 10 "Mapping for this FEC is not the given label at stack-depth <RSC>" if any below conditions fail (the notation <RSC> refers to the Return Subcode): - Validate that the PSID is signaled or provisioned for the SR Policy { * Validate that the signaled or provisioned headend, color, and endpoint for the PSID match with the corresponding fields in the received SR Policy Associated PSID - IPv4 sub-TLV. } } If all the above validations have passed, set the return code to 3 "Replying router is an egress for the FEC at stack-depth <RSC>". Set the FEC-Status to 1 and return. } Else, if the Label-stack-depth is 1 and the Target FEC Stack sub-TLV at FEC-stack-depth is 50 (SR Candidate Path Associated PSID - IPv4 sub-TLV), { Set the Best-return-code to 10 "Mapping for this FEC is not the given label at stack-depth <RSC>" if any below conditions fail: - Validate that the PSID is signaled or provisioned for the SR Candidate Path { * Validate that the signaled or provisioned headend, color, endpoint, originator, and discriminator for the PSID match with the corresponding fields in the received SR Candidate Path Associated PSID - IPv4 sub-TLV. } } If all the above validations have passed, set the return code to 3 "Replying router is an egress for the FEC at stack-depth <RSC>". Set the FEC-Status to 1 and return. } Else, if the Label-stack-depth is 1 and the Target FEC Stack sub-TLV at FEC-stack-depth is 51 (SR Segment List Associated PSID - IPv4 sub-TLV), { Set the Best-return-code to 10 "Mapping for this FEC is not the given label at stack-depth <RSC>" if any below conditions fail: - Validate that the PSID is signaled or provisioned for the SR Segment List { * Validate that the signaled or provisioned headend, color, endpoint, originator, discriminator, and segment-list-id for the PSID match with the corresponding fields in the received SR Segment List Associated PSID - IPv4 sub-TLV. } } If all the above validations have passed, set the return code to 3, "Replying router is an egress for the FEC at stack-depth <RSC>". Set the FEC-Status to 1 and return. } Else, if the Label-stack-depth is 1 and the Target FEC Stack sub-TLV at FEC-stack-depth is 52 (SR Policy Associated PSID - IPv6 sub-TLV), { Set the Best-return-code to 10 "Mapping for this FEC is not the given label at stack-depth <RSC>" if any below conditions fail - Validate that the PSID is signaled or provisioned for the SR Policy { * Validate that the signaled or provisioned headend, color, and endpoint for the PSID match with the corresponding fields in the received SR Policy Associated PSID - IPv6 sub- TLV. } } If all the above validations have passed, set the return code to 3 "Replying router is an egress for the FEC at stack-depth <RSC>". Set the FEC-Status to 1 and return. } Else, if the Label-stack-depth is 1 and the Target FEC Stack sub-TLV at FEC-stack-depth is 53 (SR Candidate Path Associated PSID - IPv6 sub-TLV), { Set the Best-return-code to 10 "Mapping for this FEC is not the given label at stack-depth <RSC>" if any below conditions fail: - Validate that the PSID is signaled or provisioned for the SR Candidate Path { * Validate that the signaled or provisioned headend, color, endpoint, originator, and discriminator for the PSID match with the corresponding fields in the received SR Candidate Path Associated PSID - IPv6 sub-TLV. } } If all the above validations have passed, set the return code to 3 "Replying router is an egress for the FEC at stack-depth <RSC>". Set the FEC-Status to 1 and return. } Else, if the Label-stack-depth is 1 and the Target FEC Stack sub-TLV at FEC-stack-depth is 54 (SR Segment List Associated PSID - IPv6 sub-TLV), { Set the Best-return-code to 10 "Mapping for this FEC is not the given label at stack-depth <RSC>" if any below conditions fail: - Validate that the PSID is signaled or provisioned for the SR Segment List { * Validate that the signaled or provisioned headend, color, endpoint, originator, discriminator, and segment-list-id for the PSID match with the corresponding fields in the received SR Segment List Associated PSID - IPv6 sub-TLV. } } If all the above validations have passed, set the return code to 3 "Replying router is an egress for the FEC at stack-depth <RSC>". Set the FEC-Status to 1 and return. } When any of the following is carried in a Reverse-Path Target FEC Stack TLV (Type 16) or Reply Path TLV (Type 21), it MUST be sent by an endpoint in an echo reply.

SR Policy Associated PSID - IPv4 sub-TLV,
SR Candidate Path Associated PSID - IPv4 sub-TLV,
SR Segment List Associated PSID - IPv4 sub-TLV,
SR Policy Associated PSID - IPv6 sub-TLV,
SR Candidate Path Associated PSID - IPv6 sub-TLV, or
SR Segment List Associated PSID - IPv6 sub-TLV

The headend MUST perform validity checks as described above without setting the return code. If any of the validations fail, then the headend MUST drop the echo reply and SHOULD log and/or report an error.

Security Considerations This document defines additional MPLS LSP Ping sub-TLVs and follows the mechanisms defined in . All the security considerations defined in apply to this document. The MPLS LSP Ping sub-TLVs defined in this document do not impose any additional security challenges to be considered.

IANA Considerations IANA has assigned six Target FEC Stack sub-TLVs from the "Sub-TLVs for TLV Types 1, 16, and 21" registry within the "TLVs" registry of the "Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters" registry group. The Standards Action range that requires an error message to be returned if the sub-TLV is not recognized (range 0-16383) has been used. Sub-TLVs for TLV Types 1, 16, and 21 Registry

Sub-Type	Sub-TLV Name	Reference
49	SR Policy Associated PSID - IPv4	of RFC 9884
50	SR Candidate Path Associated PSID - IPv4	of RFC 9884
51	SR Segment List Associated PSID - IPv4	of RFC 9884
52	SR Policy Associated PSID - IPv6	of RFC 9884
53	SR Candidate Path Associated PSID - IPv6	of RFC 9884
54	SR Segment List Associated PSID - IPv6	of RFC 9884

References Normative References Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters IANA SR Policy Protocol Origin IANA Key words for use in RFCs to Indicate Requirement Levels In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures This document describes a simple and efficient mechanism to detect data-plane failures in Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs). It defines a probe message called an "MPLS echo request" and a response message called an "MPLS echo reply" for returning the result of the probe. The MPLS echo request is intended to contain sufficient information to check correct operation of the data plane and to verify the data plane against the control plane, thereby localizing faults. This document obsoletes RFCs 4379, 6424, 6829, and 7537, and updates RFC 1122. Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes A Segment Routing (SR) architecture leverages source routing and tunneling paradigms and can be directly applied to the use of a Multiprotocol Label Switching (MPLS) data plane. A node steers a packet through a controlled set of instructions called "segments" by prepending the packet with an SR header. The segment assignment and forwarding semantic nature of SR raises additional considerations for connectivity verification and fault isolation for a Label Switched Path (LSP) within an SR architecture. This document illustrates the problem and defines extensions to perform LSP Ping and Traceroute for Segment Routing IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with an MPLS data plane. Segment Routing Policy Architecture Segment Routing (SR) allows a node to steer a packet flow along any path. Intermediate per-path states are eliminated thanks to source routing. SR Policy is an ordered list of segments (i.e., instructions) that represent a source-routed policy. Packet flows are steered into an SR Policy on a node where it is instantiated called a headend node. The packets steered into an SR Policy carry an ordered list of segments associated with that SR Policy. This document updates RFC 8402 as it details the concepts of SR Policy and steering into an SR Policy. Path Segment Identifier in MPLS-Based Segment Routing Networks A Segment Routing (SR) path is identified by an SR segment list. A subset of segments from the segment list cannot be leveraged to distinguish one SR path from another as they may be partially congruent. SR path identification is a prerequisite for various use cases such as performance measurement and end-to-end 1+1 path protection. In an SR over MPLS (SR-MPLS) data plane, an egress node cannot determine on which SR path a packet traversed the network from the label stack because the segment identifiers are removed from the label stack as the packet transits the network. This document defines a Path Segment Identifier (PSID) to identify an SR path on the egress node of the path. Informative References Path Computation Element Communication Protocol (PCEP) Extensions for Signaling Multipath Information Ciena Corporation Ciena Corporation Cisco Systems Juniper Networks, Inc. Nokia Ciena Huawei Technologies Verizon Inc. Cisco Systems. Certain traffic engineering path computation problems require solutions that consist of multiple traffic paths that together form a solution. Returning a single traffic path does not provide a valid solution. This document defines mechanisms to encode multiple paths for a single set of objectives and constraints. This allows encoding of multiple Segment Lists per Candidate Path within a Segment Routing Policy. The new Path Computation Element Communication Protocol (PCEP) mechanisms are designed to be generic, where possible, to allow for future re-use outside of SR Policy. The new PCEP mechanisms are applicable to both stateless and stateful PCEP. Additionally, this document updates RFC 8231 to allow encoding of multiple Segment Lists in PCEP. Work in Progress Multiprotocol Label Switching Architecture This document specifies the architecture for Multiprotocol Label Switching (MPLS). [STANDARDS-TRACK] Guidelines for Writing an IANA Considerations Section in RFCs Many protocols make use of points of extensibility that use constants to identify various protocol parameters. To ensure that the values in these fields do not have conflicting uses and to promote interoperability, their allocations are often coordinated by a central record keeper. For IETF protocols, that role is filled by the Internet Assigned Numbers Authority (IANA). To make assignments in a given registry prudently, guidance describing the conditions under which new values should be assigned, as well as when and how modifications to existing values can be made, is needed. This document defines a framework for the documentation of these guidelines by specification authors, in order to assure that the provided guidance for the IANA Considerations is clear and addresses the various issues that are likely in the operation of a registry. This is the third edition of this document; it obsoletes RFC 5226. Segment Routing Architecture Segment Routing (SR) leverages the source routing paradigm. A node steers a packet through an ordered list of instructions, called "segments". A segment can represent any instruction, topological or service based. A segment can have a semantic local to an SR node or global within an SR domain. SR provides a mechanism that allows a flow to be restricted to a specific topological path, while maintaining per-flow state only at the ingress node(s) to the SR domain. SR can be directly applied to the MPLS architecture with no change to the forwarding plane. A segment is encoded as an MPLS label. An ordered list of segments is encoded as a stack of labels. The segment to process is on the top of the stack. Upon completion of a segment, the related label is popped from the stack. SR can be applied to the IPv6 architecture, with a new type of routing header. A segment is encoded as an IPv6 address. An ordered list of segments is encoded as an ordered list of IPv6 addresses in the routing header. The active segment is indicated by the Destination Address (DA) of the packet. The next active segment is indicated by a pointer in the new routing header. A Scalable and Topology-Aware MPLS Data-Plane Monitoring System This document describes features of an MPLS path monitoring system and related use cases. Segment-based routing enables a scalable and simple method to monitor data-plane liveliness of the complete set of paths belonging to a single domain. The MPLS monitoring system adds features to the traditional MPLS ping and Label Switched Path (LSP) trace, in a very complementary way. MPLS topology awareness reduces management and control-plane involvement of Operations, Administration, and Maintenance (OAM) measurements while enabling new OAM features. Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) Egress Peer Engineering (EPE) Segment Identifiers (SIDs) with MPLS Data Plane Egress Peer Engineering (EPE) is an application of Segment Routing (SR) that solves the problem of egress peer selection. The SR-based BGP-EPE solution allows a centralized controller, e.g., a Software-Defined Network (SDN) controller, to program any egress peer. The EPE solution requires the node or the SDN controller to program 1) the PeerNode Segment Identifier (SID) describing a session between two nodes, 2) the PeerAdj SID describing the link or links that are used by the sessions between peer nodes, and 3) the PeerSet SID describing any connected interface to any peer in the related group. This document provides new sub-TLVs for EPE-SIDs that are used in the Target FEC Stack TLV (Type 1) in MPLS Ping and Traceroute procedures. Advertisement of Segment Routing Policies Using BGP - Link State Individual Cisco Systems Huawei Technologies RtBrick Inc. Nvidia BGP SR Policy Extensions for Segment List Identifier New H3C Technologies China Mobile ZTE Cisco Systems New H3C Technologies Segment Routing is a source routing paradigm that explicitly indicates the forwarding path for packets at the ingress node. An SR Policy is a set of candidate paths, each consisting of one or more segment lists. This document defines extensions to BGP SR Policy to specify the identifier of segment list. Work in Progress

Acknowledgements The authors would like to acknowledge , , , , , , , , , , , , , and for their thorough review and very helpful comments. The authors would like to acknowledge and for the very helpful face to face discussion.

Authors' Addresses ZTE Corp.