Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "1 MEF Technical Activities Paul Bottorff, Co-Chair MEF Technical Committee."— Presentation transcript:

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

2 2 What is the MEF The Metro Ethernet Forum is a non-profit organization dedicated to accelerating the adoption of optical Ethernet as the technology of choice in metro networks worldwide.The Metro Ethernet Forum is a non-profit organization dedicated to accelerating the adoption of optical Ethernet as the technology of choice in metro networks worldwide. The Forum is comprised of leading service providers, major incumbent local exchange carriers, top network equipment vendors and other prominent networking companies that share an interest in metro Ethernet. It has 60 members as of February, 2002.The Forum is comprised of leading service providers, major incumbent local exchange carriers, top network equipment vendors and other prominent networking companies that share an interest in metro Ethernet. It has 60 members as of February, 2002.

3 3 MEF Key Objectives Build consensus and unite service providers, equipment vendors, end customers on optical EthernetBuild consensus and unite service providers, equipment vendors, end customers on optical Ethernet Facilitate implementation of optical Ethernet standards to allow delivery of Ethernet services and make Ethernet-based metro transport networks carrier-classFacilitate implementation of optical Ethernet standards to allow delivery of Ethernet services and make Ethernet-based metro transport networks carrier-class Enhance worldwide awareness of the benefits of optical Ethernet services and Ethernet-based metro transport networksEnhance worldwide awareness of the benefits of optical Ethernet services and Ethernet-based metro transport networks Enable Ethernet applications and services, building on the physical transport specified by e.g. 10GEAEnable Ethernet applications and services, building on the physical transport specified by e.g. 10GEA

4 4 MEF Structure

5 5 MEF: Diverse Leadership The MEF Board of Directors is comprised of representatives from: –BellSouth –SBC –France Telecom –Rockefeller Group Telecommunications Services –Agilent Technologies –Procket Networks –Atrica –Nortel Networks –Alcatel For more information about the MEF leadership please visit

6 6 Marketing Committee Structure Messaging Collateral Sub-committee Economic Analysis Sub-committee Events Sub-committee Marketing Committee Marketing committee is divided into three areas

7 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 Test Methods Sub-committee

8 8 Approach to Technical Standards IEEE 802 IETF ITU OIF MPLS Forum 10 GE Alliance Etc. Etc. Etc. Etc. MEF Use existing Standards and only fill the technical gaps for Metro Ethernet

9 9 Document Types Implementation AgreementsImplementation Agreements –Building consensus on existing standards Test ProceduresTest Procedures –Promoting/Performing Interoperability testing Position StatementsPosition Statements –Proposing work for existing standards bodies Technical SpecificationsTechnical Specifications –Developing new standards within MEF

10 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 Test Methods Sub-committee

11 11 Architecture Metro Ethernet Network (MEN) Reference ModelMetro Ethernet Network (MEN) Reference Model –User Network Interface (UNI) –Network to Network Interfaces (NNIs) MEN FrameworkMEN Framework –defines the modeling conventions for the functional elements which compose a MEN –Provides common terminology for all MEF technical documents User Network Interface (UNI)User Network Interface (UNI) –The demark for customer or subscriber attachment Ethernet Interworking NNI (EI-NNI)Ethernet Interworking NNI (EI-NNI) –Interface between autonomous systems

12 12 Services Ethernet Services ModelEthernet Services Model Ethernet DefinitionsEthernet Definitions –Ethernet Line Services (ELINE) –Ethernet LAN Services (ELAN) –Circuit Emulation Service (CES) Bandwidth Profiles ParametersBandwidth Profiles Parameters –Committed Information Rate (CIR) –Peak Information Rate (PIR)

13 13 Transport and Protocol ProtectionProtection –Protection Framework describes a model and framework to deliver network protection schemes EMFEMF –Ethernet Multiplexor provides a subset of the functions under discussion at IEEE Provider Bridges EoSEoS –Agreements for transport of Ethernet over Sonet

14 14 Management Element Management SystemElement Management System –defines the requirements for the central systems which manage the network elements of a MEN EMS/NMS Information ModelEMS/NMS Information Model –defines a vendor independent data model for information exchanged between the service providers NMS and the MEN EMS OAM ManagementOAM Management –defines end-to-end OAM for the service assurance

15 15 MEF Technical Committee Dash Board MEF Technical Committee Management Area OAM&P Architecture Area MEN Architecture Protocol & Transport Area QOS UNI QOS Framework d2 UNI Framework d3 Protection Framework d3 Protection Requirements d3 MPLS Protection IA d1 EoS EoS IA d1 Services Area Ethernet Services Ethernet Services Definitions d2 Ethernet Services Model d4 Process Ad-Hoc Legend Gray Color = Not Approved Project Orange Color = Approved Project Blue Color = Draft Status Green Color = Approved Standard Red Color = Sent to Ballot MEN Architecture FW Part 1 d1 MEN Architecture FW Part 2 MEN Architecture FW part 3 MEN Architecture FW part 4 MEN Architecture FW part 5 EMS Mgmt EMS Requirements d1 TM Traffic Performance Parameters d3 EMS-NMS Information Model d3 EMS-NMS If CES CES Requirements d2 UNI Requirements d2 NI-NNI EI-NNI UNI PVC IA d1 TC Rules and Procedures EMF Ethernet Services OAM d4 MPLS NI-NNI D1 EI-NNI TS d1 Test Area Conformance & Performance EMF TS d1

16 16 16 Approved Drafts

17 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 18 Ethernet Services Layer (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 Services Layer (s) MEN Layered Network Model Domain

19 19 Subscriber Metro Ethernet Network (MEN) Autonomy Y UNI Ethernet Interworking EI-NNI Metro Ethernet Network (MEN) Autonomy X MEF External Reference Points Metro Ethernet Network (MEN) Autonomy X Network Interworking NI-NNI Public Service Networks Internet, FR, etc. Service Interworking SI-NNI Transport Network Intercarrier Network

20 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 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 22 Services Definition Metro Ethernet Network Customer Equipment (CE) User Network Interface (UNI) Service Provider Responsibility Service Model: Services described as seen by CE, UNI to UNI

23 23 Ethernet Virtual Connection Types (EVC) Point-to-PointMultipoint-to-Multipoint Root Leaf Leaf Point-to-Multipoint

24 24 Some Service Features Bandwidth Profile: Defines the way in which less than the full physical bandwidth of UNI can utilized by the subscriber. Basis of the pay for the bandwidth that you need capability of an Ethernet Service. Service Multiplexing: Multiple EVCs accessible at a single UNI. Reach multiple destinations across the MEN via a single UNI, e.g., a Gigabit Ethernet UNI. IWF IWF Interworking Function: Non-Ethernet services via an Interworking Function (IWF), e.g., TDM over Ethernet

25 25 Ethernet Line Service (ELINE) ELINE service is Point-to-Point and may describe both Private Lines and Virtual Private LinesELINE service is Point-to-Point and may describe both Private Lines and Virtual Private Lines May build a Frame Relay like serviceMay build a Frame Relay like service ELINE

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

27 27 Ethernet LAN Service (ELAN) Service is Multipoint-to-Multipoint fully connectedService is Multipoint-to-Multipoint fully connected ELAN

28 28 MEF Protection Mechanism Protection Model Aggregated Line and Node Protection End-to-End Path Protection Topology Transport Application Protection Constraint Policy Multiple levels of service resiliency enabled by flexible protection mechanism

29 29 Aggregated Line and Node Protection Ingress Network Element Network Element Egress Network Element Primary Path Network Element Detour Path

30 30 Network Element End-to-End Path Protection Ingress Network Element Network Element Egress Network Element Primary Path Network Element Secondary Path

31 31 End-to-end OAM Metro Ethernet Network Metro Ethernet Network Metro Ethernet Network Metro Ethernet Network ISP Router Internet Access Provider Edge Provider Edge Ethernet Virtual Connection (EVC) Ethernet Access Network Ethernet Access Network Ethernet Access Network Ethernet Access Network Customer Edge Customer Edge UNI LMI LMI

32 32 OAM Management AvailabilityAvailability Status MonitoringStatus Monitoring ScalabilityScalability ExtensibilityExtensibility SecuritySecurity Tunnel and Transport IndependenceTunnel and Transport Independence Layer 3 IndependenceLayer 3 Independence

33 33 Summary MEF is working to fill the gaps between existing standards needed to standardize complete MEN systems.MEF is working to fill the gaps between existing standards needed to standardize complete MEN systems. Technical work is focused onTechnical work is focused on – Customer Service Specifications – User Interface Definition – Network To Network Interface Definitions – Transport Network Features for Protection, QoS, and EoS – End-to-end Management – Network Element Management


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

Similar presentations


Ads by Google