MPLS-TP, is a set of MPLS protocols that are still being discussed in IETF. It is supposedly a stripped down, "simplified" version of MPLS for transport networks with some of the original MPLS functions turned off: For xample, Penultimate Hop Popping (PHP), Label-Switched Paths (LSPs) merge, and Equal Cost Multi Path (ECMP).
MPLS-TP does not require MPLS control plane capabilities and enables the management plane to set up LSPs manually. Its OAM may operate without any IP layer functionalities.
An example of implementation is Cisco's Carrier Packet Transport (CPT) System, where Service providers can consider implementing industry’s first, standards-based Packet Optical Transport System (P-OTS) that unifies packet and transport technologies using MPLS-TP.
Benefits as quoted by Cisco:
To summarise, the main properties of MPLS-TP defined by IETF and ITU-T are:
The current general consensus seems to tend towards "The market will ultimately decide which is the right approach for MPLS-TP OAM."
Well, I guess we will wait and see :-)
MPLS-TP does not require MPLS control plane capabilities and enables the management plane to set up LSPs manually. Its OAM may operate without any IP layer functionalities.
An example of implementation is Cisco's Carrier Packet Transport (CPT) System, where Service providers can consider implementing industry’s first, standards-based Packet Optical Transport System (P-OTS) that unifies packet and transport technologies using MPLS-TP.
Benefits as quoted by Cisco:
- Provides standards-based transport technologies and familiar operational models. Service providers can use a single unified interface for point-and-click provisioning of wavelengths and MPLS-TP label switch paths.
- Simplifies the network by combining multiple functions into one. Service providers can reduce the number of network elements and interconnect ports by combining functions such as ROADM, TDM/OTN switching, Ethernet, and MPLS-TP in a single platform, drastically reducing space and power consumption, thus enabling greener networks.
- Supports a comprehensive set of packet services for mobile backhaul, legacy TDM, Ethernet, and fiber services targeted at business and residential customers.
- Enables an integrated IP/MPLS and MPLS-TP architecture with a single control plane and forwarding mechanism. This provides OpEx savings and allows service providers to set up simple connection-oriented paths for point-to-point or point-to-multipoint connections with in-band operations, administration, and management (OAM) and sub-50 millisecond automatic protection switching.
To summarise, the main properties of MPLS-TP defined by IETF and ITU-T are:
- MPLS forwarding plane with restrictions
- PWE3 Pseudowire architecture
- Control Plane: static or dynamic Generalized MPLS (G-MPLS)
- Enhanced OAM functionality
- OAM monitors and drives protection switching
- Use of Generic Associated Channel (G-ACh) to support fault, configuration, accounting, performance, and security (FCAPS) functions
- Multicasting is under further study
There is still a bit of discussion up in the air, especially about the OAM part. For example, here's some insight from Mike Capuano's blog: http://blogs.cisco.com/sp/there-is-no-split-standard-in-mpls-oam/
The current general consensus seems to tend towards "The market will ultimately decide which is the right approach for MPLS-TP OAM."
Well, I guess we will wait and see :-)
3 comments:
Thank you for sharing this detailed summary.
You are most welcome! Thanks for taking the time to read!
Santanu
Post a Comment