Large operators have embraced multiprotocol label switching, deploying it in their backbone networks to enable a number of services and applications such as virtual private networks to just name one. Since the inception of the respective IETF working group, MPLS has accumulated a number of features and has been extended to be applicable in new contexts such as optical networks in the form of generalized MPLS. Currently, MPLS is being further extended to finally mature into a technology from which to build a full-fledged packet transport network that fulfills a large number of traditional transport network requirements. Having celebrated the early teens of MPLS in 2009, the IETF might well find itself celebrating MPLS's coming of age with the completion of the MPLS Transport Profile (MPLS-TP). This article is a short tutorial on what MPLS-TP is, how it came about, and what it promises to deliver in the future.
[1]
Eric C. Rosen,et al.
Multiprotocol Label Switching Architecture
,
2001,
RFC.
[2]
David Thaler,et al.
What Makes for a Successful Protocol?
,
2008,
RFC.
[3]
Stewart Bryant,et al.
A Framework for MPLS in Transport Networks
,
2010,
RFC.
[4]
Stewart Bryant,et al.
MPLS Generic Associated Channel
,
2009,
RFC.
[5]
Ina Minei,et al.
LDP Specification
,
2007,
RFC.
[6]
Scott Mansfield,et al.
Network Management Requirements for MPLS-based Transport Networks
,
2010,
RFC.
[7]
Vijay Srinivasan,et al.
RSVP-TE: Extensions to RSVP for LSP Tunnels
,
2001,
RFC.
[8]
Deborah Brungard,et al.
Requirements of an MPLS Transport Profile
,
2009,
RFC.
[9]
David Ward,et al.
Requirements for Operations, Administration, and Maintenance (OAM) in MPLS Transport Networks
,
2010,
RFC.