Share on Facebook Share on Twitter Email
Answers.com

Metro Ethernet Forum

 

A standard for carrier-class Ethernet services for network service providers. Carrier Ethernet extends Ethernet from the local area network (LAN) to the wide area network (WAN), enabling companies to connect their Ethernet LANs to service provider networks via the same Ethernet interface they use to attach every device in the network. It provides a transparent LAN service that bridges LANs in separate locations together as if they were one network. An administrator can manage a global Ethernet network using virtual LAN tools, which group computers together logically no matter where they physically reside. See virtual LAN and carrier class.

Using traditional TDM and SONET backbones, service providers have taken days and weeks to establish wide area networks for new customers and make subsequent changes. Since Carrier Ethernet connects to a LAN using Ethernet plugs and sockets, new customers can be hooked up to Gigabit Ethernet and 10 Gigabit Ethernet interfaces in a much shorter time. See TDM and SONET.

From Local Networks to Subscriber Networks

Residing within a building or campus, almost all business networks are Ethernet. In order to extend Ethernet to a global network that serves multiple customers, Ethernet had to be extensively upgraded to handle fault tolerance, levels of service and continuous changes in a timely manner. For detailed information about the standards, visit the Metro Ethernet Forum (MEF) at www.metroethernetforum.org.

MPLS for Service Quality

Most LAN traffic is IP based; therefore the bulk of all Carrier Ethernet traffic is IP packets. Since MPLS is a method for providing quality of service (QoS) in an IP network, it can also be used to ensure quality levels in a Carrier Ethernet network. See MPLS and QoS.

Carrier Ethernet Over SONET

Although Carrier Ethernet is designed to transport Ethernet frames natively (layer 2 in the OSI model), network providers can deploy it over legacy point-to-point SONET circuits. Carrier Ethernet can also ride directly over fiber (see WDM).

Ethernet Virtual Connection (EVC) Topology

Carrier Ethernet is based on a virtual connection between two user network interface (UNI) points. An "E-Line" is one EVC (point-to-point), whereas an "E-LAN" offers a multipoint EVC topology just like any local network. See Metro Ethernet.

Private or Virtual Point-to-Point
There are two types of point-to-point E-Line connections: an Ethernet Private Line (EPL) is a dedicated connection between two points, whereas an Ethernet Virtual Private Line (EVPL) is shared with other network connections.

Multipoint Topology
An E-LAN provides a multipoint topology like a local network. Each node can reach any other node.

Download Computer Desktop Encyclopedia to your iPhone/iTouch

Search unanswered questions...
Enter a question here...
Search: All sources Community Q&A Reference topics
Wikipedia: Metro Ethernet Forum
Top

The Metro Ethernet Forum (MEF) was founded in 2001. It is a non-profit international industry consortium, dedicated to worldwide adoption of Carrier Ethernet networks and services.

The Forum is composed 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 140 members as of January, 2008.

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. The Forum makes recommendations to existing standards bodies and creates specifications that are not being developed by (or fall within the scope of) other standards bodies.

Contents

MEF White Papers

Metro Ethernet Services - A Technical Overview

This white paper provides a comprehensive technical overview of Ethernet services, based on the work of the Metro Ethernet Forum (MEF) Technical Committee. The paper is intended to help buyers and users of Ethernet services understand the various types and characteristics of Ethernet services, and to help service providers clearly communicate their service capabilities.


MEF Technical Specifications

As of Feb 2009, the MEF has approved 19 technical specifications (see the full list):

  • 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 (supersedes MEF 10, below) -
  • 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 20 UNI Type 2 Implementation Agreement
  • MEF 21 Abstract Test Suite for UNI Type 2 Part 1 Link OAM
  • MEF 22 Mobile Backhaul Implementation Agreement

External links

See also


 
 

 

Copyrights:

Computer Desktop Encyclopedia. THIS DEFINITION IS FOR PERSONAL USE ONLY.
All other reproduction is strictly prohibited without permission from the publisher.
© 1981-2010 The Computer Language Company Inc.  All rights reserved.  Read more
Wikipedia. This article is licensed under the Creative Commons Attribution/Share-Alike License. It uses material from the Wikipedia article "Metro Ethernet Forum" Read more