1. Nov 2009 draft-ietf-mpls-tp-framework-06.txt A framework for MPLS in Transport networks draft-ietf-mpls-tp-framework-06.txt Stewart Bryant (Cisco), Matthew Bocci (Alcatel-Lucent) (Eds.) Lieven Levrau (Alcatel-Lucent) Dan Frost (Cisco)

2. Nov 2009 draft-ietf-mpls-tp-framework-06.txt Objectives of the MPLS-TP Framework Provide a high level overview of the functional components of MPLS that can be used for a packet transport service, as per RFC5654 Presents an architectural framework to illustrate how those components fit together Implementations can choose which functions to use as applicable to their role in a network A specific implementation does not necessarily need all functions

3. Nov 2009 draft-ietf-mpls-tp-framework-06.txt Changes Since IETF 75 Major rewrite to align with ongoing debate on MPLS-TP architecture and improve readability Expanded terminology section: –MPLS Transport Profile and its relationship to MPLS –MPLS-TP LSP, PE, P and CE Removed P2MP content –This will be covered in a separate draft

4. Nov 2009 draft-ietf-mpls-tp-framework-06.txt Changes since IETF 75 Clarified applicability / scope of MPLS-TP Architecture now split into Adaptation and Forwarding Functions Clients: –Includes Pseudowires and Network Layer Protocols (IP and MPLS) Alignment of sections covering OAM with OAM framework draft. Currently under review by ITU-T

5. Nov 2009 draft-ietf-mpls-tp-framework-06.txt Scope of MPLS-TP Existing MPLS RFCs prior to RFC5654 ECMP LDP / non-TE LSPs IP forwarding MPLS-TP Subset to meet transport network operational requirements MPLS/PWE3 architecture MPLS forwarding GMPLS/PWE3 control MPLS Additional functionality based on Transport Requirements

6. Nov 2009 draft-ietf-mpls-tp-framework-06.txt MPLS-TP Clients Extensive discussion on the list about which clients are applicable, and how they fit into the MPLS-TP architecture Pseudowires: –PW used for services defined by L2VPN –SS-PW and MS-PW supported –MS-PW only needed if required as per RFC5254 Network Layer Clients: –IP and MPLS –Detailed architecture described –Use service label to demux network layer client –Optional Encapsulation label indicates protocol

7. Nov 2009 draft-ietf-mpls-tp-framework-06.txt MPLS-TP clients Service implemented using LSP –anything that MPLS can support: LSP, IP, PW Service implemented using PW –anything that PW can support Data-plane behaviour matches best current practice that MPLS and PW data plane supports today

8. Nov 2009 draft-ietf-mpls-tp-framework-06.txt MPLS-TP - Client relationship LSP label S=1 IP PW label S=1 LSP label S=0 PW Payload LSP label* S=1 LSP label S=0 LSP Payload MPLS-TP layer Client layer Labelled service PW-based service - PW-based service includes packet PW if desired - Label stacks are those inside MPLS-TP network - Label stacks shown are the smallest no. labels possible. These could include more labels. *Could be NULL IP service

9. Nov 2009 draft-ietf-mpls-tp-framework-06.txt Next Steps Address ITU-T feedback and further comments from IETF participants Align OAM, control plane and survivability sections with their respective framework drafts, and where possible simplify content ….then WG last call?