| Technical Committee Work |
| The Technical Committee focuses on four broad areas of development work: Services, Architecture, Management, Test & Measurement. Each area has teams working on specific projects to define and advance Carrier Ethernet in support of its worldwide adoption. The first chart below describes projects already approved as MEF specifications in each area. The four areas of work and Specification types are described. The second chart shows new Technical Committee projects under development. |
| MEF Completed Specifications |
| Service Area |
Architecture Area |
Management Area |
Test Area |
|
Service Attributes
|
MEF 10.2 UNI & EVC Service Attributes Phase 2
MEF 10.2.1 Amendment: Availability and Resiliency Performance Attributes
MEF 26.1 ENNI rollup + Rooted Multipoint EVC
MEF 29 Ethernet Service Constructs |
| Service Definitions |
MEF 6.1 Ethernet Services
Definitions Phase 2
MEF 6.1.1 Amendment: Layer 2 Control Protocol (L2CP)
MEF 28 UNI Tunnel Access (UTA) Service & Attributes
MEF 33 Ethernet Access Services |
|
Legacy Services
|
| MEF 3 Circuit Emulation Service Requirements |
|
Implementation Agreements
|
MEF 8 Emulation of PDH over MENs
MEF 22.1 Mobile Backhaul
MEF 23.1 Class of Service |
|
|
ETH Service Layer
|
MEF 4 Part 1: Generic Framework
MEF 12.1 Part 2: Ethernet Services Layer Phase 2
MEF 12.1.1 Amendment: UTA, VUNI |
|
External Interfaces: UNI
|
|
MEF 11 UNI Framework and Requirements
|
|
External Interfaces: ENNI, VUNI
|
| See MEF 26.1, MEF 28, & MEF 12.1.1 |
|
Protection
|
MEF 2 Protection Framework and Requirements
MEF 32 Service Protection across External Interface |
|
Protocols
|
| MEF 16 Ethernet Local Management Interface (E-LMI) |
| Implementation Agreements |
MEF 13 UNI Type 1
MEF 20 UNI Type 2 |
|
|
Protocol Neutral Information Model
|
MEF 7.1 EMS-NMS Information Model Phase 2
MEF 7.1.1 Amendment |
|
Protocol specific MIBs
|
MEF 31 SOAM FM/TC (SNMP)
MEF 31.0.1 Amendment: Service OAM (SNMP)
MEF 36 SOAM PM (SNMP)
MEF 38 SOAM CFM/FM (Yang)
MEF 39 SOAM PM (Yang) |
|
Network Elements & Service Management
|
MEF 15 Requirements for Management of Carrier Ethernet Phase 1 – Network Elements
MEF 17 Service OAM Requirements and Framework |
|
Implementation Agreements
|
MEF 30 Service OAM FM Phase1
MEF 35 Service OAM PM |
|
|
Abstract Test Suites (ATS) for Services
|
MEF 9 ATS for Ethernet Services at the UNI
MEF 14 ATS for Traffic Management Phase 1
MEF 18 ATS for CES over Ethernet
MEF 34 ATS for Ethernet Access Services |
|
ATS for External Interfaces
|
MEF 19 ATS for UNI Type 1
UNI Type 2 ATSs:
MEF 21 UNI Type 2 ATS Part 1 link OAM
MEF 24 UNI Type 2 ATS Part 2 E-LMI
MEF 25 UNI Type 2 ATS Part 3 Service OAM
MEF 27 UNI Type 2 ATS Part 5 Enhanced UNI Attributes, Part 6, L2CP
MEF 37 ATS for ENNI Part 1 |
|
| |
| Development Areas |
|
Service Area Mandated to define Carrier Ethernet services models, definitions and service parameters and attributes. The focus is to define common services terminology along with the associate attributes and parameters to allow equipment manufacturers, service providers and enterprise customers to speak in a common language for standardized Carrier Ethernet implementations.
Architecture Mandated to develop an architectural reference model and set of common linguistic tools for the technical committee work. The layered MEN/CEN architecture is defined including the multiple base transport layers, the single Ethernet Services layer and the application layers that ride on top of the Ethernet Services. Each layer has been further decomposed into the Adaptation, Connection and Termination elements. This critical area is completed with the UNI framework allowing users to seamlessly access the Carrier Ethernet network from the customer premise equipment to the core backbone.
Management - Mandated to develop Carrier Ethernet operations, administration and maintenance (OA&M) requirements, models and definitions. This area is focused on defining and ensuring that network management is effective and interoperable across Carrier Ethernet platforms. This includes normal network implementations that include multi-vendor solutions and integration into legacy network architectures.
Test and Measurement – Mandated to define suites of test methodologies and test cases that matching the clauses in the related MEF Specifications. Their intended use is as the basis for the MEF Certification Programs test plans to ensure the functional conformance of both products and services to MEF Specifications.
|
| Types of Specifications |
|
Technical Specifications 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 typically quantify specific parameters and attributes called out in the technical specifications so that consistent, interoperable implementation can occur
Abstract Test Suites are the comprehensive sets of test cases to be used to evaluate conformance to certain MEF specifications as described under Test and Measurement above.
|
| Technical Committee Work in Progress |
| Service Area |
Architecture Area |
Management Area |
Test Area |
|
Service Attributes
|
- MEF 10.3 UNI & EVC Service Attributes
- Performance Metric (MEF 10.3.z)
- Layer 2 Control Protocol (L2CP) Processing for MEF Services
- Generic BWP
- Adhoc: Availability Metric
|
| Service Definitions |
- Ethernet Access Service with vNID Function
- Ethernet Service Definitions (MEF 6.2)
- OVC Services Definition
|
| Legacy Services
|
|
|
|
|
Implementation Agreements
|
- Mobile Backhaul
Phase 3
- Class of Service Phase 3
- CE for Cloud
|
|
|
ETH Service Layer
|
- MEF 12.2 Part 2 (vNID & Rollup)
|
| External Interfaces
|
|
| Protection |
|
| Protocols |
|
|
|
|
| Implementation Agreements |
|
|
|
Protocol Neutral Information Model
|
- MEF 7.2 Information Model
- Interface Profiles for EMS, NE, RMI
- Cloud Services Management Interface
|
|
Protocol specific MIBs
|
- Service MIB (SNMP) EVC and UNI

- Service MIB (SNMP) ENNI and OVC
- Service MIB (SNMP) vNID RMI
|
|
Automated Operations
|
- Service Activation Testing
- Service Activation PDU
- Ethernet Service Latching Loopback
|
|
Network Elements, Service Mgmnt
|
|
|
Implementation Agreements
|
- MEF 30.1 Service OAM FM Phase 2

- MEF 35.0.x Service OAM PM Amendment -1SL
- MEF 35.0.x Service OAM PM Amendment - TCA
|
|
|
Interfaces
|
|
|
Services
|
|
|
Management
|
|
|
|
= Letter Ballot |
| Q2 2013 |