metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 9545: Path Segment Identifier in MPLS-Based Segment Routing Networks

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC9545
Published
February 2024
Authors
W. Cheng; H. Li; C. Li; R. Gandhi; R. Zigler
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
11
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/9545-path-segment-identifier-in-mpls-based-segment-routing-networks