RFC 9884: Label Switched Path Ping for Segment Routing Path Segment Identifier with MPLS Data Plane
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9884
- Published
- October 2025
- Authors
- X. Min; S. Peng; L. Gong; R. Gandhi; C. Pignataro
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9885Multi-Part TLVs in IS-ISCurrent
October 2025
- RFC 9889A Realization of Network Slices for 5G Networks Using Current IP/MPLS TechnologiesCurrent
November 2025
- RFC 9892Dynamic Link Exchange Protocol (DLEP) Traffic Classification Data ItemCurrent
January 2026
- RFC 9893Dynamic Link Exchange Protocol (DLEP) Credit-Based Flow Control Messages and Data ItemsCurrent
January 2026
- RFC 9894Dynamic Link Exchange Protocol (DLEP) Diffserv Aware Credit Window ExtensionCurrent
January 2026
- RFC 9895Dynamic Link Exchange Protocol (DLEP) IEEE 802.1Q Aware Credit Window ExtensionCurrent
January 2026
- RFC 9871BGP Color-Aware Routing (CAR)Current
November 2025
- RFC 9866Root Node Failure Detector (RNFD): Fast Detection of Border Router Crashes in the Routing Protocol for Low-Power and Lossy Networks (RPL)Current
October 2025
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?