Enrique Hernandez-Valencia Director Network Architectures and Technologies Alcatel-Lucent enrique.hernandezalcatel-luce

2. Agenda Ethernet Network-to-Network Interface Scope and Objectives ENNI Attributes / Specifications ENNI, UTA and MEF Roadmap Multi-Provider Class of Service MEF 23 Scope and Objectives CoS Metrics MEF23.1 and MEF Roadmap

3. Key Initiative for the MEF for 2009-2011 MEF Global Interconnect Defined The interconnection of autonomous Carrier Ethernet networks to enable standardized and streamlined delivery of MEF-certified Carrier Ethernet services with end-to-end Class of Service, management and protection Strategic Opportunity for Broadband Service Providers Expand coverage Extend reach Broaden service offering Reduce costs MEF Global Interconnect Accelerate the implementation of standardized Ethernet interconnects throughout the industry Supporting the MEF’s mission of accelerating the worldwide adoption of Carrier-class Ethernet networks and services Deliver all elements relating to multi-operator implementation of MEF Carrier Ethernet services through a comprehensive informational program of Specifications Certification Operational ToolsAccelerate the implementation of standardized Ethernet interconnects throughout the industry Supporting the MEF’s mission of accelerating the worldwide adoption of Carrier-class Ethernet networks and services Deliver all elements relating to multi-operator implementation of MEF Carrier Ethernet services through a comprehensive informational program of Specifications Certification Operational Tools

4. What is the MEF ENNI? Detailed CEN-to-CEN interface specifications Final stages of ratification by MEF* Provides the key remaining element for standardized Ethernet interconnectivity among SPs Enables global delivery of MEF Carrier Ethernet services Specifications and certification for Carrier Ethernet services to enable delivery of fully featured MEF Carrier Ethernet services over multi-operator networks. A Reference Point where 2 Service Providers meet in support of specified MEF Services Technical functionally supported by equipment at the specified reference point in support of MEF Services (ENNI *Functional Element)Specifications and certification for Carrier Ethernet services to enable delivery of fully featured MEF Carrier Ethernet services over multi-operator networks. A Reference Point where 2 Service Providers meet in support of specified MEF Services Technical functionally supported by equipment at the specified reference point in support of MEF Services (ENNI *Functional Element)

5. ENNI Phase I Operator Virtual Connections - New service entity! E-LINE and E-LAN services (but not E-TREE) Includes “hair-pin” switching (e.g., frame may go in/out same PHY – NEW service option ENNI Link Protection (but not service protection) Customers & SP must provide loop-free connectivity Like APS with link aggregation (ala IEEE 802.3ad) End-to-End OAM and QoS Traffic “coloring” via IEEE PCPs or IETF DSCPs Support for MEF23 (CoS) Service Frame delineation via IEEE 802.1ad Encapsulation will have an S-Tag which reflects an EVC End Point Maps defined to concatenate OVCs across CENs Other frame formats may be added in future updates Link Protection Only Two Links -- Load balancing based on S-Tag Status – we are at draft 7 – letter ballot in Washington DC LSP between ENNI to another and map PWE – put the tunnel onto this and use VCCV tomake the reports Use .1ag and send CFM and send it into the PW and measure – Ethernet SLA (use our IP SLA engine to generate CFM instead of IP packets) IP SLA is more complicated and need to assign IP traffic and bridge it into the tunnelLink Protection Only Two Links -- Load balancing based on S-Tag Status – we are at draft 7 – letter ballot in Washington DC LSP between ENNI to another and map PWE – put the tunnel onto this and use VCCV tomake the reports Use .1ag and send CFM and send it into the PW and measure – Ethernet SLA (use our IP SLA engine to generate CFM instead of IP packets) IP SLA is more complicated and need to assign IP traffic and bridge it into the tunnel

6. ENNI Building Blocks: Operator Virtual Connection (OVC) Operator Virtual Connections (OVCs) associate UNIs and ENNIs in a CEN to support a given Ethernet Service instance Concatenation of OVCs are used to create EVCs OVCs can also be used to create other CEN to CEN Ethernet Services

7. ENNIs & OVCs ENNI Attributes: Per ENNI Attributes (aka ENNI link) Per OVC Attributes (aka ENNI service instance) Per OVC End Point Attributes at an ENNI (aka ENNI service endpoint) Per OVC End Point Attributes at an UNI (per MEF10.2)

8. ENNI Service Attributes Service: Type MTU Endpoint: Endpoint Maps Service Mux Tag ID/CoS Preservation Link: Rate L2CPs

9. Hairpin Switching

10. ENNI and MEF Roadmap ENNI Roadmap UNI Tunnel Service Rooted Multipoint connections Transit Tunnels New Encapsulation Protocol Types – MPLS, 802.1ah Security Attributes Layer2 Control Processing Performance Definition Service Protection & Resiliency Methods eg. Node protection, hold-off timers Separate MEF Projects Services OAM and Fault Management (SOAM –FM) Y.1731 Performance Configuration Fault Management (CFM) Only Two Links -- Load balancing based on S-Tag •    Mechanisms which allow multiple EVCs to be provisioned across an Operator's MEN without this Operator knowing the details of the EVCs it is transporting.?•    Additional physical layers.?•    Other encapsulation protocols e.g., MPLS, IEEE 802.1ah Provider Backbone Bridges, ?•    Security attributes.?•    Support for the Rooted Multipoint EVC.?•    Additional protection methods, e.g., node protection and hold off timers.?•    Layer 2 Control Protocol processing.?•    Performance definitions.Only Two Links -- Load balancing based on S-Tag •    Mechanisms which allow multiple EVCs to be provisioned across an Operator's MEN without this Operator knowing the details of the EVCs it is transporting.?•    Additional physical layers.?•    Other encapsulation protocols e.g., MPLS, IEEE 802.1ah Provider Backbone Bridges, ?•    Security attributes.?•    Support for the Rooted Multipoint EVC.?•    Additional protection methods, e.g., node protection and hold off timers.?•    Layer 2 Control Protocol processing.?•    Performance definitions.

11. UTAS Constructs: VUNI, RUNI ENNI extension defining requirements for UNI Tunnel Access Service (UTAS) which connects the Virtual UNI (VUNI) and Remote UNI (RUNI) UTAS associate a VUNI and an RUNI VUNI is the Logical interface at endpoint of E-NNI side of UTAS which Maps CEVC(s) to its UTAS RUNI is a Logical interface at end point of UNI side of the UTAS

12. UTAS Constructs: Putting it Together

13. Rooted Multipoint Connections Define two new endpoint types: Trunk: Receives from Root and Trunk ; Delivers to Leaf, Root, and Trunk Branch: Receives from Leaf and Branch ; Delivers to Root and Branch Each E-NNI has a pair of Trunk and Branch End Points Issues addressed: Eliminated UNI black-hole depending Leaf/Root UNI location wrt ENNI Compatible with either IEEE 802.1Q bridges or VPLS based networks

14. Global Interconnect In-depth, Part 1MEF 23: Multi-Provider Class of Service Implementation Options

15. Introduction to MEF 23 - CoS The Motivation for MEF 23 - to introduce and define specific “classes” or CoS that will receive a commitment for a particular level of performance for a set of Service Frames (e.g., those belonging to a particular application) from the Service Provider for further development of Carrier Ethernet services that are interoperable and predictably support subscriber applications. Several definitions for Several definitions for

16. Scope & Applicability

17. MEF 23 in a Nutshell Carrier Ethernet CoS Implementation Agreement Phase 1 Specifies a 3 CoS Model and allows for subsets and extensions Provides Guidance for interconnections of CENs with 3 CoS Models vs 2 CoS Model CoS IA PCP or DSCP values recommended for UNI CoS IA S-tag PCP values mandatory for ENNI PCP/DSCP mandatory values are subset of the total value Guidance on Bandwidth Profile constraints Includes consideration for frame disposition (i.e., Color) Performance Objectives for FD, IFDV/FDV and FLR positioned as placeholders (define in MEF Phase 2) Quantification in future phase (will likely add MFD and FDR) May vary for Point to Point vs Multipoint EVC types Positions for future certification PCP (8 values) – Priority Control Point – Ethernet DSCP (64 values) – Differentiated Services Control Point EVC/VLAN Tag ID – defines priority and not use PCP in 10.1 MEF spec FD = Frame Delay IFDV = Interconnect Frame Delay Variation FLR = Frame Delay Range MFD = Measured Frame Delay PCP (8 values) – Priority Control Point – Ethernet DSCP (64 values) – Differentiated Services Control Point EVC/VLAN Tag ID – defines priority and not use PCP in 10.1 MEF spec FD = Frame Delay IFDV = Interconnect Frame Delay Variation FLR = Frame Delay Range MFD = Measured Frame Delay

18. Three CoS Model 1 Full CoS Identifier includes EVC. Table specifies only the PCP or DSCP values to be used with EVC. EVC indication is not constrained by CoS IA. 2 The Color Yellow column values are N/A when DEI is used to represent Color at the E-NNI. 3 CBS, EBS, Color Mode and Coupling Flag BWP parameters are not addressed in this table. 4 EIR is not constrained though EIR=0 assumed since not specifying Color Yellow PCP and DSCP for CoS Label H. Relaxation of EIR constraint is for applications such as Mobile Backhaul (see Mobile Backhaul example use case in Appendix). 5 Both CIR and EIR = 0 is not allowed as this would result in no conformant Service Frames. Note: Separate rows for Point-to-Point and Multipoint for each CoS Label to allow for different Performance Objectives for each as denoted by the prime (?). Multipoint also includes Rooted Multipoint as per [2]. Color Green – in contract Color yellow – out of contract Color Red – drop EF = Expedited Forward AF = Assured Forwarding PHB = Per hop behavior H = Realtime M = data L = best effort Color Aware = knowledge of the customer priority before it hit interface (don’t make it higher) Color Blind = no knowledge of customer priority Stag = MEF COS mandatory for ENNI; recommended for UNI 1 Full CoS Identifier includes EVC. Table specifies only the PCP or DSCP values to be used with EVC. EVC indication is not constrained by CoS IA. 2 The Color Yellow column values are N/A when DEI is used to represent Color at the E-NNI. 3 CBS, EBS, Color Mode and Coupling Flag BWP parameters are not addressed in this table. 4 EIR is not constrained though EIR=0 assumed since not specifying Color Yellow PCP and DSCP for CoS Label H. Relaxation of EIR constraint is for applications such as Mobile Backhaul (see Mobile Backhaul example use case in Appendix). 5 Both CIR and EIR = 0 is not allowed as this would result in no conformant Service Frames. Note: Separate rows for Point-to-Point and Multipoint for each CoS Label to allow for different Performance Objectives for each as denoted by the prime (?). Multipoint also includes Rooted Multipoint as per [2]. Color Green – in contract Color yellow – out of contract Color Red – drop EF = Expedited Forward AF = Assured Forwarding PHB = Per hop behavior H = Realtime M = data L = best effort Color Aware = knowledge of the customer priority before it hit interface (don’t make it higher) Color Blind = no knowledge of customer priority Stag = MEF COS mandatory for ENNI; recommended for UNI

19. Class of Service Alignment [MEF 23] Solving the problem of Class of Service spanning two or more Service Providers requires: Common Class of Service lexicon between the service providers on either side of the standardized Ethernet interconnect CENs may implement different number of CoS Alignment of the respective Classes of Service at the ENNI The Motivation for MEF 23 - to introduce and define specific “classes” or CoS that will receive a commitment for a particular level of performance for a set of Service Frames (e.g., those belonging to a particular application) from the Service Provider for further development of Carrier Ethernet services that are interoperable and predictably support subscriber applications. The Motivation for MEF 23 - to introduce and define specific “classes” or CoS that will receive a commitment for a particular level of performance for a set of Service Frames (e.g., those belonging to a particular application) from the Service Provider for further development of Carrier Ethernet services that are interoperable and predictably support subscriber applications.

20. Mapping the CoS Model at an ENNI

21. Example PCP Mappings

22. CoS & MEF Roadmap: Performance Objectives Geographic Tiers (GT) and CPO values GT is a CEN, set of CENs or domain within a CEN, for which specific service instances and associated MEF CoS Performance Objectives (CPOs) apply Different GTs may provide different CPOs Metro (250km), Regional (1200km), National (7000km), Global/Intercontinental (27500 km) Ethernet Services adherence to GT distance basis not required (only a basis for deriving CPOs) Up to 4 GTs envisioned

23. Geographic Tier (GT) and Network Section (ENS) Example

25. Summary Carrier Ethernet continues its fast growth as technology and service. ENNI Provides the key remaining element for standardized Ethernet interconnectivity and enables delivery of MEF Carrier Ethernet services. MEF CoS IA provides a common set of CoS the Operators can map frames into to facilitate interworking and introduces and defines specific “classes” to achieve a commitment for a particular level of performance. Implementation of Ethernet interconnects has begun and will rapidly accelerate in 2010

26. Accelerating Worldwide Adoption of Carrier-class Ethernet Networks and Services