An Introduction to The MEF Specifications

1
An Introduction to The MEF Specifications

• Overview of the technical work
• The MEF specifications and Carrier Ethernet
• MEF architecture
• Summaries of current recent specifications

September 2009
2
The Technical Work of the MEF

• Technical Committee
• The Technical Committee is organized into
  Services, Architecture, Management, Test
  Measurement.
• The Technical Committee has active liaisons with
  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

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

4
Approved MEF Specifications
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 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.1 Ethernet Services
Attributes Phase 2 MEF 11 User Network
Interface (UNI) Requirements and Framework MEF
12 Metro Ethernet Network Architecture Framework
Part 2 Ethernet Services Layer 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 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
Notes MEF 6.1 replaced MEF 6. MEF 10.1 replaced
MEF 10, which replaced MEF 1 and MEF 5. MEF
10.1.1 is an amendment to MEF 10.1
5
Specifications Timeline
MEF 23
MEF 16
MEF 4
MEF 7
Class of Service
ELMI
Architecture
EMS-NMS
MEF 12
MEF 6.1
Architecture
MEF 10.1
MEF 22
Ethernet Service Definitions Phase 2
MEF 17
MEF 11
Mobile Backhaul Phase 1
MEF 25
Service OAM
MEF 2
MEF 15
Service AttributesPhase 2
Service OAM
Protection
UNI Framework
Management
2009
2001-3
2006
2005
2004
2007
2008
MEF 13
MEF 18
MEF 20 UNI Type 2 MEF 21 UNI Type 2 Test Suite
Part 1
MEF 3
MEF 10
MEF 10.1.1 Services Amendment MEF 24 UNI Type
2 Test Suite Part 2
UNI-IA
Circuit Emulation Services Test Suite
Circuit Emulation
Service Attributes Phase 1
MEF 14
MEF 19
Traffic Management Test Suite
UNI Type 1 Test Suite
MEF 6
MEF 8
Service Definitions
Circuit Emulation
MEF 9
Services Test Suite
6
MEF Technical Committee Work Dashboard
August 2008
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
Service Management
Reliability
Quality of Service
Standardized Services
Scalability
MEF Specs


Architecture Area


MEF 2
Service Area

Service Area


MEF 3
Architecture Area




MEF 4
Service Area

Service Area

Service Area
MEF 6.1
Management Area




MEF 7
Service Area




MEF 8
Test Measurement Area

Test Measurement Area


MEF 9
Service Area
Service Area


Service Area
MEF 10.1
Architecture Area




MEF 11
Architecture Area



Architecture Area
MEF 12
Architecture Area




MEF 13

Test Measurement Area
Test Measurement Area
Test Measurement Area

MEF 14

Management Area



MEF 15

Management Area



MEF 16

Management Area



MEF 17

Test Measurement Area
Test Measurement Area

MEF 18

Test Measurement Area
Test Measurement Area

MEF 19
MEF 20
Architecture Area



Architecture Area

Test Measurement Area
Test Measurement Area

MEF 21
8
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
Service Management
Reliability
Quality of Service
Standardized Services
Scalability
MEF Specs




MEF 22
Service Area
Service Area
Service Area



MEF 23
Service Area
Service Area
Service Area




MEF 24
Test Measurement Area
Test Measurement Area


MEF 25
Test Measurement Area
Test Measurement Area
9
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

10
Architecture

• The following slides summarize the Carrier
  Ethernet architecture

11
Carrier Ethernet Architecture (1)
Data moves from UNI to UNI across "the network"
with a layered architecture.                      
                                                 W
hen traffic moves between ETH domains is does so
at the TRAN layer. This allows Carrier Ethernet
traffic to be agnostic to the networks that it
traverses.
Management Plane
APP Layer
Control Plane
Data Plane
ETH Layer
TRAN Layer
12
Carrier Ethernet Architecture (2)
Ethernet Services Eth Layer
Carrier Ethernet Network
Service Provider 1
Service Provider 2
Subscriber Site
Subscriber Site
UNI
UNI
I-NNI
E-NNI
I-NNI
CE
CE
Ethernet Services Layer Terminology
ETH UNI-C
ETH UNI-N
ETH UNI-N
ETH E-NNI
ETH UNI-C
ETH E-NNI
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
13
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

14
MEF Carrier Ethernet Terminology

• 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 located at
the port of the service provider edge device
located in the customer premises. The service
provider cloud is shown terminating in the
customer premises
CE
Carrier Ethernet Network
customer responsibility
Service provider responsibility
UNI
CE Customer Equipment, UNI User Network
Interface. MEF certified Carrier
Ethernet products
15
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 responsibility
Service provider responsibility
UNI
CE Customer Equipment, UNI User Network
Interface. MEF certified Carrier
Ethernet products
16
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 Subscribers 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

17
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 customers equipment
• (Less typical although in theory the Service
  providers edge device need not be on the
  customer premises)

• 1. At the port of the service provider equipment
• (The usual position in the customer premises or
  multi-tenant location)

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

• 3. In the middle of the wire between Customer and
  Service Provider
• (This is only an abstract view)

Customer Premises Equipment
Service Provider Carrier Ethernet Network
18
Overview of the Specifications
19
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
20
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 E-LAN 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

21
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
22
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

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.)
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.
23
MEF Specifications Overview
MEF 4
Metro Ethernet Network Architecture Framework
Part 1 Generic Framework
Purpose
Introduces the framework and terminology for the
services (Eth) layer
Audience
All (Equipment Manufacturers, Service Providers
Enterprises), since it provides the fundamental
understanding of the Carrier Ethernet architecture
Technical Committee Architecture Area
Ethernet Services Attributes Phase 2
MEF 10.1
Purpose
Defines the service attributes and parameters
required to offer the services defined in MEF 6.
Updated from Original MEF 10
Audience
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.
Standardized Services
Technical Committee Service Area
24
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)
Audience
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
MEF 12
Metro Ethernet Network Architecture Framework
Part 2 Ethernet Services Layer
Purpose
Defines the Ethernet Services (ETH) Layer as the
specific layer network responsible for delivery
of Ethernet Protocol Data Units across internal
and external interfaces.
Audience
Equipment Manufacturers building devices that
will carry Carrier Ethernet Services. Useful for
Service Providers architecting their systems.
Technical Committee Architecture Area

25
MEF Specifications Overview
MEF 7
EMS-NMS Information ModelElement Management
SystemNetwork Management System
Purpose
Provides a standard for carrier management
systems to enable configuration and fault
management of Metro Ethernet services.
Audience
Equipment Manufacturers building devices that
will carry Carrier Ethernet Services. Useful for
Service Providers architecting their systems.
Technical Committee Management Area
Requirements for Management of Metro Ethernet
Phase 1 Network Elements
MEF 15
Purpose
Specifies the network management requirements to
be met by Network Elements supporting Ethernet
Service Phase 1
Audience
Equipment Manufacturers building devices that
will carry Carrier Ethernet Services. Useful for
Service Providers architecting their systems.
Technical Committee Management Area
26
MEF Specifications Overview
Ethernet Local Management Interface (E-LMI)
MEF 16
Purpose
Enables customer equipment to receive information
regarding the status and attributes of Ethernet
Services thus allowing automatic configuration
and improved Subscriber network performance.
Audience
Equipment manufacturers of Customer Edge devices
and of Service Provider equipment. Useful for
Service Providers architecting their systems.
Technical Committee Management Area
Service OAM Requirements Framework Phase 1
MEF 17
Purpose
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
Audience
Equipment Manufacturers building devices and
Service Providers architecting their systems.
Technical Committee Management Area
27
MEF Specifications Overview
MEF 11
User Network Interface (UNI) Requirements and
Framework
Purpose
Defines a split demarcation function between the
customer (Subscriber), and the Service Provider
MEF 13
User Network Interface (UNI) Type 1
Implementation Agreement
Purpose
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
MEF 20
User Network Interface (UNI) Type 2
Implementation Agreement
Purpose
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
Audience
Equipment Manufacturers building devices that
will carry Carrier Ethernet Services. Useful for
Service Providers architecting their systems.
Technical Committee Architecture Area
28
MEF Specifications Overview
MEF 9
Abstract Test Suite for Ethernet Services at the
UNI
Purpose
Defines the test suite for conformance of
Ethernet services and equipment when deployed at
the UNI
Abstract Test Suite for Traffic Management Phase 1
MEF 14
Purpose
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
Audience
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
29
MEF Specifications Overview
Abstract Test Suite for CES
MEF 18
Purpose
Specifies testing procedures for pass/fail
assessment of conformance with each of the
operating modes in MEF 8.
Audience
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
Abstract Test Suite for UNI Type 1
MEF 19
Purpose
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
MEF 21/24
Provides the first of six possible test suites
for UNI type 2 (MEF 20)
Purpose
Audience
Equipment Manufacturers building devices that
will carry Carrier Ethernet Services. Useful for
Service Providers architecting their systems.
Technical Committee Test and Measurement Area
30
MEF Specifications Overview
Requirements and Framework for Ethernet Service
Protection
MEF 2
Purpose
Defines a broad frame work for hop-by-hop and
end-to-end service level protection.
Audience
Equipment Manufacturers building devices that
will carry Carrier Ethernet Services. Useful for
Service Providers architecting their systems.
Technical Committee Architecture Area
Class of Service Implementation Phase 1
MEF 23
Purpose
Defines sets of classes of service, each set
having two to four classes of 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.
Audience
Equipment Manufacturers building devices and
Service Providers architecting their systems.
Technical Committee Management Area
31
MEF Specifications Overview
Circuit Emulation Service Definitions, Framework
and Requirements in Metro Ethernet Networks
MEF 3
Purpose
Circuit Emulation Service tunnels TDM traffic
through a Metro Ethernet network allowing
inclusion of legacy networks within a Carrier
Ethernet environment
Audience
Equipment Manufacturers supporting devices that
provide Circuit 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 Metro Ethernet Networks
MEF 8
Purpose
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
Audience
Equipment Manufacturers supporting devices that
provide Circuit Emulation over Carrier Ethernet
Services.Useful for Service Providers
architecting their systems.
Technical Committee Service Area
32
Recently Approved Specifications
33
MEF 20 Advances Carrier Ethernet Deployment

• Carrier Ethernet growth challenges
• The success of Carrier Ethernet brings its own
  challenges, not the least of these is operational
  scalability
• Until now, MEF specifications have defined manual
  management process relying on manual or ad hoc
  processes. This cannot scale.
• MEF 20
• Introduces automated processes for managing
  services, fault monitoring and management
  enabling at UNI level
• Carrier Ethernet networks to scale
• Carrier Ethernet networks to operate at reduce
  cost and
• Creation of a framework for the dynamic service
  provisioning that will leverage the inherent
  benefits of MEF-defined Carrier Ethernet services

34
The MEF User Network Interface

• 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

• In this instance the UNI is located at the port
  of the service provider edge device located in
  the customer premises.
• The service provider cloud is shown
  terminating in the customer premises

CE
Carrier Ethernet Network
customer responsibility
Service provider responsibility
UNI
CE Customer Equipment, UNI User Network
Interface. MEF certified Carrier
Ethernet products
35
Functional Elements of the UNI

• 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 responsibility
Service provider responsibility
UNI
CE Customer Equipment, UNI User Network
Interface. MEF certified Carrier
Ethernet products
36
MEF 20 UNI Type 2 Overview (In context of MEF 11)

• MEF 11 introduced 3 types of UNI
• UNI Type 1 (now defined in MEF 13), November 2005
• Service Provider and Customer manually configure
  the UNI-N and UNI-C for services
• UNI Type 1.1 and 1.2 are defined
• Type 1.1 Non-multiplexed UNI for Services like
  EPL
• Type 1.2 Multiplexed UNI for Services like EVPL
• UNI Type 2 (now defined in MEF 20)
• An automated implementation model allowing UNI-C
  to retrieve EVC status and configuration
  information from UNI-N
• Enhanced UNI attributes
• Additional fault management and protection
  functionality
• Backward compatibility with UNI Type 1
• UNI Type 3 (Possible future MEF Specification)
• Allows the UNI-C to request, signal and negotiate
  EVCs and its associated Service Attributes to the
  UNI-N. UNI
• Type 3 is for further study.

37
Functionality and Scope of MEF 20

• Ethernet Local Management Interface (E-LMI)
• Allows UNI-C to retrieve EVC status and service
  attributes from UNI-N as specified in MEF 16
• Link OAM (Operation, Administration and
  Management)
• Allows customer and service provider to monitor
  and diagnose the UNI connectivity via Link OAM
  (link level)
• Service OAM
• Allows customer and service provider to monitor
  and diagnose the UNI connectivity via Service OAM
  (end-to-end)
• Protection
• Capability to protect UNI against port failure
  via Link Aggregation protocol
• Enhanced UNI Attributes
• Such as bandwidth profile per egress UNI, Maximum
  Transfer Unit size, etc. as defined in MEF 10.,
  MEF 6.1
• L2CP Handling
• Governs the passing or filtering of Layer 2
  control protocols to the Ethernet Virtual
  Connections

Details of each mandatory and optional element
are to be found in the specification
38
MEF 21/24/25 Testing UNI Type 2
Work in Progress
MEF 11 User Network Interface (UNI) Requirements
and Framework
Abstract Test Suite for UNI Type 2 Part 4
Protection
Abstract Test Suite for UNI Type 2 Part 5
Enhanced UNI Attributes
MEF 20 UNI Type 2 Implementation Agreement
MEF 13 UNI Type 1 Implementation Agreement
Abstract Test Suite for UNI Type 2 Part 6 L2CP
Handling
MEF 19 Abstract Test Suite for UNI Type 1
MEF 21 Abstract Test Suite for UNI Type 2 Part 1
Link OAM
MEF 24 Abstract Test Suite for UNI Type 2 Part
2 E-LMI (Approved April 21st 2009)

• Further Test projects are in preparation
• MEF Certification will be decided in due course

MEF 25 Abstract Test Suite for UNI Type 2 Part 3
ServiceOAM
39
MEF 22 Mobile Backhaul Implementation Agreement

• Purpose of specification
• First phase
• EVCs spanning a single MEN (Metro Ethernet
  Network).
• Synchronization is either delivered outside of
  the Ethernet transport network or using a packet
  based method that is transparent to the MEN,
  e.g. treated as standard Service Frames
• GSM, WCDMA, CDMA, CDMA2000, and WiMAX 802.16e.
• Subsequent phases anticipated
• EVCs spanning arbitrary number of MENs.
• Other synchronization methods.
• Other mobile standards, such as LTE (Long Term
  Evolution).
• Synchronous Ethernet

40
MEF 23 Class of Service Implementation Agreement

• Purpose of specification
• 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 dont 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

41
MEF Work in Development
42
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

43
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 todays specifications. These
  benefits increase as the specifications complete
• MEF Timescales
• The MEF continues to exist during the foreseeable
  future to complete our mission

44
MEF Technical Committee Dashboard
Sept 2009
TS Technical Specification IA Implementation
Agreement
Notes MEF 6.1 replaced MEF 6. MEF 10.1 replaced
MEF 10, which replaced MEF 1 and MEF 5. MEF
10.1.1 is an amendment to MEF 10.1
45
Bandwidth Profiles
Service Area
MEF 6.1 Ethernet Services Definitions Phase 2
(TS)

• Defines new services work related to the
  definitions
• Service frame can be subjected to more than one
  Bandwidth Profile allowing, for example, limits
  on all traffic at the specific.

MEF 3 Circuit Emulation Service Requirements
(TS)
MEF 8 Emulation of PDH over MENs (IA)
MEF 10.1 Ethernet Services Attributes Phase 2 (TS)
MEF 22 Mobile Backhaul (IA)
MEF 23 Carrier Ethernet Class of Service (IA)
MEF 10.1.1 AmendmentAttribute Enhancements
MEF 10.2 Ethernet Services Document Alignment
Ethernet Services Amendment New Bandwidth Profile
Mobile Backhaul (IA) Phase 2
Carrier Ethernet Class of Service (IA) Phase 2

• The customer has a CIR/EIR per Class of Service
  and an overall rate limiter per EVC.
• During congestion flows will reside on different
  queues
• Allow more EIR per class without putting too
  much burst on the network.
• Traditionally high-class high bandwidth legacy
  traffic not dropped to match EVC profiles

Hierarchical Bandwidth profile aware network
Legacy Network
EVC Profile
EVC Profile
EVC.CoS
EVC.CoS
EVC.CoS
EVC.CoS
EVC.CoS
EVC.CoS
46
External Network to Network Interface (E-NNI)
Architecture Area
MEF 2 Protection Framework and Requirements (TS)

• MEF E-NNI Defined
• External Network Network Interface ("E-NNI") is
  defined as a reference point representing the
  boundary between two Operator Carrier Ethernet
  Networks that are operated as separate
  administrative domains.

MEF 4 Metro Ethernet Network Architecture
Framework Part 1 Generic Framework (TS)
MEF 11 - UNI Framework and Requirements (TS)
MEF 12 Metro Ethernet Network Architecture
Framework Part 2 Ethernet Services Layer (TS)
MEF 13 User Network Interface Type 1 (IA)
MEF 20 UNI Type 2 (IA)
External NNI (E-NNI) Phase 1 (TS)
Ethernet Service Constructs (TS)
MEF 12 Network Architecture Framework Update
NID Specification (TS)
E-NNI
Provider 1
Provider 2
EVC-1
UNI
UNI
UNI
UNI
IMPORTANT NOTE This information is preliminary
and is subject to change
47
E-NNI Constructs UTAS, VUNI, RUNI
Architecture Area
MEF 2 Protection Framework and Requirements (TS)

• Work in parallel with E-NNI defines requirements
  for UNI Tunnel Access Service (UTAS) which
  connects the Virtual UNI (VUNI) and Remote UNI
  (RUNI)
• Terminating Tunnels associate a VUNI and an RUNI
• VUNI is the Logical interface at endpoint of
  E-NNI side of Terminating Tunnel which Maps
  CEVC(s) to its Terminating Tunnel
• RUNI is a Logical interface at end point of UNI
  side of the Terminating Tunnel

MEF 4 Metro Ethernet Network Architecture
Framework Part 1 Generic Framework (TS)
MEF 11 - UNI Framework and Requirements (TS)
MEF 12 Metro Ethernet Network Architecture
Framework Part 2 Ethernet Services Layer (TS)
MEF 13 User Network Interface Type 1 (IA)
MEF 20 UNI Type 2 (IA)
External NNI (E-NNI) Phase 1 (TS)
Ethernet Service Constructs (TS)
MEF 12 Network Architecture Framework Update
NID Specification (TS)
UNI
EVC1
E-NNI
E-NNI
EVC1
Operator 3
Operator 2
Operator 1
UNI
Terminating Tunnel
EVC3
EVC3
UNI
UNI
EVC2
EVC2
48
E-NNI Constructs Putting it Together
Architecture Area
MEF 2 Protection Framework and Requirements (TS)

• 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

MEF 4 Metro Ethernet Network Architecture
Framework Part 1 Generic Framework (TS)
MEF 11 - UNI Framework and Requirements (TS)
MEF 12 Metro Ethernet Network Architecture
Framework Part 2 Ethernet Services Layer (TS)
MEF 13 User Network Interface Type 1 (IA)
MEF 20 UNI Type 2 (IA)
External NNI (E-NNI) Phase 1 (TS)
Ethernet Service Constructs (TS)
MEF 12 Network Architecture Framework Update
NID Specification (TS)
E-NNI 2
E-NNI 1
UNI 1
Transport Network Provider
Access Network Provider
UNI 2
Ethernet Service Provider
Terminating Tunnel
Terminating Tunnel
Subscriber
Subscriber
49
Ethernet Service Constructs
Architecture Area
MEF 2 Protection Framework and Requirements (TS)

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

MEF 4 Metro Ethernet Network Architecture
Framework Part 1 Generic Framework (TS)
MEF 11 - UNI Framework and Requirements (TS)
MEF 12 Metro Ethernet Network Architecture
Framework Part 2 Ethernet Services Layer (TS)
MEF 13 User Network Interface Type 1 (IA)
MEF 20 UNI Type 2 (IA)
External NNI (E-NNI) Phase 1 (TS)
Ethernet Service Constructs (TS)
MEF 12 Network Architecture Framework Update
NID Specification (TS)
ESN
TE Mouth
TE Stem
Tunnel Construct
IMPORTANT NOTE This information is preliminary
and is subject to change
50
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 Interface in NID towards UNI-C
Metro Ethernet NID Towards Metro Ethernet Edge
Interface
Metro Ethernet Towards NID Interface
Inter-NID Interface
Carrier
Carrier
Customer
Ethernet
Ethernet
Equipment
NID

1
NID

2
IMPORTANT NOTE This information is preliminary
and is subject to change
51
MEF 12 Network Architecture Framework

• Update to Network Architecture Part 2 includes
  new elements related to
• Network Interface Device
• Ethernet Services Constructs
• External Network Interface project

CEN X
UNI-C
UNI-N
UNI
Subscriber
Site B
UNI-N
UNI-C
CEN Y
E-NNI
E-NNI
E-NNI
UNI-N
UNI-C
Subscriber
Site C
UNIC-C Executes the process of the customer
side of the UNI
CEN Carrier Ethernet Network
UNIC-N Executes the process of the network side
of the UNI
52
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 Forums 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
53
Service OAM (SOAM) Performance Management

• Specifies an Implementation Agreement (IA) for
  Service Operations, Administration, and
  Maintenance (SOAM).
• Planned to consist of extensions to the
  Y.1731/IEEE802.1ag procedures and protocols to
  achieve the requirements of MEF Service OAM PM
  Phase I and extend the PM framework.
• Extensions are required to manage performance for
  multipoint EVCs since Y.1731 only covers
  Point-to-Point EVCs

Right Solution Components. NE conducts and
stores performance measurements. EMS-NMS
collects, processes to determine one or more
performance attributes for the EVC
EMS/NMS
This specification specifies network element (NE)
requirements to enable the following PM Solutions
Stored Measurements
NE B
NE A
Initiated Measurements
NE C
IMPORTANT NOTE This information is preliminary
and is subject to change
NE Network Element
54
Service OAM Fault Management

• Specifies how to utilize Q.1731 and IEEE 802.1ag
  protocols and procedures for fault management of
  Ethernet services.

UNI Single Hop
UNI is Multi-Hop
E-NNI
If the UNI is a single-hop, MEPs will detect the
UNI failure if their MAs include the UNI, or if
they are positioned on the Ethernet interface of
the UNI-C and UNI-N which realize the UNI
If the UNI is multi-hop, and a failure occurs at
an intermediate point, only those MEPs whose MA
spans the UNI will detect the UNI failure.
MEPs will detect the E-NNI failure if their MA
spans the E-NNI, or if they are positioned on the
Ethernet interface of the E-NNI-N which realizes
the E-NNI.
IMPORTANT NOTE This information is preliminary
and is subject to change
55
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

Observed TPL Statistics
Observed throughput Statistics
IMPORTANT NOTE This information is preliminary
and is subject to change
56
Abstract Test Suites

• UNI Type 2 Part 3 Service OAM
• Defines test procedures based on a combination of
  requirements for Service OAM described in the
  UNI Type 2 Implementation Agreement, ITU-T Y.1731
  and IEEE 802.1ag
• 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 Abstract Test Suite
• 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
57
Accelerating Worldwide Adoption of Carrier-class
Ethernet Networks and Services
www.MetroEthernetForum.org