Presentation on theme: "MEF Technical Activities"— Presentation transcript:
1 MEF Technical Activities Paul Bottorff, Co-Chair MEF Technical Committee
2 What is the MEFThe 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.
3 MEF Key ObjectivesBuild consensus and unite service providers, equipment vendors, end customers on optical EthernetFacilitate implementation of optical Ethernet standards to allow delivery of Ethernet services and make Ethernet-based metro transport networks carrier-classEnhance worldwide awareness of the benefits of optical Ethernet services and Ethernet-based metro transport networksEnable Ethernet applications and services, building on the physical transport specified by e.g. 10GEA
5 MEF: Diverse Leadership The MEF Board of Directors is comprised of representatives from:BellSouthSBCFrance TelecomRockefeller Group Telecommunications ServicesAgilent TechnologiesProcket NetworksAtricaNortel NetworksAlcatelFor more information about the MEF leadership please visit
6 Marketing Committee Structure Messaging CollateralSub-committeeEventsSub-committeeEconomic AnalysisSub-committeeMarketing committee is divided into three areas
7 Technical Committee Structure All MembersAreasArchitecture Sub-committeeServicesSub-committeeProtocol &TransportSub-committeeManagement Sub-committeeTestMethodsSub-committeeTechnical committee is divided into five specialization areas
8 Approach to Technical Standards Use existing Standards and only fill the technical gaps for Metro EthernetIEEE 802OIFITUIETFMPLS ForumMEFEtc.Etc.10 GE AllianceEtc.Etc.
9 Document Types Implementation Agreements Test Procedures Building consensus on existing standardsTest ProceduresPromoting/Performing Interoperability testingPosition StatementsProposing work for existing standards bodiesTechnical SpecificationsDeveloping new standards within MEF
10 TC Work Is Divided By Specialization Area Technical CommitteeAll MembersAreasArchitecture Sub-committeeServicesSub-committeeProtocol &TransportSub-committeeManagement Sub-committeeTestMethodsSub-committee
11 Architecture Metro Ethernet Network (MEN) Reference Model User Network Interface (UNI)Network to Network Interfaces (NNIs)MEN Frameworkdefines the modeling conventions for the functional elements which compose a MENProvides common terminology for all MEF technical documentsThe demark for customer or subscriber attachmentEthernet Interworking NNI (EI-NNI)Interface between autonomous systems
12 Services Ethernet Services Model Ethernet Definitions Ethernet Line Services (ELINE)Ethernet LAN Services (ELAN)Circuit Emulation Service (CES)Bandwidth Profiles ParametersCommitted Information Rate (CIR)Peak Information Rate (PIR)
13 Transport and Protocol ProtectionProtection Framework describes a model and framework to deliver network protection schemesEMFEthernet Multiplexor provides a subset of the functions under discussion at IEEE Provider BridgesEoSAgreements for transport of Ethernet over Sonet
14 Management Element Management System EMS/NMS Information Model defines the requirements for the central systems which manage the network elements of a MENEMS/NMS Information Modeldefines a vendor independent data model for information exchanged between the service provider’s NMS and the MEN EMSOAM Managementdefines end-to-end OAM for the service assurance
15 TC Rules and Procedures Protection Requirements d3 MEF Technical Committee Dash BoardMEF Technical CommitteeConformance &PerformanceTestAreaProcess Ad-HocTC Rules and ProceduresManagementAreaArchitectureAreaProtocol & TransportAreaServicesAreaMEN ArchitectureQOSQOS Framework d2OAM&PMEN Architecture FW Part 1 d1MEN Architecture FW Part 2MEN Architecture FW part 3MEN Architecture FW part 4MEN Architecture FW part 5EthernetServicesModel d4EthernetServicesProtectionEthernet ServicesOAM d4Protection Requirements d3EthernetServicesDefinitions d2ProtectionFramework d3TMEMS MgmtUNIUNI Requirements d2MPLS Protection IA d1Traffic PerformanceParameters d3EMS Requirements d1EoSUNI Framework d3EoS IA d1CESUNI PVC IA d1EMS-NMS IfNI-NNICES Requirements d2EI-NNIInformation Model d3EMS-NMSMPLS NI-NNI D1EI-NNI TS d1LegendEMFGray Color = Not Approved ProjectOrange Color = Approved ProjectBlue Color = Draft StatusGreen Color = Approved StandardRed Color = Sent to BallotEMF TS d1
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 MEN Layered Network Model Ethernet Services layer (ETH)uses services from its Transport Layer(s)provides services to its Application Services Layer(s)Application ServicesLayer (s)(VoIP, IP, MPLS, PDH, ...)Ethernet ServicesLayer(Ethernet)TransportLayer (s)Domain(802.3 PHY, SDH/SONET,MPLS, OTN, ...)
19 MEF External Reference Points Public ServiceNetworksInternet, FR, etc.UNIService Interworking SI-NNIMetro EthernetNetwork (MEN)Autonomy XMetro EthernetNetwork (MEN)Autonomy YSubscriberIntercarrierNetworkEthernetInterworkingEI-NNINetworkInterworkingNI-NNITransportNetworkMetro EthernetNetwork (MEN)Autonomy X
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 pointService 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 MEF External Reference Point (Cont.) Ethernet Interworking NNI (EI-NNI)Reference point between MENs in different autonomysNetwork 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).
22 Services DefinitionCustomer Equipment(CE)User Network Interface (UNI)Metro Ethernet NetworkService Provider ResponsibilityService Model: Services described as seen by CE, UNI to UNI
24 Some Service FeaturesBandwidth 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.Interworking Function: Non-Ethernet services via an Interworking Function (IWF), e.g., TDM over EthernetIWFIWF
25 Ethernet Line Service (ELINE) ELINE service is Point-to-Point and may describe both Private Lines and Virtual Private LinesMay build a Frame Relay like service
26 ELINE Service Multiplexing In this example a single site has multiple ELINE connections to other sites multiplexed over a single UNI.
27 Ethernet LAN Service (ELAN) Service is Multipoint-to-Multipoint fully connected
28 Protection ModelMultiple levels of service resiliency enabled by flexible protection mechanismApplication Protection Constraint PolicyMEF Protection MechanismEnd-to-End Path ProtectionAggregated Line and Node ProtectionTopologyTransport
29 Aggregated Line and Node Protection Detour PathNetwork ElementIngress Network ElementNetwork ElementNetwork ElementEgress Network ElementPrimary PathNetwork ElementDetour Path
32 OAM Management Availability Status Monitoring Scalability ExtensibilitySecurityTunnel and Transport IndependenceLayer 3 Independence
33 SummaryMEF is working to fill the gaps between existing standards needed to standardize complete MEN systems.Technical work is focused onCustomer Service SpecificationsUser Interface DefinitionNetwork To Network Interface DefinitionsTransport Network Features for Protection, QoS, and EoSEnd-to-end ManagementNetwork Element Management