Multiprotocol Label Switching (MPLS)
Multiprotocol Label Switching · Also known as: label switching, traffic engineering
Multiprotocol Label Switching (MPLS) is a forwarding paradigm that prepends a short label to packets, enabling routers to make forwarding decisions based on the label rather than IP destination address. Introduced by IETF (2001), MPLS was designed to enable traffic engineering, VPN creation, and fast rerouting in IP networks. While MPLS complexity is high, it remains foundational in service provider backbones for traffic engineering and Quality of Service (QoS) provisioning.
Read the full method
Sign in with a free account to read this section.
Method map
The neighbourhood of related methods — select a node to explore.
When to use it
Use MPLS in service provider networks for traffic engineering and VPN provisioning. MPLS is valuable when LSP-based routing (engineering paths explicit paths) offers advantages over dynamic IP routing. Avoid MPLS in small networks; operational complexity is high. For SDN-based traffic engineering, MPLS combined with controller-driven LSP setup (segment routing) is effective.
Strengths & limitations
- Traffic engineering: explicit path control enables load balancing and congestion avoidance
- Fast rerouting: precomputed backup LSPs enable sub-50 ms failover
- VPN support: MPLS LDP/BGP enables provider-provisioned VPNs (MPLS/BGP VPN)
- Protocol independence: label-based forwarding works with any IP version or protocol
- Fast lookup: label-based lookup is O(1), faster than IP prefix matching
- QoS integration: label values can encode QoS class, enabling per-class prioritization
- Operational complexity: MPLS configuration and troubleshooting require expertise
- Packet overhead: MPLS header adds 4+ bytes to every packet
- Scalability: managing thousands of LSPs becomes complex; state explosion risk
- Limited visibility: packet labels obscure content from monitoring and security tools
- Deployment maturity: MPLS is mature in service provider networks but uncommon in enterprises
Frequently asked
What is a forwarding equivalence class (FEC)?
An FEC is a set of packets receiving the same treatment (routing, QoS) and thus sharing the same LSP. An FEC is defined by match criteria (IP destination prefix, IP protocol, port) or more granularly (per-flow FEC).
How is an LSP established?
LSPs are established using label distribution protocols (LDP, RSVP-TE). LDP uses hop-by-hop routing to build LSPs. RSVP-TE allows ingress routers to explicitly specify the path, enabling traffic engineering.
What is segment routing (SR)?
Segment routing simplifies MPLS by encoding paths in packet headers without requiring per-LSP state at every hop. Ingress router pushes segment IDs (labels) onto the stack; each hop pops the top label and forwards. This reduces operational complexity significantly.
Why is MPLS less common in data centers than ISP networks?
Data centers prioritize simplicity and speed of deployment. MPLS adds complexity without clear benefit in data center environments. SDN and segment routing offer similar capabilities with less overhead. However, MPLS-based VPNs are still used for connecting geographically distributed data centers.
Sources
How to cite this page
ScholarGate. (2026, June 3). Multiprotocol Label Switching. ScholarGate. https://scholargate.app/en/telecommunications/mpls
Which method?
Set this method beside its closest kin and read them side by side — the library lays the books on the table; the choice is yours.
- BGPTelecommunications↔ compare
- DiffServTelecommunications↔ compare
- OSPFTelecommunications↔ compare
- Software-Defined NetworkingTelecommunications↔ compare