An Introduction to The MEF Specifications

1
An Introduction to The MEF Specifications
the technical work in development

January 2007
2
The Technical Work of the MEF

• Technical Committee
• The Technical Committee currently focuses their
  work
• Services, Architecture, Architecture, Management,
  Test Measurement.
• Each have sub-teams focused on delivering
  technical specifications, implementation
  agreements, frameworks, agreements and
  interoperability content to support the adoption
  of Carrier Ethernet.
• The Technical Committee has active liaisons with
  other standards organizations.
• Active Participation in the Development of
  Carrier Ethernet
• The Development of Carrier Ethernet is driven
  solely by the active participation of the
  members. This participation is an opportunity to
  advnce member companies and contribution to next
  generation networking.
• Active recruitment to involve new Service
  Provider and equipment manufacturers in the work
  of the MEF

3
Introduction

• Purpose
• This presentation is a brief look at the
  specifications and their purpose prior to going
  to individual specification overviews
• Contents
• Connectivity between Carrier Ethernet and the
  specifications
• Specification timeline
• A summary of all the specifications
• A quick look at terminology and the two types of
  specifications
• A slide showing the technical dashboard of the
  MEF
• A look ahead at work in development
• 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

4
Specifications Timeline
MEF 16
MEF 4
MEF 7
MEF 12
ELMI
Architecture
EMS-NMS
Architecture
MEF 10.1
MEF 2
MEF 11
MEF 15
MEF 17
Protection
Management
Service AttributesPhase 2
UNI Framework
Service OAM
2006
2005
2004
2001-3
2007
MEF 3
MEF 10
MEF 13
MEF 18
UNI-IA
Circuit Emulation
Service Attributes Phase 1
Circuit Emulation Services Test Suite
MEF 14
MEF 19
Traffic Management Test Suite
UNI Type 1 Test Suite
MEF 6
MEF 8
Circuit Emulation
Service Definitions
MEF 9
Services Test Suite
The work of the MEF is driven by active
participation by a membership representing all
Carrier Ethernet industry stakeholder groups
MEF 10 .1 replaces and enhances MEF 10
Ethernet Services Definition Phase 1 and replaced
MEF 1 and MEF 5.
5
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 Metro Ethernet Services Definitions Phase I
  
• 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 10 .1 replaces and enhances MEF 10
Ethernet Services Definition Phase 1 and replaced
MEF 1 and MEF 5.
6
How the MEF Specifications Enable Carrier Ethernet
This chart shows how the MEF specifications
enable the attributes of Carrier Ethernet
indicating the responsible area within the MEF
Technical Committee
Carrier Ethernet Attributes





MEF Specs
MEF 2


Architecture Area


Service Area
MEF 3

Service Area


Architecture Area
MEF 4




MEF 6
Service Area

Service Area

Service Area
Management Area
MEF 7




MEF 8
Service Area




Test Measurement Area
MEF 9

Test Measurement Area


MEF 10.1
Service Area
Service Area


Service Area
MEF 11
Architecture Area




MEF 12
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

Contents
Carrier Ethernet
Technical
Future Work
Certification
Membership
Marketing
7
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
8
MEF Specifications Overview
MEF 6
Metro Ethernet Services Definitions Phase I
Purpose
Defines the Ethernet Services (EPL, EVPL,
E-Line, ELAN, 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

9
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
10
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
11
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
Audience
Equipment Manufacturers building devices that
will carry Carrier Ethernet Services. Useful for
Service Providers architecting their systems.
Technical Committee Architecture Area
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
Audience
Equipment Manufacturers building devices that
will carry CE Services. Useful for Service
Providers architecting their systems.
Technical Committee Architecture Area
12
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
Audience
Equipment Manufacturers building devices that are
designed to conform to MEF Specifications.
Service Providers who want to assure their end
customers that their services comply with MEF
Specifications.
Technical Committee Test and Measurement Area
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
13
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
Audience
Equipment Manufacturers building devices that
will carry CE Services. Useful for Service
Providers architecting their systems.
Technical Committee Test and Measurement Area
14
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
15
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
16
The Work of the MEF Continues
17
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

18
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

19
MEF Technical Committee Work Dashboard
Test and Measurement Area
Management Area
Architecture Area
Service Area
MEF 9 Abstract Test Suite for Ethernet Services
at the UNI (TS)
MEF 7 EMS - NMS Information Model (TS)
MEF 2 Protection Framework and Requirements (TS)
MEF 6 Ethernet Services Definitions (TS)
MEF 3 Circuit Emulation Service Requirements
(TS)
MEF 14 Abstract Test Suite for Traffic
Management Phase 1 (TS)
MEF 15 Requirements for Management of Metro
Ethernet Phase 1 Network Elements (TS)
MEF 4 Metro Ethernet Network Architecture
Framework Part 1 Generic Framework (TS)
MEF 18 Abstract Test Suite for CES over Ethernet
(TS)
MEF 16 Ethernet Local Management Interface
E-LMI (TS)
MEF 11 - UNI Framework and Requirements (TS)
MEF 8 Emulation of PDH over MENs (IA)
MEF 19 Abstract Test Suite for UNI Type 1 (TS)
MEF 17 Service OAM Requirements and Framework (TS)
MEF 12 Metro Ethernet Network Architecture
Framework Part 2 Ethernet Services Layer (TS)
MEF 10.1 Ethernet Services Attributes Phase 2 (TS)
EMS-NMS Information Model (TS) Phase 2
MEF 13 User Network Interface Type 1 (IA)
Ethernet Services Definitions Phase 2 (TS)
UNI Type 2 Test Suite (TS) Part 2 E-LMI
UNI Type 2 (IA)
Abstract Test Suite for E-NNI (TS)
Mobile Backhaul (IA)
Service OAM Performance Management (IA)
UNI Type 2 Test Suite (TS) Part 1 link OAM
External NNI (E-NNI) Phase 1 (TS)
Service OAM Fault Management (IA)
Classes of Service (IA)
Ethernet Service Constructs (TS)
NID Specification (TS)
January 2008
20
Preview of Upcoming MEF Specifications
Ethernet Service Definitions Phase II
MEF TBA
Purpose
Supersedes MEF 6 with additional work to define a
third service type Rooted Multipoint Ethernet
Virtual Connection (EVC). It also contains
updates to E-Line E-LAN Service Definitions
Audience
All, since it provides the fundamental required
to build devices and services that deliver
Carrier Ethernet.
Straw Ballot
Status
Technical Committee Service Area

• Upcoming specifications provide and ideal focal
  point for new members to make contributions

Contents
Carrier Ethernet
Technical
Future Work
Certification
Membership
Marketing
21
Preview of Upcoming MEF Specifications
External Network to Network Interface (E-NNI)
MEF TBA
Purpose
This document describes the functions and
protection mechanisms of the E-NNI The E-NNI is
the interface connecting two MENs where the MENs
belong to different administrative domains
Audience
Equipment Manufacturers building devices that
will carry CE Services. Useful for Service
Providers architecting their systems creating
interconnectivity with other Service Providers.
Status
Straw Ballot
Technical Committee Architecture Area

• Upcoming specifications provide and ideal focal
  point for new members to make contributions

22
Preview of Upcoming MEF Specifications
User Network Interface (UNI) Type
2 Implementation Agreement
MEF TBA
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
All interested parties (including Enterprise
users, whose ability to verify connectivity etc.,
is envisaged by the specification)
Status
Sent to Straw Ballot
Technical Committee Architecture Area

• Upcoming specifications provide and ideal focal
  point for new members to make contributions

23
Preview of Upcoming MEF Specifications
Purpose
Replacement for MEF 7 with support for E-LMI (MEF
16) and Phase II Service Definitions and
Attributes
Audience
Equipment Manufacturers building devices and
Service Providers architecting their systems.
Status
Approved Draft
Technical Committee Management Area

• Upcoming specifications provide and ideal focal
  point for new members to make contributions

24
Preview of Upcoming MEF Specifications
Abstract Test Suite for E-NNI
MEF TBA
Purpose
Tests the function, protection recovery
mechanisms of two interoperating MENs via their
External Network to Network Interfaces. Uses
similar constructs used in MEF 9 MEF 14
Audience
Equipment Manufacturers building devices that
will carry CE Services. Useful for Service
Providers architecting their systems.
Status
New Project
Technical Committee Test and Measurement Area

• Upcoming specifications provide and ideal focal
  point for new members to make contributions

25
Complementary Standards Activities

• Goals
• Reach consensus, bring MEF work to other bodies,
  re-use work of other bodies, work with other
  bodies, avoid duplication, keep in communications

Scalability
IEEE
Provider Bridge IEEE 802.1ad Provider Backbone
Bridge IEEE 802.1ah (MAC-in-MAC, and extended
label space)
ITU-T
ITU-T SG 15 has referenced the MEF service work
in their documents that describe EPL and EVPL.
IETF
Layer 2 VPNs
Service Management
IEEE
IEEE 802.1ag Fault Management IEEE 802.3ah link
OAM
ITU-T
ITU-T SG13 for Service OAM Working with ITU SG 4
on harmonizing their work with MEF 7 and adding
additional features of interest to the MEF such
as support of E-LMI
OIF
Customer signaling of Ethernet Services
Reliability
IETF
MPLS Fast Reroute, graceful restart
26
Ethernet Standards Summary
Ethernet OAM
Architecture/Control
Ethernet Services
Ethernet Interfaces
Standards Body

• 802.3ah EFM OAM
• 802.1ag CFM
• 802.1AB - Discovery
• 802.1ap VLAN MIB

• 802.3 MAC
• 802.3ar Congestion Management
• 802.1D/Q Bridges/VLAN
• 802.17 - RPR
• 802.1ad Provider Bridges
• .1ah Provider Backbone Bridges
• .1ak Multiple Registration Protocol
• .1aj Two Port MAC Relay
• .1AE/af MAC / Key Security
• .1aq Shortest Path Bridging

-

• 802.3 PHYs
• 802.3as - Frame Expansion

IEEE

• MEF 4 Generic Architecture
• MEF 2 Protection Req Framework
• MEF 11 UNI Req Framework
• MEF 12 - Layer Architecture

• MEF 10 Service Attributes
• MEF 3 Circuit Emulation
• MEF 6 Service Definition
• MEF 8 PDH Emulation
• MEF 9 Test Suites
• MEF 14 Test Suites
• Services Phase 2

MEF

• MEF 7 EMS-NMS Info Model
• MEF 15 NE Management Req
• OAM Req Framework
• OAM Protocol Phase 1
• Performance Monitoring

• MEF 13 - UNI Type 1
• MEF 16 ELMI
• E-NNI

• G.8010 Layer Architecture
• G.8021 Equipment model
• G.8010v2 Layer Architecture
• G.8021v2 Equipment model
• Y.17ethmpls - ETH-MPLS Interwork

• G.8011 Services Framewrk
• G.8011.1 EPL Service
• G.8011.2 EVPL Service
• G.asm Service Mgmt Arch
• G.smc Service Mgmt Chnl

ITU

• Y.1730 Ethernet OAM Req
• Y.1731 OAM Mechanisms
• G.8031 Protection
• Y.17ethqos QoS
• Y.ethperf - Performance

• G.8012 UNI/NNI
• G.8012v2 UNI/NNI

-
-
TMF

• TMF814 EMS to NMS Model

-
27
Two 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

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
28
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.
29
Accelerating Worldwide Adoption of Carrier-class
Ethernet Networks and Services
www.MetroEthernetForum.org