An introduction to the mef specifications the technical work in development
Download
1 / 29

TechnicalOverview - PowerPoint PPT Presentation


  • 283 Views
  • Updated On :

An Introduction to The MEF Specifications & the technical work in development January 2007 The Technical Work of the MEF Technical Committee The Technical Committee currently focuses their work: Services, Architecture, Architecture, Management, Test & Measurement.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'TechnicalOverview' - niveditha


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
An introduction to the mef specifications the technical work in development l.jpg

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

January 2007


The technical work of the mef l.jpg
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


Introduction l.jpg
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


Specifications timeline l.jpg
Specifications Timeline

MEF 4

MEF 7

MEF 12

MEF 16

Architecture

EMS-NMS

Architecture

ELMI

MEF 10.1

MEF 2

MEF 11

MEF 15

MEF 17

Protection

Management

Service AttributesPhase 2

UNI Framework

Service OAM

2001-3

2004

2005

2006

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


Slide5 l.jpg

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.


How the mef specifications enable carrier ethernet l.jpg
How the MEF Specifications Enable Carrier Ethernet

Quality of Service

Service Management

Reliability

Scalability

Standardized Services

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

MEF 3

Service Area

Service Area

MEF 4

Architecture Area

MEF 6

Service Area

Service Area

Service Area

MEF 7

Management Area

MEF 8

Service Area

MEF 9

Test & Measurement Area

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

Marketing

Certification

Membership


Mef specifications overview l.jpg
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


Mef specifications overview8 l.jpg
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


Mef specifications overview9 l.jpg
MEF Specifications Overview

MEF 7

EMS-NMS* Information Model*Element Management System–Network 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

MEF 15

Requirements for Management of Metro Ethernet Phase 1 Network Elements

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


Mef specifications overview10 l.jpg
MEF Specifications Overview

MEF 16

Ethernet Local Management Interface (E-LMI)

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

MEF 17

Service OAM Requirements & Framework – Phase 1

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


Mef specifications overview11 l.jpg
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


Mef specifications overview12 l.jpg
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

MEF 14

Abstract Test Suite for Traffic Management Phase 1

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


Mef specifications overview13 l.jpg
MEF Specifications Overview

MEF 18

Abstract Test Suite for CES

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

MEF 19

Abstract Test Suite for UNI Type 1

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


Mef specifications overview14 l.jpg
MEF Specifications Overview

MEF 2

Requirements and Framework for Ethernet Service Protection

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


Mef specifications overview15 l.jpg
MEF Specifications Overview

MEF 3

Circuit Emulation Service Definitions, Framework and Requirements in Metro Ethernet Networks

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

MEF 8

Implementation Agreement for the Emulation of PDH Circuits over Metro Ethernet Networks

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



Mef development work l.jpg
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: ……


Mef development work18 l.jpg
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


Slide19 l.jpg

MEF Technical Committee Work Dashboard

MEF Standards Process and Legend

TS Technical Specification

IA Implementation Agreement

NewProject

ApprovedDraft

StrawBallot

LetterBallot

ApprovedSpecification

comments

* MEF 10.1 replaced MEF 10. which replaced MEF 1 and MEF 5

Service Area

Architecture Area

Management Area

Test and Measurement Area

MEF 6 – Ethernet Services Definitions (TS)

MEF 2 – Protection Framework and Requirements (TS)

MEF 7 – EMS - NMS Information Model (TS)

MEF 9 – Abstract Test Suite for Ethernet Services at the UNI (TS)

MEF 3 – Circuit Emulation Service Requirements (TS)

MEF 4 – Metro Ethernet Network Architecture Framework Part 1: Generic Framework (TS)

MEF 15 – Requirements for Management of Metro Ethernet Phase 1 – Network Elements (TS)

MEF 14 – Abstract Test Suite for Traffic Management Phase 1 (TS)

MEF 8 Emulation of PDH over MENs (IA)

MEF 11 - UNI Framework and Requirements (TS)

MEF 16 – Ethernet Local Management Interface E-LMI (TS)

MEF 18 Abstract Test Suite for CES over Ethernet (TS)

MEF 10.1 Ethernet Services Attributes Phase 2 (TS)

MEF 12 – Metro Ethernet Network Architecture Framework Part 2: Ethernet Services Layer (TS)

MEF 17 Service OAM Requirements and Framework (TS)

MEF 19 Abstract Test Suite for UNI Type 1 (TS)

Ethernet Services Definitions Phase 2 (TS)

MEF 13 – User Network Interface Type 1 (IA)

EMS-NMS Information Model (TS) Phase 2

UNI Type 2 Test Suite (TS) Part 2 E-LMI

Mobile Backhaul (IA)

UNI Type 2 (IA)

Service OAM Performance Management (IA)

Abstract Test Suite for E-NNI (TS)

Classes of Service (IA)

External NNI (E-NNI) Phase 1 (TS)

Service OAM Fault Management (IA)

UNI Type 2 Test Suite (TS) Part 1 link OAM

Ethernet Service Constructs (TS)

NID Specification (TS)

January 2008


Preview of upcoming mef specifications l.jpg

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

Preview of Upcoming MEF Specifications

MEF [TBA]

Ethernet Service Definitions Phase II

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.

Status

Straw Ballot

Technical Committee Service Area

Contents

Carrier Ethernet

Technical

Future Work

Marketing

Certification

Membership


Preview of upcoming mef specifications21 l.jpg

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

Preview of Upcoming MEF Specifications

MEF [TBA]

External Network to Network Interface (E-NNI)

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


Preview of upcoming mef specifications22 l.jpg

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

Preview of Upcoming MEF Specifications

MEF [TBA]

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

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


Preview of upcoming mef specifications23 l.jpg

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

Preview of Upcoming MEF Specifications

MEF [TBA]

EMS-NMS* Information Model Phase II

*Element Management System–Network Management System

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


Preview of upcoming mef specifications24 l.jpg

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

Preview of Upcoming MEF Specifications

MEF [TBA]

Abstract Test Suite for E-NNI

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


Complementary standards activities l.jpg
Complementary Standards Activities new members to make contributions

  • 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


Ethernet standards summary l.jpg
Ethernet Standards Summary new members to make contributions

Standards Body

Ethernet Services

Architecture/Control

Ethernet OAM

Ethernet Interfaces

IEEE

-

  • 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.3ah – EFM OAM

  • 802.1ag – CFM

  • 802.1AB - Discovery

  • 802.1ap – VLAN MIB

  • 802.3 – PHYs

  • 802.3as - Frame Expansion

MEF

  • 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 4 – Generic Architecture

  • MEF 2 – Protection Req & Framework

  • MEF 11 – UNI Req & Framework

  • MEF 12 - Layer Architecture

  • 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

ITU

  • G.8011 – Services Framewrk

  • G.8011.1 – EPL Service

  • G.8011.2 – EVPL Service

  • G.asm – Service Mgmt Arch

  • G.smc – Service Mgmt Chnl

  • G.8010 – Layer Architecture

  • G.8021 – Equipment model

  • G.8010v2 – Layer Architecture

  • G.8021v2 – Equipment model

  • Y.17ethmpls - ETH-MPLS Interwork

  • 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

-


Two types of specifications l.jpg
Two Types of Specifications new members to make contributions

  • 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


Terminology l.jpg
Terminology new members to make contributions

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

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


Accelerating worldwide adoption of carrier class ethernet networks and services l.jpg

Accelerating Worldwide Adoption of new members to make contributions Carrier-class Ethernet Networks and Services

www.MetroEthernetForum.org


ad