RFC 8663: MPLS Segment Routing over IP
In plain English — editorial summary, not part of the RFC
MPLS Segment Routing (SR-MPLS) is a method of source routing a packet through an MPLS data plane by imposing a stack of MPLS labels on the packet to specify the path together with any packet-specific instructions to be executed on it. SR-MPLS can be leveraged to realize a source-routing mechanism across MPLS, IPv4, and IPv6 data planes by using an MPLS label stack as a source-routing instruction set while making no changes to SR-MPLS specifications and interworking with SR-MPLS implementations. This document describes how SR-MPLS-capable routers and IP-only routers can seamlessly coexist and interoperate through the use of SR-MPLS label stacks and IP encapsulation/tunneling such as MPLS-over-UDP as defined in RFC 7510.
Document record
- Document ID
- RFC8663
- Published
- December 2019
- Authors
- X. Xu; S. Bryant; A. Farrel; S. Hassan; W. Henderickx; Z. Li
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 17
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8661Segment Routing MPLS Interworking with LDPCurrent
December 2019
- RFC 8660Segment Routing with the MPLS Data PlaneCurrent
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?