Specifications published by MEF are intended for general distribution to the public and may be downloaded from this site and reproduced without charge.
Please note: Any reproduction of MEF documents shall contain the following statement: "Reproduced with permission of the MEF Forum." All rights granted to MEF under applicable copyright laws are expressly reserved. No permission is granted to any recipient or user of MEF publications to modify any of the information contained therein and MEF disclaims all responsibility and liability for such modifications.
Technical Committee Specifications are grouped below by Carrier Ethernet Service Definitions, Architecture, Management, Service Operations, and Test Suites. Most specifications are introduced by a Powerpoint overview presentation that gives background and explanations that are in addition to the normative definitions in the specifications. The superseded specifications are included at the foot of the table.
Uses the service attributes and parameters that are defined in the MEF “Ethernet Services Attributes Phase 2” and applies them to create different Ethernet services. This document defines three generic service constructs called Ethernet Service types and specifies their associated service attributes and parameters used to create Point-to-Point, Multipoint-to-Multipoint, and Rooted-Multipoint Ethernet services. It defines the Ethernet Services (EPL, EVPL, E-Line, E-LAN, E-Tree, etc.) with Service Attributes and parameters as specified in MEF 10.3, “Ethernet Services Attributes” and in MEF 45, “Multi-CEN Layer 2 Control Protocol”
Gives precise instructions for implementing interoperable CES equipment that reliably transport TDM circuits across Carrier Ethernet Networks while meeting the required performance of circuit emulated TDM services as defined in ITU-T and ANSI TDM standards
Identifies the requirements for MEF Ethernet Services and MEF External Interfaces for use in Mobile Backhaul networks based on MEF specifications
This amendment makes the following changes to MEF 22.2:
Addition of two use cases for phase and time synchronization
Addition of new service attributes for the first phase and time synchronization use case
Addition of new requirements in support of phase and time synchronization
Alignment of synchronization clause to distinguish between frequency and time synchronization
Various editorial corrections, including alignment to current MEF style
Extends the ENNI by defining the UNI Tunnel Access (UTA) which associates a Virtual UNI (VUNI), a remote UNI, and at least one supporting OVC.
Defines Ethernet Access Services, ENNI to UNI Carrier Ethernet services in contrast to the EVC-based (UNI to UNI) services which are defined in MEF 6.1
Specifies the functionality offered by an Access Provider (AP) that, when combined with an Ethernet-Access (E-Access) Service, allows a Service Provider (SP) to monitor and configure selected objects associated with a given UNI and one or more OVC End Points at that UNI in the AP’s network.
This document identifies the requirements for MEF Ethernet Services and MEF External Interfaces (EIs such as UNIs) as well as a management interface for use in support of Cloud Services.
This document specifies Operator Virtual Connection (OVC) Services based mainly on the service attributes defined in MEF 26.1; there are also some service attributes defined in this document that go beyond MEF 26.1.
Carrier Ethernet Service Attributes
The attributes of Ethernet Services observable at a User Network Interface (UNI) and from UNI-to-UNI are defined. In addition, a frame-work for defining specific instances of Ethernet Services is described. These are used in MEF 6.1
This amendment makes the following changes to MEF 10.3: section 8.8.7 is added to define the Composite Performance Metric, new terms are added to Table 1 of MEF 10.3., a new entry is added to Reference of MEF 10.3., and a new appendix is added to MEF 10.3 as Appendix D.
This document amends MEF 10.3 to enhance the UNI Resiliency Service Attribute to include multiple physical links that can carry different Service Frames simultaneously at a UNI.
This Implementation Agreement formalizes the CoS Name and defines three specific CoS Names called Class of Service Labels (CoS Labels). This IA also provides guidelines for CoS Names, in general, in terms of how the performance objectives for OVCs are composed into performance objectives for EVCs.
This document contains specifications for interconnecting Operator CENs in order to support MEF Forum Ethernet Services. This Technical Specification specifies:
The requirements at the ENNI reference point as well as the interface functionality in sufficient detail to ensure interoperability between two Operator CENs.
The connectivity attributes UNI to UNI, UNI to ENNI, and ENNI to ENNI such that multiple Operator CENs can be interconnected and the Ethernet services and Service Attributes in MEF 6.2, MEF 10.3, and MEF 51 can be realized.
The concept of the Super Operator which allows an Operator, acting as a Super Operator, to combine multiple Operator CENs together and make them appear as a single Operator CEN to a Service Provider or another Super Operator
This document specifies a Generic Token Bucket Algorithm based on the Bandwidth Profile Algorithm specified in MEF 10.3 It is expected that other documents can reference this specification for describing new Bandwidth Profiles and methods for regulating the use of other resources.
This document specifies the service attributes and requirements for handling Layer 2 Control Protocol (L2CP) Frames in a Carrier Ethernet Network.
Defines a broad frame work for hop-by-hop and end-to-end service level protection.
Circuit Emulation Service “tunnels” TDM traffic through a Carrier Ethernet network allowing inclusion of legacy networks within a Carrier Ethernet environment
Introduces the framework and terminology for the services (Eth) layer
Defines a split demarcation function between the customer (Subscriber), and the Service Provider
Defines the architecture framework to model the Ethernet Services Layer of MEF compliant Carrier Ethernet Networks.
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
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
Defines an abstract set of Ethernet Service Constructs that are widely applicable regardless of how the UNI-to-UNI Network may be sugmented by providers
Contains requirements for protecting Ethernet Services at an External Interface against link or a Network Element (NE) failure. This specification identifies resiliency requirements at external interfaces applicable to MEF Service and associated Service End Points.
Information and Data Models
This model identifies and defines the information necessary to manage the Carrier Ethernet services as defined by the MEF, including EVC and OVC services. This model is intended to mediate between a product information model and a resource information models, roughly following the TMF SID. This model can be used as the basis for LEGATO Interface Profiles defining APIs for managing Carrier Ethernet services.
Service OAM Fault Management Definition of Managed Objects (SNMP)
Amendment to Service OAM SNMP MIB for Fault Management
Specifies the Performance Monitoring(PM) SNMP Management Information Base(MIB) necessary to manage Service OAM implementations that satisfy the Service OAM requirements and framework specified by MEF 17.
Specifies the Fault Management (FM) YANG Modules necessary to implement the Service Operations, Administration, and Maintenance (OAM) that satisfies the Service OAM requirements and framework specified by MEF 17.
Specifies the Performance Monitoring(PM) YANG Module necessary to satisfy the Service OAM requirements and framework specified by MEF 17.
Specifies the User Network Interface (UNI) and Ethernet Virtual Connection (EVC) Management Information Base (MIB) necessary to configure and monitor the UNI and EVC.
Specifies the External Network Network Interface (ENNI), Operator Virtual Connection (OVC), and Virtual User Network Interface (VUNI) Management Information Base (MIB) necessary to configure and monitor the MEF ENNI, OVC, and VUNI.
Specifies the Virtual NID (vNID) Management Information Base (MIB) necessary to configure and monitor the MEF vNID functionality that satisfies the requirements and definitions found in MEF 43 (vNID) by the Service Provider (SP).
Service Activation and Test
This specification defines the protocol and functionality for Latching Loopbacks (LLs) for Service Activation Testing (SAT) and troubleshooting up to the Information Rate for point-to-point and multipoint services across multiple Carrier Ethernet Networks (CENs).
This document specifies the requirements and use cases for Carrier Ethernet Service Activation Testing (SAT) for E-Access services (Access Ethernet Private Line (Access EPL) and Access Ethernet Virtual Private Line (Access EVPL)) as defined in MEF 33. Service Activation Testing encompasses those business processes for testing MEF services to ensure that the service is configured as specified and meets the defined Service Acceptance Criteria (SAC). Service Activation Testing occurs after the Operator Virtual Connection (OVC) for an E-Access service has been provisioned and before the service is deployed to the customer.
This document standardizes the following: The test PDUs that are exchanged between devices during the test, the control protocol used to configure SAT test, and the control PDUs that are exchanged between the devices in two operators’ networks.
The control protocol provides the ability to configure and control the SAT steps and to fetch test results at the completion of the test. The requirements defined within this document are based on the SAT process as defined in section 10 of the Carrier Ethernet Service Activation Testing Technical Specification (MEF 48).
Amendment to Service Activation Testing Control Protocol and PDU Formats
SOAM Fault and Performance Management
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 E-NNI) and the work of other standards bodies
Implementation Agreement (IA) for Service Operations, Administration, and Maintenance (OAM) that builds upon the framework and requirements specified by MEF 17. In particular, specifying Service OAM requirements for Maintenance Entity Groups (MEGs) and for Fault Management(FM).
Amendment to SOAM FM IA
Specifies an Implementation Agreement for Service Operations, Administra-tion, and Maintenance (SOAM) that satisfies and extends the Performance Monitoring(PM) framework and requirements described in MEF 17.
Specifies the network management requirements to be met by Network Elements supporting Ethernet Service Phase 1
Enables customer equipment to receive information regarding the status and attributes of Ethernet Services thus allowing automatic configuration and improved Subscriber network performance
MEF Service Lifecycle
A process model for the generic Carrier Ethernet service lifecycle, including Service Operations Lifecycle management and Product Lifecycle management. It establishes a foundation for specifications developed by the MEF Service Operations Committee.
This specification documents a Carrier Ethernet service performance reporting framework in which Carrier Ethernet Network (CEN) Operators provide their Subscribers with access to Key Performance Indicators (KPIs) and statistics reporting through a standardized interface.
This document specifies the processes, use cases and guidelines for a standardized MEF Carrier Ethernet Services Qualification Questionnaire that can be used by potential buying carriers to more efficiently find a selling carrier that matches their needs. The questionnaire will encompass MEF defined services and process alignment (quote/order/delivery/assurance/billing/etc) information.
This document is intended to act as an Implementation Agreement for any Operator interested in connecting their Carrier Ethernet network to another Operator using an Ethernet ENNI.
LSO is an agile approach to streamlining and automating the service lifecycle in a sustainable fashion for coordinated management and control across all network domains responsible for delivering an end-to-end Connectivity Service (e.g., Carrier Ethernet, IP VPN, MPLS, etc.). This document describes a Reference Architecture and Framework for orchestrating the service lifecycle.
Abstract Test Suites
Defines the test suite for conformance of Ethernet services and equipment when deployed at the UNI. This is one of the two foundational documents of the CE 1.0 Certification Program.
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. This is one of the two foundational documents of the CE 1.0 Certification Program.
Specifies testing procedures for pass/fail assessment of conformance with each of the operating modes in MEF 8.
Supplements the MEF test specifications MEF 9, and MEF 14 with test procedures for UNI manual configuration mode defined in MEF 13
The Link OAM part of the Abstract Test Suite for UNI Type 2 describes test procedures based on a combination of the requirements for Link OAM described in MEF 20, etc.
Defines test procedures based on a combination of requirements for E-LMI described in MEF 20
Defines test procedures based on a combination of requirements for Service OAM described in MEF 20
Defines test procedures based on requirements for UNI Type 2 described in MEF 20
Defines test procedures for testing and certification of Ethernet Access (E-Access) Services namely Access EPL and Access EVPL deployed service provider networks. The test cases are based on requirements defined in MEF 33 and MEF 23.1
Defines Abstract Test Suite for External Network Network Interface (ENNI) in accordance with the requirements and service attributes specified in the ENNI (MEF 26.1)
Superseded MEF Specifications
Superseded by MEF
Ethernet Services Model Phase I
Traffic Management Phase 1
Metro Ethernet Services Definitions Phase 1
Metro Ethernet Services Definitions Phase 2
Layer 2 Control Protocol Handling Amendment to MEF 6.1
EMS-NMS Information Model
Phase 2 EMS-NMS Information Model
Technical Corrections to MEF 7.1
Provides a standard for carrier management systems to enable configuration and fault management of Carrier Ethernet services. The overview presentation was updated August 2nd, 2013
Ethernet Services Attributes Phase 1
Ethernet Services Attributes Phase 2
Amendment to MEF 10.1 Ethernet Services Attributes Phase 2
MEF 10.2 Ethernet Services Attributes Phase 2
Performance Attributes Amendment to MEF 10.2
Metro Ethernet Network Architecture Framework Part 2: Ethernet Services Layer
Carrier Ethernet Network Architecture Framework Part 2: Ethernet Services Layer - Basic Elements
Network Architecture Framework Part 2: External Interface Extensions
Mobile Backhaul Implementation Agreement (2/09)
Mobile Backhaul Phase 2 Implementation Agreement
Amendment to MEF 22.1 – Small Cell Backhaul
Class of Service Phase 1 Implementation Agreement
External Network to Network Interface (ENNI) Phase I
Corrected Figure 10 for MEF 26
OVC Layer 2 Control Protocol Tunneling Amendment to MEF 26
Service Level Specification Amendment to MEF 26
Service OAM Fault Management Implementation Agreement
Service OAM Performance Monitoring Implementation Agreement
This Implementation Agreement specifies a set of Class of Service Names called CoS Labels that can be used by Service Providers and their Subscribers to indicate the performance expectations to be associated with a given set of frames that comprise a CoS Frame Set. This CoS IA includes standards for CoS and Color identification as well as performance objectives and supporting requirements.
Specifies the requirements at the ENNI reference point as well as the interface functionality in sufficient detail to ensure interoperability between two Operator MENs in-cluding Link OAM and the connectivity attributes UNI to UNI, UNI to ENNI, and ENNI to ENNI such that multiple Operator MENs can be interconnected and the Ethernet services and attributes in MEF 6.1, MEF 10.2.