RFC 8661: Segment Routing MPLS Interworking with LDP
In plain English — editorial summary, not part of the RFC
A Segment Routing (SR) node steers a packet through a controlled set of instructions, called segments, by prepending the packet with an SR header. A segment can represent any instruction, topological or service based. SR allows enforcing a flow through any topological path while maintaining per-flow state only at the ingress node to the SR domain. The Segment Routing architecture can be directly applied to the MPLS data plane with no change in the forwarding plane. This document describes how Segment Routing MPLS operates in a network where LDP is deployed and in the case where SR-capable and non-SR-capable nodes coexist.
Document record
- Document ID
- RFC8661
- Published
- December 2019
- Authors
- A. Bashandy; C. Filsfils; S. Previdi; B. Decraene; S. Litkowski
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8660Segment Routing with the MPLS Data PlaneCurrent
December 2019
- RFC 8663MPLS Segment Routing over IPCurrent
December 2019
- RFC 9256Segment Routing Policy ArchitectureCurrent
July 2022
- RFC 9801Private Line Emulation over Packet Switched NetworksCurrent
July 2025
- RFC 9857Advertisement of Segment Routing Policies Using BGP - Link StateCurrent
October 2025
- RFC 9860Multicast-Only Fast Reroute (MoFRR) Based on Topology Independent Loop-Free Alternate (TI-LFA) Fast RerouteCurrent
October 2025
- RFC 8662Entropy Label for Source Packet Routing in Networking (SPRING) TunnelsCurrent
December 2019
- RFC 8664Path Computation Element Communication Protocol (PCEP) Extensions for Segment RoutingUpdated
December 2019
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?