There has been a lot of buzz recently about a second OAM (Operations, Administration, and Maintenance) solution for MPLS-TP that will cause interoperability problems between MPLS-TP and MPLS. It is accurate that there is an alternative OAM based on ITU-T Y.1731 (Ethernet OAM) proposed by a number of vendors and countries and indeed, it will cause interoperability issues. As a strong believer in standards, I certainly hope that a second approach does not occur because vendors and customers do not need the additional cost burden that a lack of interoperability causes. The fact is that only the draft recommendation for MPLS-TP OAM based on Y.1731 has begun the first step in a very long approval ITU process -- but nothing more – and in my estimates will take well over a year and could easily take up to two years to standardize. IETF MPLS OAM is widely deployed in MPLS networks today and will simply be extended as MPLS-TP is deployed as a next generation transport solution. In fact, recent interoperability testing of MPLS-TP took place at the MPLS World Congress earlier this month in Paris.
I believe that after careful consideration most operators will see the benefit of having a single end-to-end methodology to operate and manage converged packet optical transport networks, which MPLS-TP using MPLS OAM provides. Operators who select another method that is perceived to meet their short term needs now my ultimately learn that it fails to provide everything they had expected, and that having multiple OAM methods (one for Ethernet and another for MPLS) is not cost effective. It will be interesting to see what happens moving forward. At the very least, operators should make an informed decision on which approach is right for them.
Read More »
Tags: EANTC, ietf, interoperability, isocore, itu-t, light reading, mpls, MPLS OAM, MPLS-TP, Service Provider, standards, Study Group 15, Y.1731, Y1731
SONET and SDH, while well established and highly reliable technologies, were optimized for an era of TDM voice communications - before cloud computing, VoIP, cell phones, mobile tablets, Video CDNs and even the Internet increased network complexity and radically changed traffic patterns. This infrastructure has delivered reliable transport because it is easy to provision, troubleshoot, and provides a high level of resiliency. However, with the increase in IP traffic and changing traffic patterns, a new solution is required: one that provides the ‘trust’ of SONET/SDH with the ‘efficiency’ and ‘agility’ of packet.
Today Cisco is announcing our latest innovation, the Cisco Carrier Packet Transport (CPT) System. Our goal is to enable the transport network in a way that combines the reliability and simplicity of point-and-click provisioning of SONET/SDH along with the efficiency and flexibility of IP/MPLS.
Service providers generate a lot of revenue from connection-oriented services like leased lines. However the growth of these services from a revenue perspective is slow. New services based on cloud, mobile, and video are IP based and have huge growth potential. Service providers need to address this growing traffic and need to do so profitably. They need to find ways to lower the cost of transport and simultaneously tap into new applications that increase the average revenue per user. The Cisco Carrier Packet Transport System helps them do exactly that!
Of course, new technology can be overwhelming. So, it’s important to deliver all the benefits of packet technology without sacrificing the trust of transport. With the Cisco CPT System, service providers can build a packet transport infrastructure with the same reliability and familiar operational models of SONET/SDH. Standards-based MPLS-TP allows for robust packet connection-oriented control. Cisco’s Premier Integrated Management Experience (PRIME) offers service providers an A-Z point-and-click network management system. Both wavelengths and MPLS-TP label switch paths are provisioned in an easy “point-and-click” fashion autonomously or from a single integrated domain. This integrated solution provides opex savings and eliminates the need for overhaul and extensive employee re-training.
Read More »
Tags: carrier packet transport, cisco prime, cpt, CPT 200, CPT 50, CPT 600, DWDM, IP NGN, mpls, MPLS-TP, Optical, OTN, p-ots, packet-optical transport system, sdh, sonet
Well I am just recovering from a fantastic IETF-79 held in Beijing, PRC from November 7-12. I have to say that the MPLS Conference 2010, held in Washington D.C. from October 24-27 was a resounding success!
MPLS-TP was the hot topic at MPLS 2010 this year in Washington D.C. Cisco had a strong presence e.g. with seven Cisco distinguished engineer and technical lead presenters:
- Monique Morrow, Distinguished Engineer
- Luyuan Fang, Principal Engineer
- George Swallow, Distinguished Engineer
- Santiago Alvarez, Distinguished Engineer
- Azhar Sayeed, Director of Product Marketing
- Clarence Filsfils, Distinguished Engineer
- Zafar Ali, Technical Leader
Cisco had presentations on MPLS-TP, multicast, mobility, optical and cloud. Following, is my presentation from the Technical Sessions on Day 1
At this conference there was no question that MPLS-TP is the industry standard!
Read More »
Tags: inter-cloud, interoperability, isocore, mpls, MPLS-TP
IP services are dominating overall network traffic growth and service providers are now truly architecting a transition from legacy Time Division Multiplexing (TDM) networks to packet transport networks. It’s no longer a question of if, but when. The Transport Profile for MPLS or MPLS-TP is the packet transport technology of choice, marrying the efficiency and flexibility of packet with the robust characteristics of a traditional transport network. The telecommunications industry has embraced this emerging standard, mainly because it is subset of and interoperable with widely deployed IP/MPLS technology. To ensure this interoperability, it was collectively decided by both the ITU-T and IETF that the IETF will be responsible to define the protocol and functionality of MPLS-TP. The embeded spreadsheet specifies which RFCs have been completed and which contributions have been accepted and are in progress as Working Group drafts.
This vision is finally coming to fruition. For the first time since its inception, a standards-based interoperability test for MPLS-TP was conducted by Isocore. The results of this interoperability test were announced this week and demonstrate to the market the reality of a true MPLS-TP standard and that the vendor community is following and adopting this standard. The interoperability focused on showing how systems from multiple vendors can work together while enabling transport-like characteristics such as statically provisioned paths, protection switching, in band OAM and OAM verification. All of the capabilities tested have been defined in RFC 5860, RFC 5654, RFC 5586 and RFC 5921 which are currently published standards from the IETF.
Read More »
Tags: ietf, ietf working group, internet protocol, interoperability, isocore, itu-t, mpls, MPLS-TP, packet transport, rfc, Service Provider, standards
I am really excited about the MPLS Conference 2010 to be held in Washington D.C. next week.
Whilst we have a fantastic agenda of industry leaders who are scheduled to speak at the conference, Cisco in particular will be highly engaged starting with the Sunday, October 24th Tutorial on Mobile Packet Core with Azhar Sayeed, Cisco.
On Monday October 25th, Cisco’s Luyuan Fang will co-present with Nabil Bitar (Verizon) and Raymond Zhang (BT), on “MPLS-TP Deployment Scenarios and Design Considerations.”
I will present on “Network Enabled Cloud and Service Models.”
The day will end with a panel co-chaired by Dave McDysan (Verizon) and Deborah Brugnard (AT&T) that includes Cisco Distinguished Engineer, George Swallow to discuss MPLS-TP and Ethernet OAM, “Peaceful Co-Existence or Continuing Competition.”
Read More »
Tags: ethernet OAM, Mobile Packet Core tutorial, mpls, mpls 2010 conference, MPLS-TP, OTN