An Introduction to

The MEF Specifications

1. Overview of the technical work
2. The MEF specifications and Carrier Ethernet
3. MEF architecture
4. Summaries of current & recent specifications

September 2009 1
MEF Technical Committee
• Technical Committee
– The Technical Committee is
organized into Services, Architecture, Management,
Test & Measurement.
– The Technical Committee has active liaisons with
Standards
other standards organizations.

• 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, 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
 Specifications Timeline January 2011

MEF 23
MEF 4 MEF 7 MEF 16
Architecture EMS-NMS ELMI Class of
MEF 26
MEF 12 MEF 6.1 Service
ENNI
Architecture MEF 10.1 Ethernet MEF 22 MEF 27
MEF 17 MEF 25
MEF 11 Service Service Mobile UNI Type 2
MEF 2 Service
UNI MEF 15 Attributes Service Definitions Backhaul Part 5&6
Protection OAM
Framework Management Phase 2 OAM Phase 2 Phase 1

1-3 2004 2005 2006 2007 2008 2009 2010

MEF 13 MEF 18 MEF 20 MEF 10.1.1

MEF 3 MEF 10
UNI-IA Circuit Emulation UNI Type 2 Services MEF 10.2
Circuit Service Amendment
MEF 14 Services Test Suite MEF 21 Services
Emulation Attributes
Traffic MEF 19 UNI Type 2 MEF 24 Amendment
Phase 1
Management UNI Type 1 Test Suite UNI Type 2
MEF 6 MEF 7.1
MEF 8 Test Suite Test Suite Part 1 Test Suite
Service EMS-NMS
Circuit Emulation Part 2
Definitions
MEF 9
Services Test Suite

4
Approved MEF Specifications
REF Description
MEF 2 Requirements and Framework for Ethernet Service Protection
MEF 3 Circuit Emulation Service Definitions, Framework and
Requirements in Metro Ethernet Networks
MEF 4 Metro Ethernet Network Architecture Framework Part 1: Generic
Framework
MEF 6.1 Metro Ethernet Services Definitions Phase 2
MEF 7.1 Phase 2 EMS-NMS Information Model
MEF 8 Implementation Agreement for the Emulation of PDH Circuits
over Metro Ethernet Networks
MEF 9 Abstract Test Suite for Ethernet Services at the UNI
MEF 10.2 Ethernet Services Attributes Phase 2*
MEF 11 User Network Interface (UNI) Requirements and Framework
MEF 12.1 Carrier Ethernet Network Architecture Framework Part 2:
Ethernet Services Layer - Basic Elements
MEF 13 User Network Interface (UNI) Type 1 Implementation Agreement
MEF 14 Abstract Test Suite for Traffic Management Phase 1
MEF 15 Requirements for Management of Metro Ethernet Phase 1
Network Elements
* MEF 6.1 replaced MEF 6., MEF 7.1 replaced MEF 7, MEF 10 .2 replaced MEF 10.1.1, MEF 10.1, MEF 10 which replaced MEF 1 and MEF 5.

5
Approved MEF Specifications

REF Description
MEF 16 Ethernet Local Management Interface
MEF 17 Service OAM Framework and Requirements
MEF 18 Abstract Test Suite for Circuit Emulation Services
MEF 19 Abstract Test Suite for UNI Type 1
MEF 20 User Network Interface (UNI) Type 2 Implementation Agreement
MEF 21 Abstract Test Suite for UNI Type 2 Part 1: Link OAM
MEF 22 Mobile Backhaul Implementation Agreement Phase 1
MEF 23 Class of Service Implementation Agreement Part 1
MEF 24 Abstract Test Suite for UNI Type 2 Part 2: E-LMI
MEF 25 Abstract Test Suite for UNI Type 2 Part 3: Service OAM
MEF 26 External Network Network Interface (ENNI) – Phase 1
MEF 27 Abstract Test Suite For UNI Type 2 Part 5: Enhanced UNI
Attributes & Part 6: L2CP Handling

6
 MEF Technical Committee Work Nov 2010

Service Area Architecture Area Management Area Test and Measurement Area
MEF 6.1 Ethernet Services Definitions MEF 2 Protection Framework and MEF 7 EMS - NMS Information Model (TS) MEF 9 Abstract Test Suite for Ethernet
Phase 2 (TS) Requirements (TS) Services at the UNI (TS)

MEF 3 Circuit Emulation Service MEF 4 Carrier Ethernet Network MEF 15 Requirements for Management of MEF 14 Abstract Test Suite for Traffic
Requirements (TS) Architecture Framework Part 1: Generic Carrier Ethernet Phase 1 – Network Management Phase 1 (TS)
Framework (TS) Elements (TS)

MEF 8 Emulation of PDH over MENs (IA) MEF 11 UNI Framework and Requirements MEF 16 Ethernet Local Management MEF 18 Abstract Test Suite for CES over
(TS) Interface E-LMI (TS) Ethernet (TS)

MEF 10.2 Ethernet Services Attributes MEF 12.1 Carrier Ethernet Network MEF 17 Service OAM Requirements and MEF 19 Abstract Test Suite for UNI Type 1
Phase 2 (TS) Architecture Framework Part 2: Ethernet Framework (TS) (TS)
Services Layer (TS)

MEF 22 Mobile Backhaul (IA) MEF 13 User Network Interface Type 1 (IA) MEF 7.1 EMS-NMS Information Model (TS) MEF 21 UNI Type 2 Test Suite (TS)
Phase 2 Part 1 link OAM

MEF 23 Carrier Ethernet Class of Service MEF 20 UNI Type 2 (IA) Service OAM Performance Management MEF 24 UNI Type 2 Test Suite (TS)
(IA) (IA) Part 2 E-LMI

Mobile Backhaul (IA) Phase 2 MEF 26 External NNI (ENNI) Phase 1 (TS) Service OAM Fault Management IA MEF 25 UNI Type 2 Test Suite (TS)
Phase 1 Part 3 Service OAM

Carrier Ethernet Class of Service (IA) ENNI Amendment: Support for UNI Tunnel Delivered Throughput (IA) MEF 27 Abstract Test Suite for UNI Type 2
Phase 2 Access and V-UNI – Part 5, Enhanced UNI Attributes, and Part
6, L2CP Handling

MEF 10.2.1 Availability and Resiliency ENNI Amendment: OVC SLS Service OAM FM MIB Abstract Test Suite for ENNI (TS): Part 1
Performance Attributes Basic

OVC Service description ENNI Amendment: L2CP Tunneling Service OAM PM MIB Abstract Test Suite for ENNI (TS): Part 2

Ethernet Services Amendment: New 12.1.1 Ethernet Services Layer

Bandwidth Profile Architecture Phase 2 (Extensions)

NID Specification (TS)

Protection across External Interfaces

Ethernet Service Constructs (TS)

TS Technical Specification
IA Implementation Agreement

MEF 6.1 = MEF 6, MEF 10.1 = MEF 10, MEF 1 = MEF 5. MEF 7.1 = MEF 7, MEF 10.2 = MEF 10.1.1 = MEF 10.1

7
 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 Standardized Services Service Management Reliability Quality of Service Scalability
MEF 2 Architecture Area
MEF 3 Service Area Service Area
MEF 4 Architecture Area
MEF 6.1 Service Area Service Area Service Area
MEF 7.1 Management Area
MEF 8 Service Area
MEF 9 Test & Measurement Area Test & Measurement Area
MEF 10.2 Service Area Service Area Service Area
MEF 11 Architecture Area
MEF 12.1 Architecture Area Architecture Area
MEF 13 Architecture Area
MEF 14 Test & Measurement Area Test & Measurement Area Test & Measurement Area
MEF 15 Management Area
MEF 16 Management Area
MEF 17 Management Area
MEF 18 Test & Measurement Area Test & Measurement Area
MEF 19 Test & Measurement Area Test & Measurement Area
MEF 20 Architecture Area Architecture Area Architecture Area
MEF 21 & 24 Test & Measurement Area Test & Measurement Area
MEF 22 Service Area Service Area Service Area Service Area
MEF 23 Service Area Service Area Service Area
MEF 25 Test & Measurement Area Test & Measurement Area

MEF 26 Service Area Service Area Service Area

MEF 27 Test & Measurement Area Test & Measurement Area Test & Measurement Area Service Area 8
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
– Some Specifications refer to CENs (Carrier Ethernet
Networks) this term may be used interchangeably with
MENs

9
 Architecture

The following slides summarize the

Carrier Ethernet architecture

10
Carrier Ethernet Architecture (1)
Data moves from UNI to UNI across "the network" with a
layered architecture.

When traffic moves between ETH domains is does so at the

TRAN layer. This allows
Carrier Ethernet traffic to be
agnostic to the networks

Management Plane
that it traverses.

Control Plane
Application Services Layer
APP Layer (e.g., IP, MPLS, PDH, etc.)

Data Plane
ETH Layer Ethernet Services Layer
(Ethernet Service PDU)

TRAN Layer Transport Services Layer

(e.g., IEEE 802.1, SONET/SDH, MPLS)

11
Carrier Ethernet Architecture (2)
Ethernet Services “Eth” Layer

Carrier Ethernet
Network
Service Provider 1 Service Provider 2
Subscriber Subscriber
Site Site

UNI I-NNI E-NNI I-NNI UNI

CE CE

ETH ETH ETH ETH ETH ETH

UNI-C UNI-N E-NNI E-NNI UNI-N UNI-C

Ethernet Services Layer Terminology

UNI: User Network Interface, UNI-C: UNI-customer side, UNI-N network side
NNI: Network to Network Interface, E-NNI: External NNI; I-NNI Internal NNI
CE: Customer Equipment

12
User Network Interface (UNI)

• Introduction
– The User Network Interface in the MEF Specifications
is an abstract concept. On one side of this point the
service provider has responsibility and on the other,
the customer.
– As such, it appears in diagrams in various positions in
both in the MEF Specifications and in presentations
– This can be the source of confusion. The next several
slides covers this topic

13
MEF UNI – Enabler of OAM
• The User Network Interface (UNI)
– The UNI is the single point that is the demarcation
between the customer and the service
provider/Cable Operator/Carrier/MSO
– The UNI is typically at a port on an active device
owned and operated by the Service Provider
– The UNI in a Carrier Ethernet Network uses a
physical Ethernet Interface at operating speeds
10Mbs, 100Mbps, 1Gbps or 10Gbps

This picture shows a Carrier Ethernet network (the cloud)

terminating inside the customer premises
In this instance the UNI is
CE located at the port of the
Service Provider service provider edge
Network device located in the
customer premises.
The service provider
Customer Service provider
“cloud” is shown terminating in
responsibility responsibility the customer premises
UNI

CE: Customer Equipment, UNI: User Network Interface. MEF certified Carrier Ethernet products
14
MEF Carrier Ethernet Terminology
• Functional Elements of the UNI (1)
– There are two functional elements (typically*) located in two
connected devices situated on either side of the UNI demarcation
point:
• UNI-C: Executes the processes of the customer side
• UNI-N: Executes the processes of the network side
* All the functions of the UNI-N and UNI-C need not be located in the
same physical device as they may be located in several devices

UNI-C

CE
Carrier Ethernet
Network

UNI-N
customer
Service provider
responsibility
UNI responsibility

CE: Customer Equipment, UNI: User Network Interface. MEF certified Carrier Ethernet products 15
UNI-C and UNI-N Functional Elements (2)
Relationship between service frames (user generated), control and
Carrier Ethernet management frames
• Subscriber to Subscriber service frames (including Subscriber’s data,
control and management frames) are handled by UNI-C and UNI-N
data plane functional elements
• Control frames between Subscriber and Service Provider are handled
by UNI-C and UNI-N control plane functional elements
• Management frames between Subscriber and Service Provider are
handled by UNI-C and UNI-N management plane functional elements
EMS Interface

ETH Trunk
Management
Management plane
Management Links
plane Management
plane plane
ETH Access Link

Data
Dataplane Control
Control plane Control Data
Control plane Data plane
plane plane plane plane

UNI-C UNI-N
Service Frame Flow

UNI Reference
Point

16
 How the UNI is shown in MEF Technical Specifications
Diagrams in the Specifications show the UNI in various positions.
All three are valid but the first is by far the most likely to be seen in an operational network

2. At the port of the customer’s equipment

1. At the port of the service provider equipment
• (Less typical although in theory the Service providers
• (The usual position in the customer
edge device need not be on the customer premises)
premises or multi-tenant location)

UNI

UNI

Customer
Premises
Equipment Service Provider Carrier
Customer Ethernet Network
Premises Service Provider Carrier
Equipment Ethernet Network

UNI

3. In the middle of the wire between

Customer and Service Provider
• (This is only an abstract view)
Customer
Premises Service Provider Carrier
Equipment Ethernet Network

17
Overview of the Specifications

18
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 three 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

19
Technical Work – Key Areas/Specifications
Carrier Ethernet Services Latest & ongoing
Specifications technical work

Carrier Ethernet services attributes and definitions

Key recent MEF technical specifications
MEF 6.1 MEF 10.2 – MEF 20 UNI Type 2 Implementation Agreement
Metro Ethernet Services Ethernet Services
Definitions Phase 2 Attributes Phase 2 – MEF 22 Mobile Backhaul Implementation
Agreement

– MEF 26 External Network Network Interface

(ENNI) Phase 1
Carrier Ethernet services Certification Test Suite

MEF 9 MEF 14 19 ongoing projects in key areas

Abstract Test Suite for Abstract Test Suite for
Ethernet Services at Traffic Management – Services
the UNI phase 1
– Management

– Architecture

–
MEF Certification Test (Certification)

20
 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

21
 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", 5. MAY This word, or the adjective
mean that the definition is an absolute requirement of the "OPTIONAL", mean that an item is truly
specification. optional. One vendor may choose to include
2. MUST NOT This phrase, or the phrase "SHALL NOT", the item because a particular marketplace
mean that the definition is an absolute prohibition of the requires it or because the vendor feels that it
specification. enhances the product while another vendor
3. SHOULD This word, or the adjective "RECOMMENDED", may omit the same item. An implementation
mean that there may exist valid reasons in particular which does not include a particular option
circumstances to ignore a particular item, but the full MUST be prepared to interoperate with
implications must be understood and carefully weighed another implementation which does include
before choosing a different course. the option, though perhaps with reduced
4. SHOULD NOT This phrase, or the phrase "NOT functionality. In the same vein an
RECOMMENDED" mean that there may exist valid reasons in implementation which does include a particular
particular circumstances when the particular behavior is option MUST be prepared to interoperate with
acceptable or even useful, but the full implications should be another implementation which does not
understood and the case carefully weighed before include the option (except, of course, for the
implementing any behavior described with this label. feature the option provides.)

22
MEF Specifications Overview

Metro Ethernet Network Architecture Framework

MEF 4 Part 1: Generic Framework

Purpose Introduces the framework and terminology for the services (Eth) layer

All (Equipment Manufacturers, Service Providers & Enterprises), since it

Audience provides the fundamental understanding of the Carrier Ethernet
architecture
Technical Committee Architecture Area

MEF 10.2 Ethernet Services Attributes Phase 2

Defines the service attributes and parameters required to offer the
Purpose
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
Audience 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
overall network.
Technical Committee Service Area

23
MEF Specifications Overview

MEF 6.1 Metro Ethernet Services Definitions Phase II

Purpose 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
Audience 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

Metro Ethernet Network Architecture Framework

MEF 12.1
Part 2: Ethernet Services Layer
Defines the Ethernet Services (ETH) Layer as the specific layer network
Purpose responsible for delivery of Ethernet Protocol Data Units across internal
and external interfaces.
Equipment Manufacturers building devices that will carry Carrier Ethernet
Audience
Services. Useful for Service Providers architecting their systems.
Technical Committee Architecture Area

24
MEF Specifications Overview

Phase 2 EMS-NMS* Information Model

MEF 7.1 *Element Management System–Network Management System
Provides a standard for carrier management systems to enable
Purpose
configuration and fault management of Metro Ethernet services.
Equipment Manufacturers building devices that will carry Carrier Ethernet
Audience
Services. Useful for Service Providers architecting their systems.
Technical Committee Management Area

Requirements for Management of Metro Ethernet Phase 1

MEF 15 Network Elements
Specifies the network management requirements to be met by Network
Purpose
Elements supporting Ethernet Service Phase 1
Equipment Manufacturers building devices that will carry Carrier Ethernet
Audience
Services. Useful for Service Providers architecting their systems.
Technical Committee Management Area

25
MEF Specifications Overview

MEF 16 Ethernet Local Management Interface (E-LMI)

Enables customer equipment to receive information regarding the status
Purpose and attributes of Ethernet Services thus allowing automatic configuration
and improved Subscriber network performance.
Equipment manufacturers of Customer Edge devices and of Service
Audience Provider equipment. Useful for Service Providers architecting their
systems.
Technical Committee Management Area

MEF 17 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
Purpose
mechanisms. It also provides context for several MEF specifications (UNI
type 2 and E-NNI) and the work of other standards bodies
Equipment Manufacturers building devices and Service Providers
Audience
architecting their systems.
Technical Committee Management Area

26
MEF Specifications Overview

MEF 11 User Network Interface (UNI) Requirements and Framework

Defines a split demarcation function between the customer (Subscriber),
Purpose
and the Service Provider
MEF 13 User Network Interface (UNI) Type 1 Implementation Agreement
This allows existing Ethernet devices (switch, router, workstation, etc)
Purpose acting as Customer Edge devices to be compliant to this IA with no
additional software or hardware upgrades
MEF 20 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
Purpose 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
Audience
Services. Useful for Service Providers architecting their systems.
Technical Committee Architecture Area

27
MEF Specifications Overview

MEF 9 Abstract Test Suite for Ethernet Services at the UNI

Defines the test suite for conformance of Ethernet services and equipment when
Purpose deployed at the UNI

MEF 14 Abstract Test Suite for Traffic Management Phase 1

Defines the requirements and corresponding test procedures for Service
Purpose 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

Audience Specifications. Service Providers conducting who require that their services comply
to MEF Specifications

Technical Committee Test and Measurement Area

28
MEF Specifications Overview

MEF 18 Abstract Test Suite for CES

Specifies testing procedures for pass/fail assessment of conformance
Purpose
with each of the operating modes in MEF 8.
Equipment Manufacturers building devices that will carry TDM traffic
Audience across Carrier Ethernet Networks. Useful for Service Providers
architecting their systems.
Technical Committee Test and Measurement Area

MEF 19 Abstract Test Suite for UNI Type 1

Supplements the MEF test specifications MEF 9, and MEF 14 with test
Purpose
procedures for UNI manual configuration mode defined in MEF 13

MEF 21/24 Abstract Test Suite for UNI Type 2, Phase 1: Link OAM

Purpose Provides the first of six possible test suites for UNI type 2 (MEF 20)

Equipment Manufacturers building devices that will carry Carrier Ethernet

Audience
Services. Useful for Service Providers architecting their systems.
Technical Committee Test and Measurement Area

29
MEF Specifications Overview

MEF 2 Requirements and Framework for Ethernet Service Protection

Defines a broad frame work for hop-by-hop and end-to-end service level
Purpose
protection.
Equipment Manufacturers building devices that will carry Carrier Ethernet
Audience
Services. Useful for Service Providers architecting their systems.
Technical Committee Architecture Area

MEF 23 Class of Service Implementation Phase 1

Defines sets of classes of service, each set having two to four classes of
Purpose services. For each set, recommendations for traffic type mapping (e.g.,
voice signaling) to each of class of service within the set will be provided.

Equipment Manufacturers building devices and Service Providers

Audience
architecting their systems.
Technical Committee Management Area

30
MEF Specifications Overview

Circuit Emulation Service Definitions, Framework and

MEF 3 Requirements in Metro Ethernet Networks
Circuit Emulation Service “tunnels” TDM traffic through a Metro Ethernet
Purpose network allowing inclusion of legacy networks within a Carrier Ethernet
environment
Equipment Manufacturers supporting devices that provide Circuit
Audience Emulation over Carrier Ethernet Services.
Useful for Service Providers architecting their systems.
Technical Committee Service Area

Implementation Agreement for the Emulation of PDH Circuits over

MEF 8 Metro Ethernet Networks
Gives precise instructions for implementing interoperable CES
equipment that reliably transport TDM circuits across Metro Ethernet
Purpose
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
Audience Emulation over Carrier Ethernet Services.
Useful for Service Providers architecting their systems.
Technical Committee Service Area

31
Recently Approved Specifications

32
 ENNI Baseline (MEF26)
Operator Service Provider
Simple 2-carrier Subscriber Network Network Subscriber
Sites UNI Sites
Model UNI
OVC_A ENNI OVC_B
UNI UNI

UNI
UNI

Transit Model Service Provider 1

Transit Operator
Service Provider 2
Network Network
UNI UNI
OVC_A OVC_C
ENNI OVC_B ENNI
UNI UNI

UNI
Subscriber UNI
Subscriber
Sites Sites

• External Network-to-Network Interface • Key ENNI requirements

(ENNI) for service availability – Services: p2p and mp EVC types, single and multiple
– Simple 2-carrier and multi-carrier service models CoS per EVC
– Ethernet Virtual Connection (EVC) between UNIs – Encapsulation: Standard S-Tag frame format
spread across multiple networks – Scalability: 1 and 10 Gbps PHYs
– Operator Virtual Connection (OVC) for each EVC – ENNI Protection: 2-link LAG, active/standby, LACP
segment

33
 7.1 Phase 2 EMS-NMS Information Model

• Describes applicability of Q.840.1 management

entity elements.
• Includes object class, attributes, relationships, methods, and
notifications applied to the Metro Ethernet EMS-NMS Interface.
• Mapping between the information model presented in Q.840.1 and TM
Forum’s MTNM 3.5 Connectionless Network Model.
• Includes the definition of objects in support of
E-NNI and SOAM

Above is example of mapping between Q.840.1 and MTNM 3.5

34
MEF 27 Abstract Test Suite for UNI

MEF 27 Abstract Test Suite for UNI Type 2 – Part

5, Enhanced UNI Attributes, and Part 6, L2CP
Handling
• Defines test procedures based on requirements for UNI Type
2 described in MEF 20 UNI Type 2 Implementation
Agreement. The overall Abstract Test Suite for UNI Type 2
will be composed of the following parts: Link OAM, E-LMI,
Service OAM, Protection, Enhanced UNI Attributes and
L2CP handling.

35
MEF Work in Development

36
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: ……

37
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

38
 MEF Technical Committee Work Nov 2010

Service Area Architecture Area Management Area Test and Measurement Area
MEF 6.1 Ethernet Services Definitions MEF 2 Protection Framework and MEF 7 EMS - NMS Information Model (TS) MEF 9 Abstract Test Suite for Ethernet
Phase 2 (TS) Requirements (TS) Services at the UNI (TS)

MEF 3 Circuit Emulation Service MEF 4 Carrier Ethernet Network MEF 15 Requirements for Management of MEF 14 Abstract Test Suite for Traffic
Requirements (TS) Architecture Framework Part 1: Generic Carrier Ethernet Phase 1 – Network Management Phase 1 (TS)
Framework (TS) Elements (TS)

MEF 8 Emulation of PDH over MENs (IA) MEF 11 UNI Framework and Requirements MEF 16 Ethernet Local Management MEF 18 Abstract Test Suite for CES over
(TS) Interface E-LMI (TS) Ethernet (TS)

MEF 10.2 Ethernet Services Attributes MEF 12.1 Carrier Ethernet Network MEF 17 Service OAM Requirements and MEF 19 Abstract Test Suite for UNI Type 1
Phase 2 (TS) Architecture Framework Part 2: Ethernet Framework (TS) (TS)
Services Layer (TS)

MEF 22 Mobile Backhaul (IA) MEF 13 User Network Interface Type 1 (IA) MEF 7.1 EMS-NMS Information Model (TS) MEF 21 UNI Type 2 Test Suite (TS)
Phase 2 Part 1 link OAM

MEF 23 Carrier Ethernet Class of Service MEF 20 UNI Type 2 (IA) Service OAM Performance Management MEF 24 UNI Type 2 Test Suite (TS)
(IA) (IA) Part 2 E-LMI

Mobile Backhaul (IA) Phase 2 MEF 26 External NNI (ENNI) Phase 1 (TS) Service OAM Fault Management IA MEF 25 UNI Type 2 Test Suite (TS)
Phase 1 Part 3 Service OAM

Carrier Ethernet Class of Service (IA) ENNI Amendment: Support for UNI Tunnel Delivered Throughput (IA) MEF 27 Abstract Test Suite for UNI Type 2
Phase 2 Access and V-UNI – Part 5, Enhanced UNI Attributes, and Part
6, L2CP Handling

MEF 10.2.1 Availability and Resiliency ENNI Amendment: OVC SLS Service OAM FM MIB Abstract Test Suite for ENNI (TS): Part 1
Performance Attributes Basic

OVC Service description ENNI Amendment: L2CP Tunneling Service OAM PM MIB Abstract Test Suite for ENNI (TS): Part 2

Ethernet Services Amendment: New 12.1.1 Ethernet Services Layer

Bandwidth Profile Architecture Phase 2 (Extensions)

NID Specification (TS)

Protection across External Interfaces

Ethernet Service Constructs (TS)

TS Technical Specification
IA Implementation Agreement

MEF 6.1 = MEF 6, MEF 10.1 = MEF 10, MEF 1 = MEF 5. MEF 7.1 = MEF 7, MEF 10.2 = MEF 10.1.1 = MEF 10.1

39
Hierarchical Bandwidth Profile (HBWP)

• Example of a HBWP
– The customer has a CIR/EIR per CoS
– The customer has an overall rate limiter per EVC (not
shaper)
"Classical"
CIR/EIR per
EVC.CoS

A second
rate limiter
per EVC

40
Class of Service Phase 1 (MEF 23)
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.

Multipoint EVC

UNI MEN 1 MEN 2 UNI

CE CE Multipoint EVC
UNI UNI
UNI MEN UNI

Point-Point EVC CE CE

UNI MEN 1 ENNI MEN 2 UNI

CE CE
Point-Point EVC

UNI MEN UNI

UNI Carrier Ethernet CoS IA ENNI Carrier Ethernet CoS IA
Application Point (recommended Application Point (mandatory PCP CE CE
PCP/DSCP values, mandatory Values if 802.1ad and mandatory
Performance Objectives) Performance Objectives)

41
Class of Service Phase 2

• Primary Goal:
– Add Performance Objectives and related parameter values to
MEF 23 CoS Model for H, M and L Classes of Service
• Status and Issues
– Currently in Straw Ballot
– Significant contributions in the areas of
• Performance parameter values and applicability are still fuzzy
• Performance Tiers
• Contributions needed: BWP constraints, MBH Objective
ranges to values, and ENNI mapping of ‘3 CoS’ subsets,
Handling of L2CPs
– Ethernet Network Sections and Multipoint Objectives: Postpone
to Phase 3 or develop contributions?

42
 UNI Tunnel Access Service

• UNI Tunnel Access (UTA) OVC connects the

Virtual UNI (VUNI) and Remote UNI (RUNI)
– Supports wholesale access model
– Operators supporting tunnel are not aware of service
details
– Operator supporting VUNI responsible for service Operator 3 EVC1
details
UNI

ENNI EVC2
Operator 2
Operator 1
EVC1 ENNI
UNI Tunnel Access
OVC connects the RUNI
UNI UNI and ENNI

EVC2
UNI
VUNI UNI

43
 E-NNI Constructs: Putting it Together
• Access Network Provider
– Provides CEVC1 connection between Subscriber UNI1 (RUNI) and E-
NNI1 with Transport Network Provider
• Transport Network Provider
– Provides CEVC2 connection between E-NNI1 and E-NNI2 with Ethernet
Service Provider
• Ethernet Service Provider
– Provides connection to E-NNI2 with Transport Network Provider
– Provides End-to-End Ethernet Service to Subscriber
• Connects VUNI to Terminating Tunnel
• Provides EVC between UNI1 and UNI2
RUNI VUNI

E-NNI 1 E-NNI 2
UNI 1 Access Network Transport Network Ethernet Service UNI 2
Terminating Tunnel Terminating Tunnel
Provider Provider Provider
Subscriber Subscriber
CEVC1 CEVC2 EVC

44
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
• Includes Ethernet Sub-Network Connection (ESNC) and attributes.
• Includes Tunnel Construct (Tunnel Endpoint (TE)), a logical entity,
associated with external interfaces and attributes.

ESN

TE Mouth

TE Stem

Tunnel Construct

IMPORTANT NOTE
This information is preliminary
and is subject to change 45
Network Interface Devices (NID) Specification

• A NID is a network element or device that terminates

both Ethernet Transport and service domains.
• Five types of NIDs identified:
• Transport NID – MEF Service Unaware
• Service NID – MEF Subscriber Service Aware
• Tunnel NID – MEF Tunnel Service Aware
• Tunnel & Service NID – MEF Tunnel Service and Subscriber Service Aware
owned and controlled by single Operator.
• Hybrid NID – MEF Tunnel Service and MEF Subscriber Service Aware owned
and controlled by Out Of Franchise Operator. Hybrid NIDs allow Out Of
Franchise Operator to relinquish control of some functions to Service Provider.

Partial UNI-N Metro Ethernet NID Metro Ethernet

Inter-NID
Interface in NID Towards Metro Ethernet Towards NID
Interface
towards UNI-C Edge Interface Interface

Customer Carrier Carrier

Ethernet Ethernet
Equipment
NID #1 NID #2 Carrier Ethernet
Network Edge

IMPORTANT NOTE
This information is preliminary
and is subject to change 46
 The Hybrid NID Service (HNS)
The Hybrid NID Service (HNS) - a standard MEF defined
service provided by an Out of Franchise (OOF) Operator,
and include:
– An OOF-owned and partially managed Hybrid NID
– A tunnel through the OOF network, between ENNI and remote UNI
• Terminating service at OOF, as a MEF-compliant UNI interface
• Multi-CoS, mapping SP CoS instances into OOF tunnel classes
– SP secure RUNI Management Interface (RMI) channel to the NID
• Using a reserved CE-VLAN ID for SP access (may be encrypted)
– A standard set of managed objects for the SP
• Access to configure UNI, SOAM, and service attributes
• Receive performance information and event notifications
Service Provider Network OOF Operator Network

Main Data Remote Site in

ENNI
Center in NE NE NE NE Paris
Los Angeles
NID NE NE NID
NE NE

NE NE NE NE
UNI UNI
47
 Ethernet OAM
Customer Service Provider 1 Service Provider 2 Customer
Site Site
UNI ENNI UNI

CE CE

MEF & IEEE 802.1ag Service OAM (UNI to UNI, UNI to ENNI)
and ITU Y.1731

IEEE 802.3ah Link OAM Link OAM Link OAM

• The Service OAM (SOAM) framework, and associated Implementation Agreements,

establishes the blueprint for how the mechanisms, as specified by IEEE and ITU-T, will be
used in Carrier Ethernet networks in support of MEF defined services

48
SOAM Fault Management
• Create an Implementation Agreement (IA) that sets
the foundation for Fault and Performance
Management
– SOAM FM specifies the use of standard protocols, mechanisms, and procedures
for monitoring the status of Ethernet Virtual Connections (EVCs) and Operator
Virtual Connections (OVCs) across a defined OAM Domain

• Base functional requirements for Fault Management

(Connectivity, Link Trace, Loopback)
• SOAM FM uses the protocols of [802.1ag] and
[Y.1731] in order to determine the status of and
troubleshoot connectivity across a particular
domain.

49
SOAM Performance Management
• Requirements for measuring performance
metrics, as defined in MEF 10.2 Right: Solution Components.
NE conducts and stores EMS/N
– Frame Delay performance measurements.
MS

– Frame Delay Variation EMS-NMS collects, processes

to determine one or more
Stored
Measurement
– Frame Loss Ratio performance attributes for the
NE s
EVC
–
B
(Service) Availability
• ITU-T has defined measurement metrics for NE A Initiated
Measuremen
NE C

items 1-3 ts

– MEF is proposing an extension to ITU-T Y.1731 for a

single mechanism to monitor EVC-based performance
– Major work underway.
• MEF has defined measurement framework for
items 1-4
– Ethernet Synthetic Frame-based measurements
– MEF 10.2 defines the metrics in technical detail

SOAM-PM, leveraging work in ITU-T, specifies

requirements for measuring performance of MEF services,
as defined in MEF 10.2
IMPORTANT NOTE
This information is preliminary
and is subject to change 50
Delivered Throughput
• Extension of SOAM protocols specifies Layer 2 throughput
performance metrics (measured and derived outputs) to
existing Ethernet OAM protocol [ITUY.1731].
• Gives customers and service providers the ability to obtain
instantaneous “IN-SERVICE” historical observed throughput
performance such as PM fault isolation for “In-Service” point
to point Ethernet services
Collective group of
PM Buckets and Bins

TPL Alarm Observed TPL Observed

Classification Statistics throughput
Logging Statistics

Threshold crossing Throughput loss Observed Throughput

comparison Calculation Calculations
(MAX / AVG)

Throughput performance counters

IMPORTANT NOTE
This information is preliminary
and is subject to change 51
Availability

• New Project, with goals to

– Amendment to MEF 10.2, in the performance attribute section, to
align MEF service availability definition with the ITU-T Y.1563
definition
– Add resiliency metric definitions (stretch goal) to support MBH
Phase 2 requirements
– Service Level Specification impact

52
Operator Virtual Connection (OVC)
Operator Virtual Connection (OVC) is an association of external interfaces (UNIs or ENNIs)
of a single Operator
Focus of project on
CE OOF Operator OVC

SP ‘OOF’ Operator
network network
ENNI UNI
UNI
CE CE
Ethernet Virtual Connection
Reference
Point
OVC OVC
EVC

• Goal is to specify Ethernet Access Services

• Phase 1 focuses on two p2p OVC service definitions, a transparent service and a
standard service
• Detailed technical service definitions, based on attributes defined in MEF 26 (ENNI)

53
 What is Service Protection?
• Service Protection is a specification which specifies the MEF requirements
for Service Protection across External Interfaces . The protection
mechanism provides local protection of Ethernet services between network
boundaries.

Interconnected
Interconnected

Zone
Zone

MEN MEN MEN

Requirements Requirements Etc…

Addressing this area Addressing this area
• The nodes, ports, and links connecting the adjacent networks are referred to as
the interconnection zone.
• The node in each of the networks which at any given moment conveys traffic
from the network to the interconnected zone, as well as from the interconnected
zone to the network.

54
MEF Mobile Backhaul Implementation Agreement
• Purpose
– Provides generic specification for Ethernet backhaul architectures for
mobile networks (2G, 3G, 4G)
ITEM PHASE 1 PHASE 2
– Explains how to apply existing MEF UNI  
specifications
Service Types  
– User-Network Interface requirements Link OAM  
– Service Requirements Service OAM FM  
• Service definitions Service OAM PM 
• Clock synchronization for
CoS  
application support
Performance
recommendations 
RAN BS

UNI Packet based sync  

UNI SyncE 
Resiliency 
Carrier Ethernet GSM, WCDMA,
RAN NC
Network CDMA2000, WiMAX  
UNI 802.16e

RAN BS LTE 

IMPORTANT NOTE
This information is preliminary
and is subject to change 55
ENNI Abstract Test Suites

• Tests the function, protection & recovery

mechanisms of two interoperating MENs via
their External Network to Network Interfaces.
– Part 1 Basic Abstract Test Suites test attributes for
CEVC, E-NNI, CEVC End Point per E-NNI, VUNI, and
CEVC per UNI / CEVC per VUNI.
– Part 3 Protection Abstract Test Suites defined per Link
Aggregation requirements of the E-NNI project which
defines test cases for protection mechanisms in
accordance with the requirements and service
attributes as specified in the E-NNI Phase 1.
– Part 2 OAM Abstract Test Suites and Part 4 Bandwidth
Profile Abstract Test are to be defined.

IMPORTANT NOTE
This information is preliminary
and is subject to change 56
For more information regarding joining the MEF:
Visit: www.metroethernetforum.org
Email us at: manager@metroethernetforum.org
Call us at: +1 310 642 2800 (California, USA)

Accelerating Worldwide Adoption of

Carrier-class Ethernet Networks and Services
57