1 MEF Technical Activities Paul Bottorff, Co-Chair MEF Technical Committee.

1

MEF Technical ActivitiesMEF Technical Activities

Paul Bottorff, Co-Chair MEF Paul Bottorff, Co-Chair MEF Technical CommitteeTechnical Committee

2

What is the MEFWhat is the MEF

• The Metro Ethernet Forum is a non-profit The Metro Ethernet Forum is a non-profit organization dedicated to accelerating the organization dedicated to accelerating the adoption of optical Ethernet as the technology of adoption of optical Ethernet as the technology of choice in metro networks worldwide. choice in metro networks worldwide.

• The Forum is comprised of leading service The Forum is comprised of leading service providers, major incumbent local exchange providers, major incumbent local exchange carriers, top network equipment vendors and carriers, top network equipment vendors and other prominent networking companies that other prominent networking companies that share an interest in metro Ethernet. It has 60 share an interest in metro Ethernet. It has 60 members as of February, 2002.members as of February, 2002.

3

MEF Key ObjectivesMEF Key Objectives

• Build consensus and unite Build consensus and unite service providers, equipment service providers, equipment vendors, end customers on optical Ethernetvendors, end customers on optical Ethernet

• Facilitate implementation Facilitate implementation of optical Ethernet standards to allow of optical Ethernet standards to allow delivery of delivery of Ethernet servicesEthernet services and make and make Ethernet-based metro Ethernet-based metro transport networks carrier-classtransport networks carrier-class

• Enhance worldwide awarenessEnhance worldwide awareness of the benefits of optical of the benefits of optical Ethernet services and Ethernet-based metro transport Ethernet services and Ethernet-based metro transport networksnetworks

• Enable Ethernet applications and services, Enable Ethernet applications and services, building on the building on the physical transportphysical transport specified by e.g. 10GEAspecified by e.g. 10GEA

4

MEF StructureMEF Structure

Awareness

Marketing Committee

Standards

Technical Committee

Board of Directors

Officers

Members

5

MEF: Diverse LeadershipMEF: Diverse LeadershipThe MEF Board of Directors is comprised of The MEF Board of Directors is comprised of representatives from:representatives from:– BellSouthBellSouth– SBCSBC– France TelecomFrance Telecom– Rockefeller Group Telecommunications ServicesRockefeller Group Telecommunications Services – Agilent TechnologiesAgilent Technologies– Procket NetworksProcket Networks– AtricaAtrica– Nortel Networks Nortel Networks – AlcatelAlcatel

For more information about the MEF leadership please For more information about the MEF leadership please visit http://www.MetroEthernetForum.org/visit http://www.MetroEthernetForum.org/

6

Marketing Committee Structure

Messaging Collateral

Sub-committee

Economic Analysis

Sub-committee

EventsSub-committee

Marketing Committee

• Marketing committee is divided into three areas

7

Technical Committee Structure

Architecture Sub-committee

Services Sub-committee

Management Sub-committee

Protocol & Transport

Sub-committee

All Members

Areas

Technical Committee

• Technical committee is divided into five specialization areas

TestMethods

Sub-committee

8

Approach to Technical Approach to Technical StandardsStandards

IEEEIEEE802802

IETFIETF

ITUITUOIFOIF

MPLSMPLSForumForum

10 GE10 GEAllianceAlliance

Etc.Etc.

Etc.Etc.

Etc.Etc.

Etc.Etc.

MEFMEF

Use existing Standards and only fill the Use existing Standards and only fill the technical gaps for Metro Ethernettechnical gaps for Metro Ethernet

9

Document TypesDocument Types

• Implementation AgreementsImplementation Agreements– Building consensus on existing standardsBuilding consensus on existing standards

• Test ProceduresTest Procedures– Promoting/Performing Interoperability testingPromoting/Performing Interoperability testing

• Position StatementsPosition Statements– Proposing work for existing standards bodiesProposing work for existing standards bodies

• Technical SpecificationsTechnical Specifications– Developing new standards within MEFDeveloping new standards within MEF

10

TC Work Is Divided By Specialization Area

Architecture Sub-committee

Services Sub-committee

Management Sub-committee

Protocol & Transport

Sub-committee

All Members

Areas

Technical Committee

TestMethods

Sub-committee

11

ArchitectureArchitecture

• Metro Ethernet Network (MEN) Reference ModelMetro Ethernet Network (MEN) Reference Model– User Network Interface (UNI) User Network Interface (UNI) – Network to Network Interfaces (NNIs) Network to Network Interfaces (NNIs)

• MEN FrameworkMEN Framework– defines the modeling conventions for the functional elements defines the modeling conventions for the functional elements

which compose a MEN which compose a MEN – Provides common terminology for all MEF technical documentsProvides common terminology for all MEF technical documents

• User Network Interface (UNI)User Network Interface (UNI)– The demark for customer or subscriber attachmentThe demark for customer or subscriber attachment

• Ethernet Interworking NNI (EI-NNI)Ethernet Interworking NNI (EI-NNI)– Interface between autonomous systemsInterface between autonomous systems

12

ServicesServices

• Ethernet Services Model Ethernet Services Model • Ethernet Definitions Ethernet Definitions

– Ethernet Line Services (ELINE)Ethernet Line Services (ELINE)– Ethernet LAN Services (ELAN)Ethernet LAN Services (ELAN)– Circuit Emulation Service (CES) Circuit Emulation Service (CES)

• Bandwidth Profiles ParametersBandwidth Profiles Parameters– Committed Information Rate (CIR)Committed Information Rate (CIR)– Peak Information Rate (PIR) Peak Information Rate (PIR)

13

Transport and ProtocolTransport and Protocol• Protection Protection

– Protection Framework describes a model and Protection Framework describes a model and framework to deliver network protection schemesframework to deliver network protection schemes

• EMF EMF – Ethernet Multiplexor provides a subset of the functions Ethernet Multiplexor provides a subset of the functions

under discussion at IEEE 802.1 Provider Bridges under discussion at IEEE 802.1 Provider Bridges

• EoSEoS– Agreements for transport of Ethernet over SonetAgreements for transport of Ethernet over Sonet

14

ManagementManagement• Element Management SystemElement Management System

– defines the requirements for the central systems which defines the requirements for the central systems which manage the network elements of a MENmanage the network elements of a MEN

• EMS/NMS Information Model EMS/NMS Information Model – defines a vendor independent data model for defines a vendor independent data model for

information exchanged between the service provider’s information exchanged between the service provider’s NMS and the MEN EMS NMS and the MEN EMS

• OAM ManagementOAM Management– defines end-to-end OAM for the service assurance defines end-to-end OAM for the service assurance

15

MEF Technical Committee Dash BoardMEF Technical Committee

Management Area

OAM&P

ArchitectureArea

MEN Architecture

Protocol & TransportArea

QOS

UNI

QOS Framework d2

UNI Framework d3

Protection

ProtectionFramework d3

Protection Requirements d3

MPLS Protection IA d1

EoS EoS IA d1

Services Area

EthernetServices

EthernetServices

Definitions d2

EthernetServices

Model d4

Process Ad-Hoc

LegendGray Color = Not Approved ProjectOrange Color = Approved ProjectBlue Color = Draft StatusGreen Color = Approved StandardRed Color = Sent to Ballot

MEN Architecture FW Part 1 d1MEN Architecture FW Part 2MEN Architecture FW part 3MEN Architecture FW part 4MEN Architecture FW part 5

EMS Mgmt

EMS Requirements d1

TM

Traffic PerformanceParameters d3

EMS-NMS Information Model d3

EMS-NMS IfCES

CES Requirements d2

UNI Requirements d2

NI-NNIEI-NNI

UNI PVC IA d1

TC Rules and Procedures

EMF

Ethernet Services OAM d4

MPLS NI-NNI D1EI-NNI TS d1

Test Area

Conformance &Performance

EMF TS d1

16

16 Approved Drafts16 Approved DraftsDoc # Draft# Title First Draft Current Draft Status Ballot% #Votes January

D00001 4 Ethernet Service Model Apr-02 Jan-03 Straw 81/19/- 16 Straw xD00002 3 A Framework For Metro Ethernet Protection Apr-02 Oct-02 Letter 74/26/- 27D00003 1 Implementing Metro Ethernet Protection using MPLS Mechanisms Jul-02 Jul-02 Straw 65/35/- 17D00004 3 Requirements for Metro Ethernet Protection Jan-02 Oct-02 Straw 77/23/- 22D00005 4 Ethernet Service OAM Apr-02 Jan-03 Draft xD00007 1 Metro Ethernet Architecture Framework- Part 1: Generic Framework Jul-02 Jul-02 DraftD00008 2 UNI Requirements Jul-02 Oct-02 Straw 68/32/0 19 Straw xD00009 3 UNI Framework Specification Apr-02 Jan-03 Draft xD00011 2 Ethernet Layer 2 Service Definitions Apr-02 Oct-03 Straw 70/29/- 17 Straw xD00012 3 EMS-NMS Information Model Apr-02 Oct-02 Draft Straw xD00013 2 CES Requirements Jul-02 Oct-03 Draft xD00014 1 EMS Requirements Jan-02 Jan-02 Straw 82/18/- 17 StrawD00015 3 Traffic Performance Parameters Apr-02 Oct-02 Straw Straw xD00016 2 QoS Framework Apr-02 Jul-02 DraftD00017 1 EOS Implementation Agreement Jul-02 Jul-02 DraftD00018 1 EI-NNI TS Oct-02 Oct-02 Draft xD00019 1 EMF TS Jan-03 Jan-03 Draft x

Approved interworking project xCES contributions to straw ballot x

17

Basic Metro Ethernet Model

• Ethernet Service provided by Metro Ethernet Network (MEN)

• Customer Equipment (CE) attaches to MEN at User-Network Interface (UNI) using 10, 100, 1000 Mbps Ethernet interface.

18

Ethernet ServicesLayer

(802.3 PHY, SDH/SONET,MPLS, OTN, ...)

Transport Layer (s)

(Ethernet)

• Ethernet Services layer (ETH)

• uses services from its Transport Layer(s)

• provides services to its Application Services Layer(s)

(VoIP, IP, MPLS, PDH, ...)

Application ServicesLayer (s)

MEN Layered Network Model

Domain

19

SubscriberMetro Ethernet

Network (MEN)Autonomy Y

UNI

EthernetInterworkingEI-NNI

Metro Ethernet Network (MEN)

Autonomy X

MEF External Reference Points

Metro Ethernet Network (MEN)

Autonomy X

NetworkInterworkingNI-NNI

Public Service Networks

Internet, FR, etc.

Service Interworking SI-NNI

TransportNetwork

IntercarrierNetwork

20

MEF External Reference Point

• User Network Interface (UNI)– Reference point between Metro Ethernet

Network (MEN) and directly/virtualized attached interfaces of customer equipment.

– Interfaces between MEN and customer equipment.

– Is the subscriber demark point

• Service Interworking NNI (SI-NNI)– Reference point between MEN and other public

service networks (IP).– Interfaces between MEN and other public

services networks (ex: ATM, FR, T1/T3, IP-Sec, etc).

21

• Ethernet Interworking NNI (EI-NNI)• Reference point between MENs in

different autonomys• Network Interworking NNI (NI-NNI)

– Reference point between MENs in same autonomy.

– Interface between MEN and other public transport networks (GE, SDH/SONET, ATM, RPR, etc).

MEF External Reference Point (Cont.)

22

Services DefinitionServices Definition

MetroMetroEthernetEthernetNetworkNetwork

CustomerCustomerEquipmentEquipment

(CE)(CE)

User NetworkUser NetworkInterfaceInterface

(UNI)(UNI)

Service ProviderService ProviderResponsibilityResponsibility

Service Model: Services described as seen by CE, UNI to UNIService Model: Services described as seen by CE, UNI to UNI

23

Ethernet Virtual Connection Ethernet Virtual Connection Types (EVC)Types (EVC)

Point-to-PointPoint-to-Point Multipoint-to-MultipointMultipoint-to-Multipoint

RootRoot

LeafLeaf

LeafLeaf

Point-to-MultipointPoint-to-Multipoint

24

Some Service FeaturesSome Service FeaturesBandwidth Profile:Bandwidth Profile: Defines the way in which less Defines the way in which less than the full physical bandwidth of UNI can utilized than the full physical bandwidth of UNI can utilized by the subscriber. Basis of the “pay for the by the subscriber. Basis of the “pay for the bandwidth that you need” capability of an Ethernet bandwidth that you need” capability of an Ethernet Service. Service.

Service Multiplexing:Service Multiplexing: Multiple EVCs accessible at a Multiple EVCs accessible at a single UNI. Reach multiple destinations across the single UNI. Reach multiple destinations across the MEN via a single UNI, e.g., a Gigabit Ethernet UNI.MEN via a single UNI, e.g., a Gigabit Ethernet UNI.

IWFIWF IWFIWFInterworking Function:Interworking Function: Non-Ethernet Non-Ethernet services via an Interworking Function services via an Interworking Function (IWF), e.g., TDM over Ethernet(IWF), e.g., TDM over Ethernet

25

Ethernet Line Service Ethernet Line Service (ELINE)(ELINE)

• ELINE service is Point-to-Point and may describe both ELINE service is Point-to-Point and may describe both Private Lines and Virtual Private LinesPrivate Lines and Virtual Private Lines

• May build a Frame Relay like serviceMay build a Frame Relay like service

ELINEELINE

26

ELINE Service MultiplexingELINE Service Multiplexing

• In this example a single site has multiple ELINE In this example a single site has multiple ELINE connections to other sites multiplexed over a single UNI.connections to other sites multiplexed over a single UNI.

27

Ethernet LAN Service Ethernet LAN Service (ELAN)(ELAN)

• Service is Multipoint-to-Multipoint fully Service is Multipoint-to-Multipoint fully connectedconnected

ELANELAN

28

MEF Protection MechanismMEF Protection Mechanism

Protection ModelProtection Model

Aggregated Line andAggregated Line andNode ProtectionNode Protection

End-to-End PathEnd-to-End PathProtectionProtection

TopologyTopology

TransportTransport

Application Protection Constraint PolicyApplication Protection Constraint Policy

Multiple levels of service resiliency enabled Multiple levels of service resiliency enabled by flexible protection mechanism by flexible protection mechanism

29

Aggregated Line and Node Aggregated Line and Node Protection Protection

IngressIngressNetworkNetworkElementElement

NetworkNetworkElementElement


EgressEgressNetworkNetworkElementElement

PrimaryPrimaryPathPath



DetourDetourPathPath

DetourDetourPathPath

30



End-to-End Path Protection End-to-End Path Protection

IngressIngressNetworkNetworkElementElement



EgressEgressNetworkNetworkElementElement

PrimaryPrimaryPathPath



SecondarySecondaryPathPath

31

End-to-end OAMEnd-to-end OAM

Metro Ethernet Network




ISP Router

Internet Access

ProviderEdge

ProviderEdge

Ethernet Virtual Connection (EVC)

Ethernet Access Network




CustomerEdge

CustomerEdge

UNIUNI LMILMI LMILMI

32

OAM ManagementOAM Management

• AvailabilityAvailability

• Status MonitoringStatus Monitoring

• ScalabilityScalability

• ExtensibilityExtensibility

• SecuritySecurity

• Tunnel and Transport IndependenceTunnel and Transport Independence

• Layer 3 IndependenceLayer 3 Independence

33

SummarySummary• MEF is working to fill the gaps between MEF is working to fill the gaps between

existing standards needed to standardize existing standards needed to standardize complete MEN systems.complete MEN systems.

• Technical work is focused onTechnical work is focused on– Customer Service SpecificationsCustomer Service Specifications– User Interface DefinitionUser Interface Definition– Network To Network Interface DefinitionsNetwork To Network Interface Definitions– Transport Network Features for Protection, QoS, Transport Network Features for Protection, QoS,

and EoSand EoS– End-to-end ManagementEnd-to-end Management– Network Element ManagementNetwork Element Management

1 MEF Technical Activities Paul Bottorff, Co-Chair MEF Technical Committee.

Documents

Transcript of 1 MEF Technical Activities Paul Bottorff, Co-Chair MEF Technical Committee.