| Internet-Draft | LSP Ping for SR PSID | May 2025 |
| Min, et al. | Expires 20 November 2025 | [Page] |
Path Segment is a type of Segment Routing (SR) segment, and a Path Segment Identifier (PSID) is used to identify an SR path. Path Segment can be used in an SR over MPLS (SR-MPLS) data plane. This document specifies three new Target Forwarding Equivalence Class (FEC) Stack sub-TLVs for PSID checks.¶
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 20 November 2025.¶
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 (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.¶
Path Segment is a type of Segment Routing (SR) segment, and a Path Segment Identifier (PSID) is used to identify an SR path. PSID in MPLS-based segment routing networks is defined in [RFC9545].¶
As specified in [RFC9545], 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 MUST pop the PSID.¶
Procedures for LSP Ping [RFC8029] as defined in [RFC8287] and [RFC8690] are also applicable 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 whether a given node has the same understanding whith the initiator on how the PSID was constructed by the control plane. To that end, this document specifies three new Target Forwarding Equivalence Class (FEC) Stack sub-TLVs for such PSID checks.¶
LSP Traceroute [RFC8287] is left out of this document because transit nodes are not involved in PSID processing.¶
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.¶
This document uses the terminology defined in [RFC3031], [RFC8402], and [RFC8029], readers are expected to be familiar with those terms.¶
Analogous to what's defined in Section 5 of [RFC8287] and Section 4 of [RFC9703], three 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 three new sub-TLVs follow the TLV's structure defined in Section 3 of [RFC8029].¶
Sub-Type Sub-TLV Name
-------- -----------------------------
TBD1 SR Policy's PSID
TBD2 SR Candidate Path's PSID
TBD3 SR Segment List's PSID
¶
As specified in Section 2 of [RFC9545], a PSID is used to identify a segment list, some or all segment lists in a Candidate path or an SR policy, so three different Target FEC Stack sub-TLVs need to be defined for PSID. When a PSID is used to identify an SR Policy, the Target FEC Stack sub-TLV of the type "SR Policy's PSID" is used to validate the control plane to forwarding plane synchronization for this PSID; When a PSID is used to identify an SR Candidate Path, the Target FEC Stack sub-TLV of the type "SR Candidate Path's PSID" is used to validate the control plane to forwarding plane synchronization for this PSID; When a PSID is used to identify a Segment List, the Target FEC Stack sub-TLV of the type "SR Segment List's PSID" is used to validate the control plane to forwarding plane synchronization for this PSID. These three new Target FEC Stack sub-TLVs are mutually exclusive (i.e., they must not be present in the same message).¶
The format of SR Policy's PSID sub-TLV is specified as below:¶
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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Address Type | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ Headend (4/16 octets) ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Color (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ Endpoint (4/16 octets) ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type¶
This field is set to the value (TBD1) which indicates that it's an SR Policy's PSID sub-TLV.¶
Length¶
This field is set to the length of the sub-TLV in octets, not including the first 4 octets. If Headend and Endpoint fields are in IPv4 address format which is 4 octets long, it MUST be set to 16; If Headend and Endpoint fields are in IPv6 address format which is 16 octets long, it MUST be set to 40.¶
Address Type¶
This field is set to 1 when the Headend and Endpoint are both IPv4. This field is set to 2 when the Headend and Endpoint are both IPv6.¶
Reserved¶
The Reserved field MUST be set to 0 when sent and MUST be ignored on receipt.¶
Headend¶
Color¶
Endpoint¶
The format of SR Candidate Path's PSID sub-TLV is specified as below:¶
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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Address Type | Reserved1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ Headend (4/16 octets) ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Color (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ Endpoint (4/16 octets) ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Protocol-Origin| Reserved2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | | | Originator (20 octets) | | | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Discriminator (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type¶
This field is set to the value (TBD2) which indicates that it's an SR Candidate Path's PSID sub-TLV.¶
Length¶
This field is set to the length of the sub-TLV in octets, not including the first 4 octets. If Headend and Endpoint fields are in IPv4 address format which is 4 octets long, it MUST be set to 44; If Headend and Endpoint fields are in IPv6 address format which is 16 octets long, it MUST be set to 68.¶
Address Type¶
This field is set to 1 when the Headend and Endpoint are both IPv4. This field is set to 2 when the Headend and Endpoint are both IPv6.¶
Reserved1¶
The Reserved1 field MUST be set to 0 when sent and MUST be ignored on receipt.¶
Headend¶
Color¶
Endpoint¶
Protocol-Origin¶
The same as defined in Section 2.3 of [RFC9256]. This field takes a value from the IANA registry defined in Section 8.4 of [I-D.ietf-idr-bgp-ls-sr-policy]. If any unregistered value is used for this field, the validation at the responder would fail.¶
Reserved2¶
The Reserved2 field MUST be set to 0 when sent and MUST be ignored on receipt.¶
Originator¶
Discriminator¶
The format of SR Segment List's PSID sub-TLV is specified as below:¶
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 = TBD3 | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Address Type | Reserved1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ Headend (4/16 octets) ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Color (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ~ Endpoint (4/16 octets) ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Protocol-Origin| Reserved2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | | | | Originator (20 octets) | | | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Discriminator (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Segment-List-ID (4 octets) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type¶
This field is set to the value (TBD3) which indicates that it's an SR Segment List's PSID sub-TLV.¶
Length¶
This field is set to the length of the sub-TLV in octets, not including the first 4 octets. If Headend and Endpoint fields are in IPv4 address format which is 4 octets long, it MUST be set to 48; If Headend and Endpoint fields are in IPv6 address format which is 16 octets long, it MUST be set to 72.¶
Address Type¶
This field is set to 1 when the Headend and Endpoint are both IPv4. This field is set to 2 when the Headend and Endpoint are both IPv6.¶
Reserved1¶
The Reserved1 field MUST be set to 0 when sent and MUST be ignored on receipt.¶
Headend¶
Color¶
Endpoint¶
Protocol-Origin¶
The same as defined in Section 2.3 of [RFC9256]. This field takes a value from the IANA registry defined in Section 8.4 of [I-D.ietf-idr-bgp-ls-sr-policy]. If any unregistered value is used for this field, the validation at the responder would fail.¶
Reserved2¶
The Reserved2 field MUST be set to 0 when sent and MUST be ignored on receipt.¶
Originator¶
Discriminator¶
Segment-List-ID¶
This field identifies an SR path within the context of a candidate path of an SR Policy. The Segment-List-ID is a 4-octet identifier of a segment list.¶
The MPLS LSP Ping procedures may be initiated by the headend of the Segment Routing path or a centralized topology-aware data plane monitoring system as described in [RFC8403]. For the PSID, the responder nodes that receive echo request and send echo reply MUST be the endpoint of the Segment Routing path.¶
When an endpoint receives the LSP echo request packet with top FEC being the PSID, it MUST perform validity checks on the content of the PSID FEC Stack sub-TLV. The basic length check should be performed on the received FEC.¶
SR Policy's PSID
------------------
If Address Type = 1, Length should be 16 octets
If Address Type = 2, Length should be 40 octets
SR Candidate Path's PSID
------------------
If Address Type = 1, Length should be 44 octets
If Address Type = 2, Length should be 68 octets
SR Segment List's PSID
------------------
If Address Type = 1, Length should be 48 octets
If Address Type = 2, Length should be 72 octets
If a malformed FEC Stack sub-TLV is received, then a return code of 1, "Malformed echo request received" as defined in [RFC8029] MUST be sent. The section below is appended to the procedure given in step 4a of Section 7.4 of [RFC8287].¶
This is an example of Segment Routing PSID validation.¶
Else, if the Label-stack-depth is 0 and the Target FEC Stack sub-TLV FEC-stack-depth is TBD1 (SR Policy's PSID 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, matches with the responding fields in the received SR Policy's PSID 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 FEC-Status to 1 and return.¶
}¶
Else, if the Label-stack-depth is 0 and the Target FEC Stack sub-TLV FEC-stack-depth is TBD2 (SR Candidate Path's PSID 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, the PSID, matches with the corresponding fields in the received SR Candidate Path's PSID 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 FEC-Status to 1 and return.¶
}¶
Else, if the Label-stack-depth is 0 and the Target FEC Stack sub-TLV t FEC-stack-depth is TBD3 (SR Segment List's PSID 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, the PSID, matches with the corresponding fields in the received SR Segment List's PSID 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 FEC-Status to 1 and return.¶
}¶
When a sub-TLV defined in this document is carried in 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. 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.¶
This document defines additional MPLS LSP Ping sub-TLVs and follows the mechanisms defined in [RFC8029]. All the security considerations defined in Section 5 of [RFC8029] 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 is requested to assign three new sub-TLVs from the "Sub-TLVs for TLV Types 1, 16, and 21" sub-registry in the "TLVs" registry of the "Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters" name space. The Standards Action range that requires an error message to be returned if the sub-TLV is not recognized (range 0-16383) should be used.¶
Sub-Type Sub-TLV Name Reference -------- ------------------------- ---------------------------- TBD1 SR Policy's PSID Section 3.1 of THIS_DOCUMENT TBD2 SR Candidate Path's PSID Section 3.2 of THIS_DOCUMENT TBD3 SR Segment List's PSID Section 3.3 of THIS_DOCUMENT¶
The authors would like to acknowledge Loa Andersson, Detao Zhao, Ben Niven-Jenkins, Greg Mirsky, Ketan Talaulikar, James Guichard, Jon Geater, Gorry Fairhurst, Bing Liu, and Mohamed Boucadair for their thorough review and very helpful comments.¶
The authors would like to acknowledge Yao Liu and Quan Xiong for the very helpful f2f discussion.¶