12/8/2015 draft-blb-mpls-tp-framework-01.txt A framework for MPLS in Transport networks draft-blb-mpls-tp-framework-01.txt Stewart Bryant (Cisco), Matthew Bocci (Alcatel- Lucent) & Lieven Levrau (Alcatel-Lucent) (Eds.)

12/8/2015 draft-blb-mpls-tp-framework-01.txt Objectives & Background Provide an architectural framework for MPLS-TP Overview of the key elements of MPLS-TP –Subset of existing MPLS concepts that fall into transport profile –New concepts required to meet MPLS-TP requirements First version introduced in Dublin

12/8/2015 draft-blb-mpls-tp-framework-01.txt Objectives of MPLS-TP 1.To enable MPLS to be deployed in a transport network and operated in a similar manner to existing transport technologies. 2.To enable MPLS to support packet transport services with a similar degree of predictability to that found in existing transport networks. 3.To create a common set of new functions that are applicable to both MPLS networks in general, and those belonging to the MPLS-TP profile.

12/8/2015 draft-blb-mpls-tp-framework-01.txt Changes in this version Clarified objectives of MPLS-TP Added figures from JWT report to illustrate: –MPLS-TP solution spectrum –MPLS-TP Architecture –Addressing in MPLS-TP –OAM architecture –Control plane architecture Added section on addressing: –Clarifies requirements (or otherwise) for IP in forwarding, OAM demux, and node identification –Default for general MPLS forwarding and OAM, but not required for MPLS-TP (e.g. use generic associate channel for OAM) – IP used for node identification Added security considerations

12/8/2015 draft-blb-mpls-tp-framework-01.txt Next Steps Consensus to move to WG draft? Received some comments on the list which we need to address –How much overlap in content with specific MPL-TP requirements and framework drafts? –Add architectural aspects of tandem connection monitoring Other comments from the list? Update draft to draft-ietf-mpls-tp-framework-00.txt