Search RFCs

RFC Editor

File formats:

Also available:XML file for editing

 

Status:

PROPOSED STANDARD

Authors:

W. Cheng, Ed.
H. Li
C. Li, Ed.
R. Gandhi
R. Zigler

Stream:

IETF

Source:

spring (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC9545

Discuss this RFC: Send questions or comments to the mailing listspring@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 9545

Abstract

A Segment Routing (SR) path is identified by an SR segment list. Asubset of segments from the segment list cannot be leveraged todistinguish one SR path from another as they may be partiallycongruent. SR path identification is a prerequisite for various usecases such as performance measurement and end-to-end 1+1 pathprotection.

In an SR over MPLS (SR-MPLS) data plane, an egress node cannotdetermine on which SR path a packet traversed the network from thelabel stack because the segment identifiers are removed from thelabel stack as the packet transits the network.

This document defines a Path Segment Identifier (PSID) to identify anSR path on the egress node of the path.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.