July 2018 • 7 min read
Understanding MPLS Traffic Engineering
Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) emerged as a core mechanism in the early 2000s to optimize path utilization and route traffic based on constraints like bandwidth, delay, and administrative preference. Carriers adopted MPLS TE extensively to overcome limitations in traditional IGP-based shortest path routing.
TE Viability in 2018
As of 2018, MPLS TE remains a viable solution, especially in legacy environments where hardware investments and operational models still rely on RSVP-TE. In such settings, path predictability and granular control remain key requirements. However, several challenges persist:
- RSVP-TE complexity in maintaining soft state and scalability across large backbones
- Operational overhead in provisioning and adjusting tunnels
- Limited interoperability across multi-vendor deployments
Segment Routing as a Disruptor
Segment Routing (SR) begins disrupting traditional TE approaches by enabling source-based routing and reducing control plane overhead. By encoding path instructions in packet headers, SR eliminates the need for per-flow state in the core. Combined with centralized SDN controllers, SR offers scalable and dynamic TE.
Comparing Use Cases
MPLS TE and SR address similar problems—optimal path selection, SLA enforcement, and failure recovery—but they differ in execution. In 2018, use cases for MPLS TE still dominate in networks with deep legacy investments or where control plane change is slow. Meanwhile, SR sees adoption in greenfield deployments and SDN pilots.
Operational Considerations
Network teams face a critical decision: continue maintaining RSVP-TE or begin transitioning to SR. Migration strategies include hybrid models, where RSVP-TE coexists with SR-TE to gradually phase out older mechanisms. Operators also explore intent-based networking where path constraints derive from policy rather than CLI configuration.
Vendor and Standards Landscape
Cisco, Juniper, and Nokia all offer robust MPLS TE and SR implementations. IETF support for SRv6, Path Computation Elements (PCE), and telemetry enhancements continues to strengthen the SR roadmap. TE in 2018 is no longer about whether to do it—but how to do it with less friction and more intelligence.
Final Thoughts
MPLS TE has served the industry well for nearly two decades. Yet, with SDN maturity and Segment Routing momentum, traditional TE sees diminishing returns. As 2018 progresses, network architects must evaluate when and how to shift toward simpler, more scalable TE architectures that align with evolving business needs.
No comments:
Post a Comment