Forum Creates Common Language for Ethernet

By Paula Bernier Comments
Posted in Articles
Print

Carriers, equipment vendors and businesses shopping for connectivity can now speak the same language when it comes to discussing Ethernet services thanks to a new document from the Metro Ethernet Forum (MEF). MEF 1.0, which the forum says is the industry’s first Ethernet service standard, defines the building blocks used to create Ethernet services.

MEF 1.0, also known as the Ethernet service model (ESM), defines common parameters and attributes for Ethernet user network interface (UNI) and Ethernet virtual circuit (EVC). For example, the standard discusses such UNI attributes as port speed; whether a port can support multiple services; and the bandwidth profile for the UNI, explains Ralph Santitoro, co-chair of MEF’s marketing committee and director of network architecture at Nortel Networks. On the EVC side, he adds, the MEF 1.0 document outlines service attributes such as whether the connection is point-to-point or multipoint-to-multipoint; whether a customer’s class of service is preserved in the Ethernet header; and whether a customer’s virtual LAN ID is preserved.

MEF 1.0 is just the first of three technical specifications in what the MEF describes as phase one of its service documents. The next document the forum is working on discusses how to apply the ESM building blocks to create services and defines Ethernet line and Ethernet LAN service types. Ethernet Services Definitions, as this second spec is known, will likely be ratified by the MEF this quarter, says Santitoro.

EVC Service Attributes
Service Attributes Service AttributesParameters
EVC TypePoint-to-Point or Multipoint-to-Multipoint
UNI ListA list of UNIs (Identified via the UNI Identifier service attribute) used with the EVC
CE-VLAN ID PreservationYes or No. Specifies whether customer VLan ID is preserved or not.
CE-VLAN Cos PreservationYes or No. Specifies whether customer VLAN CoS (802.1p) is preserved or not.
Unlcast Service Frame DeliverySpecifies whether unlcast frames are Discarded, Delivered Unconditionally of Delivered Conditionally
Multicast Service Frame DeliverySpecifies whether multicast frames are discarded, Delivered Unconditionally of Delivered Conditionally
Broadcast Service Frame DeliverySpecifies whether broadcast frames ar Discarded, Delivered Unconditionally of Delivered Conditionally
Layer 2 Control Protocol ProcessingDiscard of Tunnel per protocol
Service PerformanceSpecifies the Frame Delay, Frame Jitter and Frame Loss per EVC or frames within an EVC Identified via their CE-VLAN CoS (802.1p) value

UNI Service Attributes
Service AttributeService AttributesParameters
UNI IdentifierA string used to identify of a UNI, e.g., NYC Bldg 12 Rm 102Slot22Port3
Physical MediumStandard Ethernet PHY
Speed10 Mbps, 100 Mbps, ! Gbps or 10 Gbps
ModeFull Duplex or Auto negotiation
MAC LayerIEEE 802.3-2002
Service MultiplexingYes or No. Defines whether multiple services can be on the UNI
UNI EVC IDA string used to identify an EVC, e.g., NCYBldg1Rm102Slot22Post3EVC3
CE-VLAN ID / EVC MapMapping table of customer VLAN IDs to EVC
Max. Number of EVCsThe maximum number of EVCs allowed per UNI
BundlingNo or Yes. Specifies that one or more customer VLAN IDs are mapped to an EVC at the UNI
All to One Bundling

No or Yes (all customer VLAN IDs are mapped to an EVC at the UNI).

Ingress Bandwidth Profile Per Ingress UNINone or <CIR, CBS, EIR, EBS>. This Bandwidth profile applies to all frames over particular EVC,
Ingress Bandwidth Profile Per EVC

None or <CIR, CBS, EIR, EBS>. This Bandwidth profile applies to all frames over particular EVC.

Ingress Bandwidth Profile Per CoS IDNone or <CIR, CBS, EIR, EBS>. This Bandwidth profile applies to all frames marked with a particular CoS ID over an EVC.
Layer 2 Control Protocol ProcessingDiscard, Peer or Pass to EVC per protocol

Probably more significant yet will be a third technical specification called Ethernet Traffic Management (ETM), which the MEF hopes to ratify in the second quarter. “Today, traffic management for Ethernet is not defined anywhere,” says Santitoro. “Many Ethernet services today don’t offer any QoS. Many large enterprise customers that want to use Ethernet demand QoS, so they’re now using private line, ATM and frame relay.”

ETM will address such traffic-management issues as how to define jitter, delay and packet loss in a consistent way, he says.

Nav Chander, a vice president for MEF and cochair for MEF’s marketing committee and director of product marketing at Coriolis Networks, says the traffic management standard will be “a huge benefit” to service providers by offering a common language for defining multipoint-to-multipoint services such as voice and multimedia for which Ethernet is the ideal transport. “The challenge, of course, is that the industry doesn’t have these definitions,” says Chander. “Those definitions are not easy to implement. It will help accelerate new types of Ethernet services.”


Comments