1. Is there a single presentation overview that summarizes the work of the MEF?

Yes. The work of the Metro Ethernet Forum is summarized in a detailed PowerPoint presentation available from the home page of MEF web site. Click here to download (3.5MB, July 2006)

The presentation covers

• Metro Ethernet Forum
• Carrier Ethernet and the attributes that distinguish it from Ethernet LANs
• The Technical Work of the MEF
  • An Introduction to the MEF Specifications
  • Current Status of the MEF Specifications
  • Future work and MEF Specifications in Preparation
  • Complementary Standards Activities
• The Marketing Work of the MEF
• MEF Certification Program
• MEF Membership

2. What is the Metro Ethernet Forum (MEF), its Mission and objectives?

The Metro Ethernet Forum is a non-profit organization chartered with the mission of accelerating Worldwide Adoption of Carrier class Ethernet Networks and Services. The Forum is comprised of leading service providers, major incumbent local exchange carriers, top network equipment vendors, test equipment vendors and other prominent networking companies that share an interest in metro Ethernet. In 2003, the MEF bylaws were amended to include membership by large Enterprise organizations specifically to address the growing interest by Business Enterprises. The involvement of the Enterprise is seen to provide valuable customer and technical requirements to further guide the activities of the MEF.

The MEF has over 80 members as of July 2006.

The Metro Ethernet Forum’s objectives

1. Build consensus and unite service providers, equipment vendors and end-customers on Ethernet service definition, technical specifications and interoperability.
2. Facilitate implementation of existing and new standards, Ethernet service definition, test procedures and technical specifications of the MEF to allow delivery of Ethernet services and make Ethernet-based metro networks carrier-class.
3. Enhance worldwide awareness of the benefits of Ethernet services and Ethernet-based metro transport networks.

3. What are the MEF priorities and Scope of Work?

The primary priorities of the MEF are to define:

1. Ethernet Services for metro transport networks. Ethernet services defined by the MEF are transport agnostic. The Metro Ethernet services can be communicated using two umbrella service types "Ethernet Line Services" (E-Line Services - point-to-point services) and Ethernet LAN Services" (E-LAN Services - multipoint-to-multipoint services). As part of the E-Line Service and E-LAN Service definitions, the MEF has defined the service attributes and parameters recommended for successful implementation of these services. This means that for each service based on these Service definitions, there are associated service attributes that have parameters, which must be set accordingly, so as to meet the customer service expectations. Typical service attributes include performance, bandwidth, speed, mode and class of service. Within each of these attributes parameters are recommended that provide interoperability between metro Ethernet Service Providers and vendors who implement the services.
2. Carrier-class Ethernet-based metro transport technologies. This will be done by specifying architecture, protocols and management for all metro transport networks, and supporting such Ethernet Services

The secondary priorities of the MEF are to define:

1. Work to be done by other organizations on other transport technologies
2. Non-Ethernet interfaces, if not defined by other organizations.

4. Ethernet has always been thought of as a LAN technology. Why is it now suitable for the metro area?

Ethernet is the logical choice for data transmission as it is by far the most widely deployed and mature data transport technology. There have also been technical advances, including increases in the speed and distance of Ethernet, supporting the migration of Ethernet into the metro area.

Other advantages driving the deployment of Ethernet technology into metro area networks include:

1. Ethernet has recognized strength as a service technology that brings lower cost, simplicity, better service granularity and rapid provisioning to customers.
2. There are continued ease-of-use advantages and price/performance improvements which are making Ethernet an important switching and transport technology in metro networks for data traffic in general, and IP traffic in particular.
3. End customers have broad expertise and comfort with Ethernet. They also have access to a wide range of low cost, high performance Ethernet products. Thus end customers have a dramatically reduced Total Cost of Ownership with Ethernet- based services.

Metro Ethernet has thus moved beyond its LAN origins to become a full-duplex, switched technology capable of meeting the long-range transport, bandwidth, geographical and capacity requirements of metro networking.

The result is a compelling combination of speed, scalability, operational simplicity, and economics that is driving Ethernet into metro networks.

5. Can you point to examples of carriers that have implemented metro Ethernet services?

Every MEF Service Provider member is at least in trials for metro Ethernet type services and most have implemented region specific service networks. A few examples include Verizon deployment in Las Vegas, NV (Mar. 2003), KT (Formerly known as Korea Telecom), Rockefeller Group Telecommunication Services in New York.

Case Studies, and examples are available from the MEF home page.

And although Metro Ethernet has not obtained mass market implementations yet, it has been forecasted by all major industry analysts groups to be the fastest growing tech market segment in the next several years. According to Infonetics Research, worldwide metro Ethernet equipment revenue hit $2.9 billion in 2003, and is projected to grow over 150% to $7.5 billion by 2007, a CAGR of 27%. Service Revenues are projected to grow to $22bn by 2008

6. What is the benefit of participating in the MEF?

Service providers rely on standards to deploy solutions that are scalable, reliable, interoperable and globally manageable. The MEF is filling a void not currently addressed by existing standards bodies by creating implementation agreements that address these objectives for metro Ethernet technologies and services.

Given the large community of service providers and network equipment vendors supporting this initiative, the MEF is leading the way toward standards-based solutions that integrate service provider requirements with solid technical recommendations. The work that the Metro Ethernet Forum has done to define and drive standardized terminology has been crucial to describing metro Ethernet service offerings in a way that customers can easily understand. The model builds on the success of the earlier generation Frame Relay and ATM Forums.

Carriers benefit by driving the MEF definition of requirements and also by participating in the development of business tools that are important to their success in the Ethernet services market.

The MEF equipment vendor members benefit from a process that includes a broad community of experts but also, more importantly, the end users of the technology.

The MEFs newest category of member, the Business Enterprise customer, can benefit by articulating their needs to vendors and providers which will strive to ensure that solutions and technologies are developed to meet end customer requirements.

7. What are some of the challenges facing the MEF?

Challenges include:

• Educating end-customers on the advantages and business case associated with Ethernet services and how to evolve Service Providers current legacy networks to metro Ethernet
• Educating the Service Provider on the application and business case (profitability) for Ethernet as a carrier class transport technology.
• Evangelizing metro Ethernet services and technologies to a broader market, including Europe and Asia. Maintaining the momentum the Organization is currently experiencing as Service Providers and equipment vendors align to move the metro Ethernet market forward.

8. What are the planned deliverables of the MEF?

Deliverables include the following:

• Marketing evangelism and collateral, including whitepapers, customer success stories, live interop demos, business case studies/whitepapers, are part of MEF deliverables.
• Implementation Agreements are MEF technical documents that specify implementations agreed to by MEF members that use existing standards.
• Test Procedures are MEF technical documents that specify testing methodologies and/or processes for interoperability testing purposes.
• Positioning Statements are MEF technical written requests to other standards bodies (IETF, IEEE, ITU, etc.) that propose additional technical work in those standards bodies.
• Technical Specifications are MEF technical documents that define new standards, where required, within the MEF.

9. Is the MEF a standards definition body?

The goal of the MEF is to create implementation agreements that leverage existing standards rather than creating new standards. The MEF is a combination of a technical and marketing forum to promote the adoption of metro Ethernet. This is a key differentiator from common standard bodies such as the IETF and IEEE. To this point, where necessary, the MEF will:

1. Make recommendations to existing standards bodies, e.g., the IETF or IEEE.
2. As a last resort, create specifications that are not being developed by (or fall within the scope of) other standards bodies.

10. What services are being defined by the MEF?

The MEF is taking a phased approach to leading the industry in defining and standardizing on Metro Ethernet services terminology and associated definitions. As of April 2005, the MEF has defined two service types:

• Ethernet Line Service Type (E-Line, point-to-point)
• Ethernet LAN Service Type (E-LAN, multipoint-to-multipoint)

• "Ethernet Private Line" (the Ethernet analogy to a dedicated TDM private line such as T1 or T3)
• "Ethernet Virtual Private Line" (the Ethernet analogy to a service using a shared network infrastructure similar to a Frame Relay).

Similar service instances can be created using the E-LAN Service.

11. Will these services support different Service Level Agreements?

Yes, the service definitions that have been agreed upon within the MEF - E-Line Services and E-LAN Services - provide specific attributes and parameters for any vendor to create their own SLA services offering.

One of the keys to the success of Ethernet in metro networks is the ability for service providers to provide differing grades of Ethernet service with the ability to derive revenue from associated service level agreements (SLAs).

A service level agreement ( SLA) is a commercial agreement binding both parties to a defined service level specification (SLS).

Because service providers have more experience with providing SLAs for existing technologies, like Frame Relay, than they do with Ethernet networks, it is a goal of the MEF to create common SLS definitions for service providers wanting to sell SLA-based Ethernet services.

In addition, it is a goal of the MEF to offer support ranging from guidelines for standard contracts, help with technologies that facilitate network uptime, and other aspects of selling SLA- based services.

12. What activities is the MEF doing outside of the U.S. to encourage adoption of metro Ethernet?

In 2003, the MEF began an outreach campaign in the European market and conducted a press and analyst tour and launch at the beginning of the year. To date, the MEF has developed many European members such as France Telecom, British Telecom, Colt, TeliaSonera. Quarterly meetings are also held in Europe with the latest being held in April 2006 in London. The second Carrier Ethernet World Congress is in Madrid in September 2006

The MEF has also begun an outreach campaign to the Asian market, where the momentum behind Carrier Ethernet networks is moving at a fast pace.

The MEF’s annual Service Provider of the Year awards are held in US, Europe and Asia

13. What are the applications driving the adoption of metro Ethernet?

Around the world, many of the applications driving metro Ethernet networks vary, but come to the delivery of service.

• In Korea: Gaming parlors, which require bandwidth-hungry real-time response, are fueling the demand.
• In Japan: Office interconnect (E-LAN service) between large multi-site corporations is the focus.
• In China/India: Residential services - voice/video/data on a single infrastructure. (High building density)
• EU/US: IT outsourcing/server consolidation (Both apps and data). Business continuity/disaster recovery/real-time off-site data backup

14. What is the role of the MEF marketing committee?

The MEF is both a marketing vehicle and a technical vehicle to realize the broader mission of accelerating worldwide adoption of carrier class Ethernet networks and services.

The specific charter of the MEF marketing committee is to enhance worldwide awareness of the benefits of Ethernet services and Ethernet-based transport networks.

This is being accomplished through deliverables that include:

• MEF participation in industry trade show and seminar events,
• The development of white papers, presentations and other collateral
• A proactive and global public relations program
• Live interoperability demonstrations
• Business case studies
• Customer success stories

15. What are the current areas of technical definition and development within the MEF?

There are four technical sub-committees currently at work within the MEF. These sub-committees include:

• Management - Mandated to develop Metro Ethernet operations, administration and maintenance (OA&M) requirements, models and definitions. This area is focused on defining and ensuring that network management is effective and interoperable across Metro Ethernet platforms. This includes normal network implementations that include multi-vendor solutions and integration into legacy network architectures. Work areas that have progressed substantially include Element Management Systems, Network Management and End-to-End OAM. As Metro Ethernet price per ports have substantially driven down the Capex cost, the simplified nature of managing Ethernet networks will also drive down Opex cost.
• Architecture Mandated to develop an architectural reference model and set of common linguistic tools for the technical teams. This team defines the layered MEN architecture including the multiple base transport layers, the single Ethernet Services layer and the above application layers that ride on top of the Ethernet Services. Each layer has been further decomposed into the Adaptation, Connection and Termination elements. This critical area is completed with the UNI framework and will allow users to seamlessly access the Metro Ethernet network from the customer premise equipment to the core backbone.
• Service Area Mandated to define Metro Ethernet services models, definitions and service parameters and attributes. The focus here is to define common services terminology along with the associate attributes and parameters to allow vendors, service providers and enterprise customers to speak in a common language for standardized Metro Ethernet implementations. Ethernet Line and Ethernet LAN are the top level agreed upon service categories with their associate attributes being defined throughout several whitepapers and reference documents.
• Test and Measurement – Mandated to define test methodologies and test suites that enable conformance to MEF services as defined in the MEF Specifications. Their intended use is as a basis for the MEF certification Program and for vendors to ensure their products will conform to MEF specifications. They also enable Service Providers to be assured that their services are implemented using conforming products and that the Services themselves conform and interoperate.

16. What has the MEF accomplished since its inception in June 2001?

As of April 2005, the MEF has approved 16 technical specifications (i.e. MEF standards)

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 Ethernet Services Attributes Phase I

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 Ethernet Services at the UNI

MEF 15 Requirements for Management of Metro Ethernet
Phase 1 Network Elements

MEF 16 Ethernet Local Management Interface

For a list of MEF technical specifications, please click here

An overview of the presentations is contained in the introduction PowerPoint

The MEF has also instigate the MEF Certification Program that has seen 150 Systems, 1000s tests conducted for 27 Equipment Manufacturers, 7 Service Providers certified. Again, details available from the MEF home page.

17. What is the role envisioned by the MEF for MPLS in delivering Ethernet based services?

The MEF is focused on metro Ethernet services but are transport agnostic we support various Ethernet transports including Sonet, WDM, dark fiber and use of MPLS.

The MEF is in the process of developing a transport-independent protection model with a related implementation framework that includes a proposal based on existing MPLS-based mechanisms as defined by the IETF. The Metro Ethernet protection model aims to deliver up to 50 ms restoration for Ethernet-based metro networks, as well as for other transport networks, independent of metro Ethernet network topologies.

In addition, MPLS has potential benefits for:

• Delivering connection-oriented services in metro Ethernet networks
• Addressing economic and operational complexities associated with inter-provider and intra-provider service provisioning across large distances (i.e. inter-city)

All these options are currently under consideration by the technical committee, and will be coordinated with the standardization process carried out in the IETF.
It is important to note, however, that MPLS is not the only option for providing these offerings. There is considerable work underway in the IEEE EFM committee that will also be considered by the MEF technical committees.

18. How is the MEF positioned relative to other industry forum organizations?

Since its inception, the MEF has expressed the intent to work with other technical forums to facilitate early interoperability and implementation agreements among vendors, service providers and end customers.
The MEF has good working relationship with the ITU-T, RPRA, MPLS and Frame Relay Alliance, OIF and are complimentary to all the MEF's efforts.

The Metro Ethernet Forum and IEEE802.17/RPRA are complementary. For example, the MEF defined Ethernet Services, capable of being carried over Ethernet-based transport, may also be carried over other transport technologies, such as standard RPR transport to be defined by IEEE802.17. In addition, the MEF may deem it necessary to define work to be done by other organizations on other transport technologies.

The first mile of transport previously served by the EFMA has now amalgamated with the MEF. The success of Carrier Ethernet has lead to activities in the access metro and core networks including delivery of Carrier Ethernet via both cable and wireless access service suppliers.

In the latter part of 2002, the MEF formed a formal, cooperative liaison relationship with the MPLS and Frame Relay Alliance (then MPLS Forum) to facilitate the development of MPLS and metro Ethernet technology and markets.

A combination of economics, operational and logistical attributes will mandate the viability and adoption of various service technologies. The MEF's work, and that of other strategic alliances, will let service providers select or combine technologies as they build their metro networks. This is why many of the Forums members are also members of these complimentary forums.

19. How is the MEF positioned with respect to SONET/SDH transport?

Once again, MEF is transport agnostic, meaning we support metro Ethernet over SONET, as well as WDM and dark fiber.

The MEF recognizes SONET/SDH as a broadly deployed transport that can deliver Ethernet services. The MEF defined Ethernet Services, capable of being carried over Ethernet-base transport, may also be carried over SONET/SDH networks. For this reason, the MEF has approved an Ethernet over SONET/SDH work item, designed to create implementation agreements as needed to assure MEF defined Ethernet Services operate over SONET/SDH networks.

A combination of economics, operational and logistical attributes will mandate viability and adoption of various service technologies. The MEFs work, and that of other strategic alliances, will let service providers select or combine technologies as they build their metro networks.

20. How does Ethernet relate to the convergence of voice and data networks in the metro area?

Over the past 20 years, Ethernet has successfully expanded its role in networking, and the low-latency transport carriage of voice and video traffic is underway as a logical next step.

Recent and pending technical advances make Ethernet a compelling technology for carrying voice, video, and data in metro networks. Ethernet is already used in certain metro voice applications, such as local voice switching, where low-latency Ethernet networks are used to carry voice traffic within a central office.

21. Is the Metro Ethernet Forum meant to expire following the completion of specific deliverables or after a certain time?

The Metro Ethernet Forum has no set expiration date its work will be done when Ethernet becomes the consensus-standard for metro networking.

22. Who are the members of the Metro Ethernet Forum?

The MEF is one of the fastest growing forums within the industry. Starting with 37 charter members in 2001 and growing to its current membership of over 80 companies, the MEF membership represents all the key leaders from service providers, equipment vendors and Enterprise organizations. For a complete current membership listing please refer to our web site, www.MetroEthernetForum.org.

23. How does a company become a member of the Metro Ethernet Forum?

Those companies interested in becoming a member should visit the web site where they can complete an application. The Metro Ethernet Forum application is located on our web site, www.MetroEthernetForum.org.
More information can be found on MEF Member Benefits at www.metroethernetforum.org/membbenefits.htm

24. How can I get more information?

Go to our web site. The web site, www.MetroEthernetForum.org, contains a great deal of information about the Forum. It also includes the names and contact information for the Forums officers. Feel free to contact them for additional information.