Carrier Ethernet, Interconnect Exchange Workshop

1. Carrier Ethernet, Interconnect & Exchange Workshop

2. ENNI & Access Services

4. Topics ENNI and Access Services Interconnect-related�Specifications � how they fit together MEF 26 Overview: External Network to Network Interface ( ENNI) MEF Access Service definitions work in progress

5. Interconnect Technical Components Interconnect elements required to enable globally connected Carrier Ethernet services ENNI provides the key remaining element for standardized Ethernet interconnectivity and enables delivery of MEF Carrier Ethernet services External Network to Network Interface (ENNI) - - Defines the Reference Point where 2 Service Providers meet in support of specified MEF Services And includes the demarcation/peering points between: - Ethernet Service Provider (ESP) and Access Network Provider, and an Ethernet Service Provider and Transport (Long Haul) Network Provider The ENNI work includes specifications and certification for Carrier Ethernet services to enable delivery of fully featured MEF Carrier Ethernet services over multi-operator networks. ============================ A-end UNI to Z-end UNI across ENNI ENNI provides the key remaining element for standardized Ethernet interconnectivity and enables delivery of MEF Carrier Ethernet services External Network to Network Interface (ENNI) - - Defines the Reference Point where 2 Service Providers meet in support of specified MEF Services And includes the demarcation/peering points between: - Ethernet Service Provider (ESP) and Access Network Provider, and an Ethernet Service Provider and Transport (Long Haul) Network Provider The ENNI work includes specifications and certification for Carrier Ethernet services to enable delivery of fully featured MEF Carrier Ethernet services over multi-operator networks. ============================ A-end UNI to Z-end UNI across ENNI

6. Completed Interconnect Related Standards The Global Interconnect program is a key initiative for the MEF for the next several years. The Global Interconnect initiative is the third phase of developing the Carrier Ethernet suite. Phase 1 being Architecture and Definition, Phase 2 being Implementation and Certification. Operators have been establishing interconnects as needed in recent years, and the MEF goal is to bring standardization to the process � ultimately benefiting the enterprise customers with a consistent global service delivery. 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 �Globalize our network� The Global Interconnect program is a key initiative for the MEF for the next several years. The Global Interconnect initiative is the third phase of developing the Carrier Ethernet suite. Phase 1 being Architecture and Definition, Phase 2 being Implementation and Certification. Operators have been establishing interconnects as needed in recent years, and the MEF goal is to bring standardization to the process � ultimately benefiting the enterprise customers with a consistent global service delivery. 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 �Globalize our network�

7. Standards in Progress The Global Interconnect program is a key initiative for the MEF for the next several years. The Global Interconnect initiative is the third phase of developing the Carrier Ethernet suite. Phase 1 being Architecture and Definition, Phase 2 being Implementation and Certification. Operators have been establishing interconnects as needed in recent years, and the MEF goal is to bring standardization to the process � ultimately benefiting the enterprise customers with a consistent global service delivery. 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 �Globalize our network� The Global Interconnect program is a key initiative for the MEF for the next several years. The Global Interconnect initiative is the third phase of developing the Carrier Ethernet suite. Phase 1 being Architecture and Definition, Phase 2 being Implementation and Certification. Operators have been establishing interconnects as needed in recent years, and the MEF goal is to bring standardization to the process � ultimately benefiting the enterprise customers with a consistent global service delivery. 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 �Globalize our network�

8. The Scope of MEF 26 The goal of ENNI is to provide a standard approach to implementing Ethernet Services as specified in MEF 10.2 and MEF 6.1 among UNIs that are supported by different Operator MENs The goal of ENNI is to provide a standard approach to implementing Ethernet Services as specified in MEF 10.2 and MEF 6.1 among UNIs that are supported by different Operator MENs

9. ENNI Baseline (MEF26)

10. 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

11. MEF 28 UNI Tunnel Access Service An ENNI extension defining requirements for UNI Tunnel Access Service (UTA) which connects the Virtual UNI (VUNI) and Remote UNI (RUNI) - UTA associates the 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 ENNI Tunneling for Multi-SP/Operators Ethernet Access Provider Provides OVC1 connection between Subscriber UNI1 (RUNI) and ENNI1 with Transport Network Provider Ethernet Transport Provider Provides OVC2 connection between ENNI1 and ENNI2 with Ethernet Service Provider Ethernet Service Provider Provides connection to ENNI2 with Transport Network Provider Provides End-to-End Ethernet Service to Subscriber Connects VUNI to UTA Provides EVC between UNI1 and UNI2 An ENNI extension defining requirements for UNI Tunnel Access Service (UTA) which connects the Virtual UNI (VUNI) and Remote UNI (RUNI) - UTA associates the 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 ENNI Tunneling for Multi-SP/Operators Ethernet Access Provider Provides OVC1 connection between Subscriber UNI1 (RUNI) and ENNI1 with Transport Network Provider Ethernet Transport Provider Provides OVC2 connection between ENNI1 and ENNI2 with Ethernet Service Provider Ethernet Service Provider Provides connection to ENNI2 with Transport Network Provider Provides End-to-End Ethernet Service to Subscriber Connects VUNI to UTA Provides EVC between UNI1 and UNI2

12. MEF 23 Class of Service Alignment 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. 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. 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

13. Slide is a duplicate of slide 9, but need a top-level concept layout. This clearly shows link vs. service OAM.Slide is a duplicate of slide 9, but need a top-level concept layout. This clearly shows link vs. service OAM.

14. Link OAM From an OAM perspective there are several standards that work together in a layered fashion to provide Ethernet OAM. IEEE 802.3ah was the first and provides link level OAM. With more of an end to end focus, 802.1ag provides a connectivity fault management layer for identifying network faults, while ITU Y.1731 adds a performance management which enables SLAs to be monitored. These layers are implemented in a network interface device or NID which can be a standalone device or integrated into other equipment. There is a great deal of commonality between these standards, especially between 802.1ag and Y.1731. From an OAM perspective there are several standards that work together in a layered fashion to provide Ethernet OAM. IEEE 802.3ah was the first and provides link level OAM. With more of an end to end focus, 802.1ag provides a connectivity fault management layer for identifying network faults, while ITU Y.1731 adds a performance management which enables SLAs to be monitored. These layers are implemented in a network interface device or NID which can be a standalone device or integrated into other equipment. There is a great deal of commonality between these standards, especially between 802.1ag and Y.1731.

15. Y.1731 Message Based Performance Measurements Delay Measurement (DM), Delay Variation Measurement (DVM) Loss Measurement (LM) Measurements end-to-end, NIDs at the customer UNI Delay measurement: DMM sends timetag, DMR reflects the timetag; the difference represents the round-trip delay Loss measurement: LMM sends TX, LMR reflects the TX (as unique ID) plus adds TX, RX; compare delta in TX and RX to detect frame loss. Maintenance End Points (MEP) � End Points of the MA Maintenance Intermediate Points (MIP) � Intermediate Points within MA A flat network is difficult to manage and define accountabilities Hierarchical Maintenance Domains define OAM Flows and OAM responsibilities Maintenance Domain (MD) � A level of monitoring within the hierarchy Maintenance Association (MA) � Boundaries of an Administrator�s scope of monitoring part of the network Delay measurement: DMM sends timetag, DMR reflects the timetag; the difference represents the round-trip delay Loss measurement: LMM sends TX, LMR reflects the TX (as unique ID) plus adds TX, RX; compare delta in TX and RX to detect frame loss. Maintenance End Points (MEP) � End Points of the MA Maintenance Intermediate Points (MIP) � Intermediate Points within MA A flat network is difficult to manage and define accountabilities Hierarchical Maintenance Domains define OAM Flows and OAM responsibilities Maintenance Domain (MD) � A level of monitoring within the hierarchy Maintenance Association (MA) � Boundaries of an Administrator�s scope of monitoring part of the network

16. SOAM Performance Management Ethernet OAM Ethernet Local Management Interface � E-LMI Point-to-Point Link OAM (802.3ah) End-to-End Service Connectivity Fault OAM (802.1ag) End-to-End Service Performance Monitoring OAM (Y.1731) From an OAM perspective there are several standards that work together in a layered fashion to provide Ethernet OAM. IEEE 802.3ah was the first and provides link level OAM. With more of an end to end focus, 802.1ag provides a connectivity fault management layer for identifying network faults, while ITU Y.1731 adds a performance management which enables SLAs to be monitored. These layers are implemented in a network interface device or NID which can be a standalone device or integrated into other equipment. There is a great deal of commonality between these standards, especially between 802.1ag and Y.1731. Benefits: Enable quick turn-up � Acct acquisition/revenue Increase reliability/up-time � Acct retention/revenue Enables SLA commitments � Keep revenue Enable efficient service operation / maintenance (man/machine/time/energy) � reduce OPEX Ethernet OAM Ethernet Local Management Interface � E-LMI Point-to-Point Link OAM (802.3ah) End-to-End Service Connectivity Fault OAM (802.1ag) End-to-End Service Performance Monitoring OAM (Y.1731) From an OAM perspective there are several standards that work together in a layered fashion to provide Ethernet OAM. IEEE 802.3ah was the first and provides link level OAM. With more of an end to end focus, 802.1ag provides a connectivity fault management layer for identifying network faults, while ITU Y.1731 adds a performance management which enables SLAs to be monitored. These layers are implemented in a network interface device or NID which can be a standalone device or integrated into other equipment. There is a great deal of commonality between these standards, especially between 802.1ag and Y.1731. Benefits: Enable quick turn-up � Acct acquisition/revenue Increase reliability/up-time � Acct retention/revenue Enables SLA commitments � Keep revenue Enable efficient service operation / maintenance (man/machine/time/energy) � reduce OPEX

17. SOAM Fault Management & FM MIB SOAM Fault Management Implementation Agreement Defines the Framework for Service OAM. Provides mechanisms to detect, verify, isolate and report end-to-end Ethernet connectivity faults Continuity Check, Remote Defect Indication Signal, Loopback, Linktrace, Alarm Indication Signal, Locked Signal, Test Signal SOAM Fault Management MIB Facilitates multivendor fault detection and trouble shooting

18. Hybrid NID Model Hybrid NID Model Enables Service Providers to deliver the same service anywhere(Collaborative delivery Carrier Ethernet services off-net) Actively utilize SOAM for fault monitoring and SLA assurance Securely access and manage their NID functionality Privately manage customers and configuration databases Service Provider doesn�t have to install, supervise or maintain equipment CE Customer Equipment UNI User Network Interface ENNI External Network to Network Interface Wholesale Tunnel � Transparent Carrier Grade Wholesale Circuit White divider in Hybrid NID � a logical demarcation point between Provider�s Wholesale Tunnel and Service Provider�s EVC (Call it an xNNI � but it�s your funeral ?) Blue Rectangle in Hybrid NID is the SP�s logical section of the NID, the grey rectangle belongs to the Wholesale Access Provider DOMAINS � Top Grey domain is Provider�s from ENNI to demarc at Hybrid NID Middle blue domain is SP�s to monitor tunnel The bottom blue domain is the SP�s EVC Hybrid NID Model Enables Service Providers to deliver the same service anywhere(Collaborative delivery Carrier Ethernet services off-net) Actively utilize SOAM for fault monitoring and SLA assurance Securely access and manage their NID functionality Privately manage customers and configuration databases Service Provider doesn�t have to install, supervise or maintain equipment CE Customer Equipment UNI User Network Interface ENNI External Network to Network Interface Wholesale Tunnel � Transparent Carrier Grade Wholesale Circuit White divider in Hybrid NID � a logical demarcation point between Provider�s Wholesale Tunnel and Service Provider�s EVC (Call it an xNNI � but it�s your funeral ?) Blue Rectangle in Hybrid NID is the SP�s logical section of the NID, the grey rectangle belongs to the Wholesale Access Provider DOMAINS � Top Grey domain is Provider�s from ENNI to demarc at Hybrid NID Middle blue domain is SP�s to monitor tunnel The bottom blue domain is the SP�s EVC

19. MEF Ethernet Access Services Establishes industry standard for deploying, buying and selling Ethernet Access Services Key for local, regional and global adoption of Carrier Ethernet New definitions for UNI-ENNI Carrier Ethernet Access Services Technical work nearing completion* Dec/Jan Survey results, confirm MRD and add performance as mandatory ATS for Access Services: Technical Committee Ad-Hoc project proposal passed Target mid year completion Dec/Jan Survey results, confirm MRD and add performance as mandatory ATS for Access Services: Technical Committee Ad-Hoc project proposal passed Target mid year completion

20. The Building Blocks to Global Interconnect Reviewed the steps to interconnect, qualification, engagement and the resources available. Discussed the technologies, specifications and MEF-certified Carrier Ethernet services over multiple, connected, Carrier Ethernet networks. You will hear more this morning on the building blocks including End-to-end Class of Service, Management and Protection� Summary

21. ENNI & Access Services

23. Coming Up NextGlobal Interconnect: OAM