An Introduction to The Technical Work of the MEF

An Introduction to The Technical Work of the MEF 1. 2. 3. 4. Overview of the technical work The specifications – summaries & recent specifications Technical work in development Relationship to other standards bodies 1 The Technical Work of the MEF Technical Committee • Technical Committee Services Testing Architecture Management – The Technical Committee is organized into Services, Architecture, Management, Test & Measurement. – The Technical Committee has active liaisons with other standards organizations. Each year, approaching 500 technical contributions are generated by the 875 members of MEF technical group who are engaged in the ongoing work. Over 120+ technical committee members meet each quarter to instigate, progress and finalize specifications and implementation agreements. • Technical Overview of the Work of the MEF – The technical committee develops technical specifications, implementation agreements, test specifications and position statements – A list of the Specifications, timelines, etc., follows – Detailed technical presentations are available on the MEF web site • www.metroethernetforum.org/presentations • www.metroethernetforum.org/techspecs 2 The Technical Work of the MEF • Technical Committee – The Technical Committee currently focuses their work: – Services, Architecture, Architecture, Management, Test & Measurement. – Each have sub-teams focused on delivering technical specifications, implementation agreements, frameworks, agreements and interoperability content to support the adoption of Carrier Ethernet. – The Technical Committee has active liaisons with other standards organizations. • Active Participation in the Development of Carrier Ethernet – The Development of Carrier Ethernet is driven solely by the active participation of the members. This participation is an opportunity to advance member companies and contribution to next generation networking. – Active recruitment to involve new Service Provider and equipment manufacturers in the work of the MEF 3 Introduction to the Specifications • Purpose – This section takes a brief look at the specifications and their purpose prior to going to individual specification overviews and or the specifications • Contents – – – – Connectivity between Carrier Ethernet and the specifications Specification timeline A summary of all the specifications A quick look at terminology and the two types of specifications • Audience – Intended for those who want to understand the scope of the presentations prior to looking at the specifications • What to do next – Review the more detailed PowerPoint presentations or read the specifications Please also see the presentations on the MEF website giving overviews on each specification and further details of upcoming specifications and industry liaisons 4 Specifications Timeline MEF 4 Architecture MEF 7 EMS-NMS MEF 12 Architecture MEF 15 Management MEF 16 ELMI MEF 10.1 Service MEF 17 Attributes Phase 2 Service OAM MEF 6.1 Ethernet Service Definitions Phase 2 MEF 2 Protection MEF 11 UNI Framework 2001-3 2004 2005 2006 2007 2008 MEF 3 Circuit Emulation MEF 6 Service Definitions MEF 10 Service Attributes Phase 1 MEF 13 UNI-IA MEF 14 Traffic Management MEF 8 Test Suite Circuit Emulation MEF 9 Services Test Suite MEF 18 Circuit Emulation Services Test Suite MEF 19 UNI Type 1 Test Suite MEF 20 UNI Type 2 MEF 21 UNI Type 2 Test Suite Part 1 5 Approved MEF Specifications • MEF 2 • MEF 3 • MEF 4 • MEF 6.1 • MEF 7 • MEF 8 • • • • MEF 9 MEF 10.1 MEF 11 MEF 12 Requirements and Framework for Ethernet Service Protection Circuit Emulation Service Definitions, Framework and Requirements in Metro Ethernet Networks Metro Ethernet Network Architecture Framework Part 1: Generic Framework Metro Ethernet Services Definitions Phase 2 EMS-NMS Information Model Implementation Agreement for the Emulation of PDH Circuits over Metro Ethernet Networks Abstract Test Suite for Ethernet Services at the UNI Ethernet Services Attributes Phase 2* User Network Interface (UNI) Requirements and Framework Metro Ethernet Network Architecture Framework Part 2: Ethernet Services Layer User Network Interface (UNI) Type 1 Implementation Agreement Abstract Test Suite for Traffic Management Phase 1 Requirements for Management of Metro Ethernet Phase 1 Network Elements Ethernet Local Management Interface Service OAM Framework and Requirements Abstract Test Suite for Circuit Emulation Services Abstract Test Suite for UNI Type 1 User Network Interface (UNI) Type 2 Implementation Agreement Abstract Test Suite for UNI Type 2 Part 1: Link OAM • MEF 13 • MEF 14 • MEF 15 • • • • • • MEF 16 MEF 17 MEF 18 MEF 19 MEF 20 MEF 21 * MEF 10 .1 replaces and enhances MEF 10 Ethernet Services Definition Phase 1 and replaced MEF 1 and MEF 5. MEF 6.1 replaced MEF 6. 6 How the Specifications Enable Carrier Ethernet This chart shows how the MEF specifications enable the attributes of Carrier Ethernet indicating the responsible area within the MEF Technical Committee Carrier Ethernet Attributes MEF Specs MEF 2 MEF 3 MEF 4 MEF 6.1 MEF 7 MEF 8 MEF 9 MEF 10.1 Service Area Test & Measurement Area Service Area Test & Measurement Area Service Area Service Area Service Area Architecture Area Service Area Management Area Service Area Service Area Standardized Services Service Management Reliability Architecture Area Quality of Service Scalability Service Area MEF 11 MEF 12 MEF 13 MEF 14 MEF 15 MEF 16 MEF 17 Architecture Area Architecture Area Architecture Area Test & Measurement Area Management Area Management Area Management Area Test & Measurement Area Test & Measurement Area Architecture Area MEF 18 MEF 19 MEF 20 MEF 21 Test & Measurement Area Test & Measurement Area Architecture Area Test & Measurement Area Test & Measurement Area Test & Measurement Area Architecture Area Test & Measurement Area 7 Global Expansion to Carrier Ethernet • Relationship between the MEF Specifications and Carrier Ethernet – The technical work of the MEF as described in the specifications, together with the work of associated standards bodies, collectively enable the functionality and attributes of Carrier Ethernet – The completed specifications continue to refer to MENs (Metro Ethernet Networks) but this is now a generic term covering the enabled service network in the increasing variety of access, metro and long haul networks 8 MEF Key Specifications • Architecture – MEF 4, Generic architecture provides a basis for offering services and building out national/international networks • Services – MEF 6.1 – Ethernet Services Definitions –defines E-Line and ELAN service types, and defines in detail Ethernet Private Line (EPL) and Ethernet Virtual Private Line (EVPL) service – MEF 10.1 - Ethernet Service Attributes – Phase 2 defines the key UNI and EVC attributes that can be used to build services. • Abstract Test Suite for Ethernet Services – MEF 9 & MEF 14 - basis for certification of vendor equipment and service provider services 9 Industry Challenges & MEF Initiatives Challenge MEF Work • MEF E-NNI Project delivers standards-based means of networknetwork interconnect, accelerating provisioning of customer orders • Wholesale Access Interconnect Group defining Access Services & wholesale processes • Access Technology Group promotes use of MEF specs including OAM on all available access technologies (copper, fiber, cable etc.) • Mobile Access Working Group supports evolving voice, data and content requirements of mobile operators. • ESD2 - E-Tree, and detailed definitions for four new services – EPLAN, EVP-LAN, EP-Tree, and EVP-Tree. Service Availability Support Evolving Requirements Service Management • UNI Type 2 (MEF 20) adds manageability between the customer and network for Ethernet services. • NID Network Interface Devices enables Service Provider management of Ethernet services to the customer’s premises. 10 Three Types of Specifications • Technical Specifications – They include architectural and abstract models required to create a robust platform of technical requirements and definitions – They are the principal documents that define mandatory and optional elements, attributes etc., of the elements of a Carrier Ethernet network (UNI, Services, NNI, etc) • Implementation Agreements – These typically quantify specific parameters and attributes called out in the technical specifications so that consistent, interoperable implementation can occur • Abstract Test Suites – These consist of a series of tests to be used to measure conformance to certain MEF specifications. – They are intended to be used to create specific test plans such as those used in the MEF Certification Program Note: The MEF specifications are written by representatives from the member companies who give their time to the work in the interests of the industry. Their various backgrounds and style are reflected n the MEF specifications 11 Terminology • Terminology – There are a great number of definitions in each specification. Where possible they reuse common understanding of terms in other standards bodies such as the ITU • Compliance terminology common to all specifications – The level of mandatory and optional compliance to the implementation agreement uses the familiar RFC 2119 terminology 1. MUST This word, or the terms "REQUIRED" or "SHALL", mean that the definition is an absolute requirement of the specification. 2. MUST NOT This phrase, or the phrase "SHALL NOT", mean that the definition is an absolute prohibition of the specification. 3. SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. 4. SHOULD NOT This phrase, or the phrase "NOT RECOMMENDED" mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label. 5. MAY This word, or the adjective "OPTIONAL", mean that an item is truly optional. One vendor may choose to include the item because a particular marketplace requires it or because the vendor feels that it enhances the product while another vendor may omit the same item. An implementation which does not include a particular option MUST be prepared to interoperate with another implementation which does include the option, though perhaps with reduced functionality. In the same vein an implementation which does include a particular option MUST be prepared to interoperate with another implementation which does not include the option (except, of course, for the feature the option provides.) 12 MEF Specifications Overview MEF 4 Purpose Audience Metro Ethernet Network Architecture Framework Part 1: Generic Framework Introduces the framework and terminology for the services (Eth) layer All (Equipment Manufacturers, Service Providers & Enterprises), since it provides the fundamental understanding of the Carrier Ethernet architecture Technical Committee Architecture Area MEF 10.1 Purpose Ethernet Services Attributes Phase 2 Defines the service attributes and parameters required to offer the services defined in MEF 6. Updated from Original MEF 10 All, since it provides the fundamentals required to build devices and services that deliver Carrier Ethernet. For Enterprise users it gives the background to Service Level Specifications for Carrier Ethernet Services being offered by their Service Providers and helps to plan Ethernet Standardized Services as part of their Services network. overall Technical Committee Service Area Audience 13 MEF Specifications Overview MEF 6.1 Purpose Metro Ethernet Services Definitions Phase II Defines the Ethernet Services (EPL, EVPL, E-Line, E-LAN, E-Tree. etc) All, since it provides the fundamentals required to build devices and services that deliver Carrier Ethernet. For Enterprise users it gives the background to Service Level Specifications for Carrier Ethernet Services being offered by their Service Providers and helps to plan Ethernet Services as part of their overall network. Technical Committee Service Area Audience MEF 12 Purpose Metro Ethernet Network Architecture Framework Part 2: Ethernet Services Layer Defines the Ethernet Services (ETH) Layer as the specific layer network responsible for delivery of Ethernet Protocol Data Units across internal and external interfaces. Equipment Manufacturers building devices that will carry Carrier Ethernet Services. Useful for Service Providers architecting their systems. Technical Committee Architecture Area Audience 14 MEF Specifications Overview MEF 7 Purpose Audience EMS-NMS* Information Model *Element Management System–Network Management System Provides a standard for carrier management systems to enable configuration and fault management of Metro Ethernet services. Equipment Manufacturers building devices that will carry Carrier Ethernet Services. Useful for Service Providers architecting their systems. Technical Committee Management Area MEF 15 Purpose Audience Requirements for Management of Metro Ethernet Phase 1 Network Elements Specifies the network management requirements to be met by Network Elements supporting Ethernet Service Phase 1 Equipment Manufacturers building devices that will carry Carrier Ethernet Services. Useful for Service Providers architecting their systems. Technical Committee Management Area 15 MEF Specifications Overview MEF 16 Purpose Ethernet Local Management Interface (E-LMI) Enables customer equipment to receive information regarding the status and attributes of Ethernet Services thus allowing automatic configuration and improved Subscriber network performance. Equipment manufacturers of Customer Edge devices and of Service Provider equipment. Useful for Service Providers architecting their systems. Technical Committee Management Area Audience MEF 17 Purpose Service OAM Requirements & Framework – Phase 1 Provides requirements to be satisfied by the Service OAM mechanisms in MENs and framework for discussing and implementing those mechanisms. It also provides context for several MEF specifications (UNI type 2 and ENNI) and the work of other standards bodies Equipment Manufacturers building devices and Service Providers architecting their systems. Technical Committee Management Area Audience 16 MEF Specifications Overview MEF 11 Purpose User Network Interface (UNI) Requirements and Framework Defines a split demarcation function between the customer (Subscriber), and the Service Provider User Network Interface (UNI) Type 1 Implementation Agreement This allows existing Ethernet devices (switch, router, workstation, etc) acting as Customer Edge devices to be compliant to this IA with no additional software or hardware upgrades User Network Interface (UNI) Type 2 Implementation Agreement Specifies MEF UNI characteristics and operation in which customer side of the UNI is automatically configured by the network side of the UNI allowing verification of SLA and UNI connectivity. Additional objectives include support for Ethernet OAM (802.3ah, 802.1ag) over the UNI. Required for support of ELMI Equipment Manufacturers building devices that will carry Carrier Ethernet Services. Useful for Service Providers architecting their systems. Technical Committee Architecture Area MEF 13 Purpose MEF 20 Purpose Audience 17 MEF Specifications Overview MEF 9 Purpose Abstract Test Suite for Ethernet Services at the UNI Defines the test suite for conformance of Ethernet services and equipment when deployed at the UNI MEF 14 Purpose Abstract Test Suite for Traffic Management Phase 1 Defines the requirements and corresponding test procedures for Service Performance and Bandwidth Profile Service Attributes that may be specified as part of a Service Level Specification (SLS) for an Ethernet Service Equipment Manufacturers building devices that are designed to conform to MEF Specifications. Service Providers conducting who require that their services comply to MEF Specifications Technical Committee Test and Measurement Area Audience 18 MEF Specifications Overview MEF 18 Purpose Audience Abstract Test Suite for CES Specifies testing procedures for pass/fail assessment of conformance with each of the operating modes in MEF 8. Equipment Manufacturers building devices that will carry TDM traffic across Carrier Ethernet Networks. Useful for Service Providers architecting their systems. Technical Committee Test and Measurement Area MEF 19 Purpose Abstract Test Suite for UNI Type 1 Supplements the MEF test specifications MEF 9, and MEF 14 with test procedures for UNI manual configuration mode defined in MEF 13 Abstract Test Suite for UNI Type 2, Phase 1: Link OAM Provides the first of six possible test suites for UNI type 2 (MEF 20) Equipment Manufacturers building devices that will carry Carrier Ethernet Services. Useful for Service Providers architecting their systems. Technical Committee Test and Measurement Area MEF 21 Purpose Audience 19 MEF Specifications Overview MEF 2 Purpose Audience Requirements and Framework for Ethernet Service Protection Defines a broad frame work for hop-by-hop and end-to-end service level protection. Equipment Manufacturers building devices that will carry Carrier Ethernet Services. Useful for Service Providers architecting their systems. Technical Committee Architecture Area 20 MEF Specifications Overview MEF 3 Purpose Circuit Emulation Service Definitions, Framework and Requirements in Metro Ethernet Networks Circuit Emulation Service “tunnels” TDM traffic through a Metro Ethernet network allowing inclusion of legacy networks within a Carrier Ethernet environment Equipment Manufacturers supporting devices that provide Circuit Emulation over Carrier Ethernet Services. Useful for Service Providers architecting their systems. Technical Committee Service Area Audience MEF 8 Purpose Audience Implementation Agreement for the Emulation of PDH Circuits over Metro Ethernet Networks Gives precise instructions for implementing interoperable CES equipment that reliably transport TDM circuits across Metro Ethernet Networks while meeting the required performance of circuit emulated TDM services as defined in ITU-T and ANSI TDM standards Equipment Manufacturers supporting devices that provide Circuit Emulation over Carrier Ethernet Services. Useful for Service Providers architecting their systems. Technical Committee Service Area 21 Recently Approved Specifications MEF 6.1 MEF 20, MEF 21 22 The Work of the MEF Continues… 23 MEF 6.1: Ethernet Services Definitions Phase 2 • Approved April 2008 • Adds a new service type (E-Tree) • Adds four new services – Two each to E-LAN and E-Tree Service Type E-Line E-LAN E-Tree* Port-Based (All-to-One Bundling) Ethernet Private Line Ethernet Private LAN* Ethernet Private Tree* VLAN-Based (Service Multiplexed) Ethernet Virtual Private Line Ethernet Virtual Private LAN* Ethernet Virtual Private Tree* No change Modified New 24 MEF 20: UNI Type 2 Subscriber UNI Private Customer Network S Subscriber Enduser Metro Ethernet Network (MEN) UNI Private Customer Network S Enduser Ethernet Virtual Connection • Allows provider equipment to provision, configure and distribute EVC information and attributes to customer equipment. • Allows customer equipment to retrieve EVC status and configuration information from service provider equipment. • • • UNI Type 2.1 and 2.2 are defined Requires backwards compatibility to UNI Type 1.1 and Type 1.2 Adds new set of functionalities to the ones defined in UNI Type 1 – – – – – – Link OAM E-LMI Service OAM Protection Enhanced UNI Attributes L2CP Handling • Approved July 2008 25 MEF 21: Abstract Test Suites for UNI Type 2: Part 1: Link OAM • UNI Type 2 Certification Parts 1 – More complex to test than UNI Type 1 – Includes Ethernet link and service OAM – UNI Type 2 service requires backwards compatibility with UNI Type 1 – Components of UNI type 2 test suite such as Link OAM (completed as MEF 21) – Test one of the six elements of MEF 20 – Work on other areas is in progress – Comprehensive: 272 Test Cases – Approved July 2008 26 MEF Development Work • Statement: – The work of the MEF continues • The questions: – How or why can I implement Carrier Ethernet while development is still ongoing? – When will it be finished? • The answers: …… 27 MEF Development Work • Future Technical Work – The MEF technical work continues on all elements of Carrier Ethernet (OAM, Network to Network Interfaces, implementation agreements, etc.) This includes coordination with other standards bodies. • Deployment now brings immediate benefits – Immediate benefits are being obtained today based on implementing today’s specifications. These benefits increase as the specifications complete • MEF Timescales – The MEF continues to exist during the foreseeable future to complete our mission 28 MEF Technical Committee Work Dashboard August 2008 Service Area MEF 6.1 – Ethernet Services Definitions Phase 2 (TS) MEF 3 – Circuit Emulation Service Requirements (TS) Architecture Area MEF 2 – Protection Framework and Requirements (TS) MEF 4 – Metro Ethernet Network Architecture Framework Part 1: Generic Framework (TS) Management Area MEF 7 – EMS - NMS Information Model (TS) Test and Measurement Area MEF 9 – Abstract Test Suite for Ethernet Services at the UNI (TS) MEF 15 – Requirements for MEF 14 – Abstract Test Suite for Management of Metro Ethernet Phase Traffic Management Phase 1 (TS) 1 – Network Elements (TS) MEF 8 Emulation of PDH over MENs (IA) MEF 10.1 Ethernet Services Attributes Phase 2 (TS) Classes of Service (IA) MEF 10.1 Update: Attribute Enhancements Mobile Backhaul (IA) MEF 11 - UNI Framework and Requirements (TS) MEF 12 – Metro Ethernet Network Architecture Framework Part 2: Ethernet Services Layer (TS) MEF 16 – Ethernet Local Management MEF 18 Abstract Test Suite for CES Interface E-LMI (TS) over Ethernet (TS) MEF 17 Service OAM Requirements and Framework (TS) MEF 19 Abstract Test Suite for UNI Type 1 (TS) MEF 21 UNI Type 2 Test Suite (TS) Part 1 link OAM Abstract Test Suite for E-NNI (TS) UNI Type 2 Test Suite (TS) Part 2 E-LMI MEF 13 – User Network Interface Type Service OAM Performance 1 (IA) Management (IA) MEF 20 UNI Type 2 (IA) External NNI (E-NNI) Phase 1 (TS) Ethernet Service Constructs (TS) NID Specification (TS) Service OAM Fault Management (IA) EMS-NMS Information Model (TS) Phase 2 Delivered Throughput (IA) MEF Standards Process and Legend TS Technical Specification IA Implementation Agreement * MEF 10.1 replaced MEF 10. which replaced MEF 1 and MEF 5. MEF 6.1 replaced MEF 6 New Project Working Document Straw Ballots comments Approved Draft Letter Ballot Stable Document Approved Draft Approved Specification 29 Preview of Upcoming MEF Specifications MEF [TBA] Purpose External Network to Network Interface (E-NNI) This document describes the functions and protection mechanisms of the ENNI The E-NNI is the interface connecting two MENs where the MENs belong to different administrative domains Equipment Manufacturers building devices that will carry CE Services. Useful for Service Providers architecting their systems creating interconnectivity with other Service Providers. Straw Ballot Technical Committee Architecture Area Audience Status Upcoming specifications provide and ideal focal point for new members to make contributions IMPORTANT NOTE This information is preliminary and is subject to change 30 E-NNI Specification E-NNI Provider 1 Provider 2 • • • • Nobody has footprint everywhere. The interconnection of Carrier Ethernet networks is one of the last hurdles for ubiquitous Ethernet services Need a common language for peering E-NNI is a reference point representing the boundary between two Carrier Ethernet Networks, each in a different administrative domain Draft # 6 is the latest version Approved Draft comments Straw Ballot Stable Document New Project Letter Ballot Approved Specification IMPORTANT NOTE This information is preliminary and is subject to change 31 Preview of Upcoming MEF Specifications MEF [TBA] Purpose Audience Status EMS-NMS* Information Model Phase II *Element Management System–Network Management System Replacement for MEF 7 with support for E-LMI (MEF 16) and Phase II Service Definitions and Attributes Equipment Manufacturers building devices and Service Providers architecting their systems. Approved Draft Technical Committee Management Area Upcoming specifications provide and ideal focal point for new members to make contributions IMPORTANT NOTE This information is preliminary and is subject to change 32 Classes of Service • Accelerate adoption of Carrier Ethernet by minimizing confusion that will result from each Service Provider inventing their own CoS schemes. – Multiple schemes result in a multiplicity of diverse CoS definitions that don’t easily map to provide end to end CoS – Interconnect (via E-NNI) simplification • Agree on 2 class and 3 class common models – Ensure key applications can be given sufficient forwarding performance end-to-end to meet application requirements – A Service Provider may well offer additional classes • Stretch goal is to quantify models Approved Draft comments Straw Ballot Stable Document New Project Letter Ballot Approved Specification IMPORTANT NOTE This information is preliminary and is subject to change 33 Mobile Backhaul Implementation Agreement UNI UNI Next-Gen Base Station Next-Gen Network Controller Interworking Function Legacy Base Station UNI RAN backhaul network based on Carrier Ethernet services UNI Interworking Function Legacy Network Controller • • Provide scalable, economic, dependable Carrier Ethernet-based solution for radio access network (RAN) backhaul Implementation Agreement (IA) provides guidelines how to apply MEF standards for – – – Legacy mobile backhaul transport Hybrid offload (HSPA/data via CE, voice via TDM/ATM) transport Next generation (IP-only base station) transport New Project Approved Draft comments Straw Ballot Stable Document Letter Ballot Approved Specification IMPORTANT NOTE This information is preliminary and is subject to change 34 Network Interface Devices (NID) Specification Partial UNI -N interface on NID towards UNI -C Inter-NID Interface Metro Ethernet NID towards Metro Ethernet Edge Interface Metro Ethernet towards NID interface CE Equipment Carrier Ethernet NID #1 Carrier Ethernet NID #2 • A NID is a device which terminates a Carrier Ethernet Network Carrier Ethernet Network Edge – Ethernet Transport Termination (ETT) – Ethernet Service Termination (EST) – Ethernet Tunnel Service Termination (ETST - to be defined in the later phases). • First Approved Draft Approved Draft comments Straw Ballot Stable Document Letter Ballot Approved Specification New Project IMPORTANT NOTE This information is preliminary and is subject to change 35 Ethernet Service Constructs • Defines constructs to be used by specifications defining specific Ethernet Sub-Networks and/or specific External Interfaces within a Carrier Ethernet network New Project Approved Draft comments Straw Ballot Stable Document Letter Ballot Approved Specification IMPORTANT NOTE This information is preliminary and is subject to change 36 Service OAM: Performance and Fault Management • Service OAM: Performance Management – Purpose: service performance monitoring – Planned to consist of extensions to the Y.1731/IEEE 802.1ag procedures and protocols – Extensions are required to manage performance for multipoint EVCs since Y.1731 only covers Point-to-Point EVCs • Fault Management – Q.1731 and IEEE 802.1ag specify protocols and procedures for fault management of Ethernet services. – The goal of this Implementation Agreement is to specify how to use these two standards for the MEF standardized Ethernet services. New Project Approved Draft comments Straw Ballot Stable Document Letter Ballot Approved Specification IMPORTANT NOTE This information is preliminary and is subject to change 37 Abstract Test Suites • UNI Type 2 Certification Parts 1 & 2 – More complex to test than UNI Type 1 – Includes Ethernet link and service OAM – UNI Type 2 service requires backwards compatibility with UNI Type 1 – Components of UNI type 2 test suite such as Link OAM (completed as MEF 21) and E-LMI are work in progress • E-NNI Certification – Tests the function, protection & recovery mechanisms of two interoperating MENs via their External Network to Network Interfaces. Uses similar constructs used in MEF 9 & MEF 14 – Abstract Test Suite is work in progress, depends on completion of E-NNI base specification – Plans to include UNI services as far as they are mapped to E-NNI services Approved Draft comments Straw Ballot Stable Document New Project Letter Ballot Approved Specification IMPORTANT NOTE This information is preliminary and is subject to change 38 Relationship to other Standards Bodies 39 What Do We Mean By “Ethernet?” • Ethernet as a point-to-point link  IEEE 802.3 view • Ethernet as a packet switched network (PSN) infrastructure  IEEE 802.1 (bridging) view  ITU-T SG15 / SG13 managed Ethernet network view • Ethernet as a service  MEF view – user-to-user transfer of 802.3 frames over any transport layer  E-Line, E-LAN and E-Tree 40 Each Standards Body Has Their Approach Working inward from the edge Working outward from the core Making it work together The MEF’s role is largely additive to these organizations, developing necessary additional specifications that are required to enable Carrier Ethernet. The MEF also provides inputs in support of Carrier Ethernet to these bodies via its participating members and liaisons. It is not within the scope of the MEF to endorse or otherwise the work of other standards bodies and associations 41 Complementary Standards Activities Goals • Reach consensus, bring MEF work to other bodies, re-use work of other bodies, work with other bodies, avoid duplication, keep in communications Scalability IEEE ITU-T IETF Provider Bridge IEEE 802.1ad Provider Backbone Bridge IEEE 802.1ah (MAC-in-MAC, and extended label space) ITU-T SG 15 has referenced the MEF service work in their documents that describe EPL and EVPL. Layer 2 VPNs Service Management IEEE ITU-T OIF IEEE 802.1ag Fault Management IEEE 802.3ah link OAM ITU-T SG13 for Service OAM Working with ITU SG 4 on harmonizing their work with MEF 7 and adding additional features of interest to the MEF such as support of E-LMI Customer signaling of Ethernet Services Reliability IETF MPLS Fast Reroute, graceful restart 42 Ethernet Standards Summary Standards Body IEEE Ethernet Services • • • • • • • • • • Architecture/Control 802.3 – MAC 802.3ar – Congestion Management 802.1D/Q – Bridges/VLAN 802.17 - RPR 802.1ad – Provider Bridges .1ah – Provider Backbone Bridges .1ak – Multiple Registration Protocol .1aj – Two Port MAC Relay .1AE/af – MAC / Key Security .1aq – Shortest Path Bridging Ethernet OAM Ethernet Interfaces - • 802.3ah – EFM OAM • 802.1ag – CFM • 802.1AB - Discovery • 802.1ap – VLAN MIB • 802.3 – PHYs • 802.3as - Frame Expansion MEF • MEF 10.1 – Service Attributes • MEF 3 – Circuit Emulation • MEF 6.1 – Service Definition • MEF 8 – PDH Emulation • MEF 9 – Test Suites • MEF 14 – Test Suites • Services Phase 2 • G.8011 – Services Framewrk • G.8011.1 – EPL Service • G.8011.2 – EVPL Service • G.asm – Service Mgmt Arch • G.smc – Service Mgmt Chnl • MEF 4 – Generic Architecture • MEF 2 – Protection Req & Framework • MEF 11 – UNI Req & Framework • MEF 12 – Layer Architecture • MEF 20 – UNI Type 2 • MEF 7– EMS-NMS Info Model • MEF 15– NE Management Req • MEF 13 - UNI Type 1 • MEF 17 – Service OAM • MEF 16 – ELMI Requirements & Framework • E-NNI • Service OAM Protocol – Ph. 1 • Performance Monitoring • Y.1730 – Ethernet OAM Req • Y.1731 – OAM Mechanisms • G.8031 – Protection • Y.17ethqos – QoS • Y.ethperf - Performance ITU • G.8010 – Layer Architecture • G.8021 – Equipment model • G.8010v2 – Layer Architecture • G.8021v2 – Equipment model • Y.17ethmpls - ETH-MPLS Interwork • G.8012 – UNI/NNI • G.8012v2 – UNI/NNI TMF - - •TMF814 – EMS to NMS Model - 43 Accelerating Worldwide Adoption of Carrier-class Ethernet Networks and Services www.MetroEthernetForum.org 44