Multiprotocol Label Switching Architecture
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://ipfyi.com/iframe/entity//" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://ipfyi.com/entity//Add a dynamic SVG badge to your README or docs.
[](https://ipfyi.com/entity//)Use the native HTML custom element.
E. Rosen, A. Viswanathan, R. Callon · 2001-01
Abstract
RFC 3031 defines the MPLS architecture, in which short fixed-length labels are appended to packets and used to make forwarding decisions independently of the network-layer header. Label distribution protocols (LDP, RSVP-TE) signal label bindings between Label Switching Routers (LSRs) to create Label Switched Paths (LSPs). The architecture enables traffic engineering, fast reroute, and VPN services.
Why This RFC Matters
MPLS decoupled packet forwarding from IP longest-prefix lookup, enabling service providers to build high-speed, traffic-engineered backbones and VPN overlays. Technologies built on MPLS—RSVP-TE, LDP, L3VPN (RFC 4364), and Segment Routing—now carry the majority of global backbone traffic. The label stack concept also influenced later developments such as VXLAN and SR-MPLS in data-center networking.