Carrier Ethernet 2.0 Services - MEF...2012/06/08 · •Carrier Ethernet 2.0 EP-LAN and EVP-LAN...

1

A Comparison of Services Attributes for CE 1.0 and CE 2.0 by Service Type

Document Editor, Isabelle Morency, Iometrix

Carrier Ethernet 2.0 Services Technical Foundation Document

Version 2

June 2012

2

Carrier Ethernet 2.0 Services Highlights

Multi-CoS

• Carrier Ethernet 2.0 multiple classes of service allow network optimization to fit a wide range of customer application requirements

• Carrier Ethernet 2.0 standardized classes of service are associated with MEF-defined performance objectives and performance tiers

Managed

• Carrier Ethernet 2.0 Service OAM enables subscribers and service providers to check the continuity of an EVC across the entire network, to trace the path of a service or to ping a target MEP or configured MIP, for subscriber and test MEGs

• Carrier Ethernet 2.0 extends traffic management to include both ingress and egress bandwidth profile capabilities

• Carrier Ethernet 2.0 specifies standard granularities for per UNI, per EVC and per class of service bandwidth profiles to tightly fit customer bandwidth requirements

Interconnected

• Carrier Ethernet 2.0 E-Access Services allow service providers to reach out-of-franchise customer locations and deliver port-based and VLAN-based services

3 3

Carrier Ethernet 2.0 Services

• The creation of Carrier Ethernet 2.0 E-Line, E-LAN and E-Tree services as defined in MEF 6.1 and E-Access services as defined in MEF 33 requires different combinations of service attributes and performance attributes.

• To assess compliance of each service independently, all the attributes defining the specific service need to be verified.

• The tables on the following slides provide details of each attribute required to create Carrier Ethernet 2.0 E-Line, E-LAN, E-Tree and E-Access services. The tables are structured as follows: Service Attributes What’s new in Carrier Ethernet 2.0

EPL EVPL

1.0 2.0 1.0 2.0

Attribute 1 Carrier Ethernet 2.0 requires ’Attribute 1’ to be… ✔ ✔

Enh. ✔

✔ Enh.

Attribute 2 Carrier Ethernet 1.0 and 2.0 require ‘Attribute 2’ to support… ✔ ✔ ✔ ✔

Attribute 3 Carrier Ethernet 2.0 requires ‘Attribute 3’ to be configurable as per… ✔ New ✔

New

✔ New

New attribute introduced in CE 2.0

✔ Enh. Attribute introduced in CE 1.0 and enhanced in CE 2.0

✔ Attribute introduced in CE 1.0 and still applicable as is in CE 2.0

Attribute not specified

4 4

Carrier Ethernet 2.0 E-Line Service Type • Carrier Ethernet 2.0 EPL and EVPL services as defined in MEF 6.1 can be used to

create a broad range of point-to-point services. • A Carrier Ethernet 2.0 EPL service uses dedicated UNIs and provides a high

degree of transparency such that Service Frames are identical at both the source and destination UNIs. All-to-one bundling at the UNIs minimizes the coordination between the Subscriber and Service Provider on the definition of the CE-VLAN ID/EVC Map at each UNI.

• A Carrier Ethernet 2.0 EVPL service allows for service multiplexing and bundling enabling the support of multiple EVCs at the UNI and the mapping of more than one CE-VLAN ID per EVC.

Carrier Ethernet 2.0 EPL Service

CE

UNI UNI

CE

Carrier Ethernet Network

UNI

UNI

CE

CE

CE

Carrier Ethernet 2.0 EVPL Services

Carrier Ethernet Network

UNI

5

UNI Service Attributes

What’s new in Carrier Ethernet 2.0 EPL EVPL

1.0 2.0 1.0 2.0

UNI Identifier Carrier Ethernet 1.0 and 2.0 require that the UNI Identifier be an arbitrary text string to identify the UNI.

✔ ✔ ✔ ✔

Physical Medium Carrier Ethernet 2.0 requires the UNI Physical Medium to be one of the PHYs listed in IEEE 802.3-2005, except PON interfaces.

✔ ✔

Enh. ✔ ✔

Enh.

Speed and Mode Carrier Ethernet 1.0 and 2.0 require the UNI Speed to be 10 Mbps, 100 Mbps, 10/100 Mbps Auto-neg, 10/100/1000 Auto-neg, 1 Gbps or 10 Gbps in Full Duplex mode.

✔ ✔ ✔ ✔

MAC Layer Carrier Ethernet 2.0 requires the MAC Layer to be IEEE 802.3-2005. ✔ ✔

Enh. ✔ ✔

Enh.

UNI MTU Size The UNI MTU Size is a new attribute of Carrier Ethernet 2.0. CE 2.0 requires the UNI MTU size to be greater or equal to 1522 bytes. ✔

New ✔ New

Service Multiplexing If Service Multiplexing is supported, Carrier Ethernet 2.0 requires the support of a minimum number of EVCs based on the UNI Speed per UNI Type 1 IA. ✔

✔ Enh.

Bundling If Bundling is supported, Carrier Ethernet 2.0 requires the support of a minimum number of CE-VLAN IDs based on the UNI Speed per UNI Type 1 IA. ✔

✔ Enh.

All to One Bundling If All to One Bundling is supported, Carrier Ethernet 2.0 requires that it only applies to Port based services such as EPL.

✔ ✔

Enh.

CE-VLAN ID for untagged and priority tagged Service Frames

Carrier Ethernet 1.0 and 2.0 require that all untagged and priority tagged Service Frames at the UNI map to the same EVC as is used for all other Service Frames for EPL and requires to specify the CE-VLAN ID for untagged and priority tagged Service Frames in the range of 1-4094 for EVPL.

✔ ✔ ✔ ✔

Maximum Number of EVCs Carrier Ethernet 2.0 requires that the maximum number of EVCs per UNI be 1 for EPL and be greater or equal to 1 for EVPL.

✔ ✔

Enh. ✔ ✔

Enh.

Ingress BWP per UNI If ingress BWP per UNI is supported, Carrier Ethernet 2.0 requires configuration granularities per UNI Type 1 IA.

✔ ✔

Enh. ✔ ✔

Enh.

Egress BWP per UNI Egress BWP per UNI is a new attribute of Carrier Ethernet 2.0. If egress BWP per UNI is supported, CE 2.0 requires requires configuration granularities per UNI Type 2 IA. ✔

New

L2CP Processing Carrier Ethernet 2.0 requires that L2CP processing be as specified in MEF 6.1.1. ✔ ✔

Enh. ✔ ✔

Enh.

E-Line - UNI Service Attributes

✔ New New attribute introduced in CE 2.0 ✔ Attribute introduced in CE 1.0 and still applicable as is in CE 2.0

✔ Enh.

Attribute introduced in CE 1.0 and enhanced in CE 2.0 Attribute not specified

6

EVC per UNI Service Attributes


1.0 2.0 1.0 2.0

UNI EVC ID Carrier Ethernet 1.0 and 2.0 require the UNI EVC ID to be a string formed by the concatenation of the UNI ID and the EVC ID.

✔ ✔ ✔ ✔

CE-VLAN ID / EVC Map Carrier Ethernet 2.0 requires that all Service Frames at the UNI map to a single point-to-point EVC for EPL and to specify mapping table of CE-VLAN IDs to EVC ID for EVPL.

✔ ✔

Enh. ✔ ✔

Enh.

Ingress BWP Per EVC If ingress BWP per EVC is supported, Carrier Ethernet 2.0 requires configuration granularities per UNI Type 1 IA.

✔ ✔

Enh. ✔ ✔

Enh.

Ingress BWP Per CoS ID If ingress BWP per CoS ID is supported, Carrier Ethernet 2.0 requires configuration granularities per UNI Type 1 IA.

✔ ✔

Enh. ✔ ✔

Enh.

Egress BWP Per EVC Carrier Ethernet 2.0 requires to not specify Egress BWP per EVC. Egress BWP Per CoS ID Carrier Ethernet 2.0 requires to not specify Egress BWP per CoS ID.

E-Line - EVC per UNI Service Attributes and SOAM Frames Handling

SOAM Frames Handling What’s new in Carrier Ethernet 2.0 1.0 2.0 1.0 2.0

Connectivity Check messages Carrier Ethernet 2.0 requires that all CCM frames at the default Test and Subscriber MEG levels be tunneled.

✔ New ✔

New

Linktrace messages with at least one MIP configured

Where at least one MIP is configured at the default Test or Subscriber MEG level, Carrier Ethernet 2.0 requires that Linktrace frames with the corresponding target MAC DA and MEG level be peered or discarded.

✔ New ✔

New

Linktrace messages without any MIPs configured

Where no MIPs are configured at the default Test or Subscriber MEG level, Carrier Ethernet 2.0 requires that Linktrace frames with the corresponding target MAC DA and MEG level be tunneled.

✔ New ✔

New

Unicast Loopback messages with at least one MIP configured

Where at least one MIP is configured at the default Test or Subscriber MEG level, Carrier Ethernet 2.0 requires that Loopback frames with the corresponding target unicast MAC DA and MEG level be peered or discarded.

✔ New ✔

New


Where at least one MIP is configured at the default Test or Subscriber MEG level, Carrier Ethernet 2.0 requires that Loopback frames with the corresponding MEG level and a target unicast DA not equal to the MAC address of any MIPs be tunneled.

✔ New ✔

New

Multicast Loopback messages Carrier Ethernet 2.0 requires that all multicast Loopback frames at the default Test and Subscriber MEG levels be tunneled.

✔ New ✔

New


✔ Enh.


7 7

EVC Service Attributes


1.0 2.0 1.0 2.0

EVC Type Carrier Ethernet 1.0 and 2.0 require that the EVC Type be point-to-point. ✔ ✔ ✔ ✔

EVC ID Carrier Ethernet 1.0 and 2.0 require that the EVC ID be an arbitrary string, unique across the MEN, for the EVC supporting the service instance.

✔ ✔ ✔ ✔

UNI List Carrier Ethernet 1.0 and 2.0 require that the UNI List be the two UNIs associated with the EVC and that the UNI type be Root for each UNI.

✔ ✔ ✔ ✔

Maximum Number of UNIs Carrier Ethernet 1.0 and 2.0 require that the Maximum Number of UNIs be 2. ✔ ✔ ✔ ✔

EVC MTU Size UNI MTU Size is a new attribute of Carrier Ethernet 2.0. CE 2.0 requires the EVC MTU size to be greater or equal to 1522 bytes. ✔

New ✔ New

CE-VLAN ID Preservation Carrier Ethernet 1.0 and 2.0 require that CE-VLAN ID Preservation be Yes for EPL and be either Yes or No for EVPL.

✔ ✔ ✔ ✔

CE-VLAN CoS Preservation Carrier Ethernet 2.0 requires that CE-VLAN CoS Preservation be Yes for EPL and be either Yes or No for EVPL.

✔ ✔

Enh. ✔ ✔

Enh.

Unicast, Multicast and Broadcast Service Frame Delivery

Carrier Ethernet 1.0 and 2.0 require that Unicast, Multicast and Broadcast Service Frames be delivered unconditionally for EPL and deliver unconditionally or conditionally for EVPL. If delivered conditionally, CE 2.0 requires to specify the delivery criteria.

✔ ✔ ✔ ✔


Enh. ✔ ✔

Enh.

EVC Performance Carrier Ethernet 2.0 requires at least one CoS, to specify the CoS ID(s) and to list values/objectives for each applicable performance attribute. Applicable service performance attributes and objectives are specified in MEF 23.1.

✔ ✔

Enh. ✔ ✔

Enh.

E-Line - EVC Service Attributes


✔ Enh.


8 8

Carrier Ethernet 2.0 E-LAN Service Type

• Carrier Ethernet 2.0 EP-LAN and EVP-LAN services as defined in MEF 6.1 can be used to create a broad range of multipoint-to-multipoint services.

• A Carrier Ethernet 2.0 EP-LAN service uses dedicated UNIs and provides a high degree of transparency such that Service Frames are identical at both the source and destination UNIs. All-to-one bundling at the UNIs minimizes the coordination between the Subscriber and Service Provider on the definition of the CE-VLAN ID/EVC Map at each UNI.

• A Carrier Ethernet 2.0 EVP-LAN service allows for service multiplexing and bundling enabling the support of multiple EVCs at the UNI and the mapping of more than one CE-VLAN ID per EVC.

Carrier Ethernet 2.0 EP-LAN Service

Carrier Ethernet 2.0 EVP-LAN Service

CE

UNI

UNI

UNI

CE

CE

ISP POP

Internet

UNI

UNI

CE

CE

CE

UNI

Carrier Ethernet Network Carrier Ethernet Network

9


What’s new in Carrier Ethernet 2.0 EP-LAN EVP-LAN

1.0 2.0 1.0 2.0

UNI Identifier Carrier Ethernet 1.0 and 2.0 require that the UNI Identifier be an arbitrary text string to identify the UNI.

✔ ✔ ✔ ✔

Physical Medium Carrier Ethernet 2.0 requires the UNI Physical Medium to be one of the PHYs listed in IEEE 802.3-2005, except PON interfaces.

✔ ✔

Enh. ✔

✔ Enh.

Speed and Mode Carrier Ethernet 1.0 and 2.0 require the UNI Speed to be 10 Mbps, 100 Mbps, 10/100 Mbps Auto-neg, 10/100/1000 Auto-neg, 1 Gbps or 10 Gbps in Full Duplex mode.

✔ ✔ ✔ ✔

MAC Layer Carrier Ethernet 2.0 requires the MAC Layer to be IEEE 802.3-2005. ✔ ✔

Enh. ✔

✔ Enh.


New ✔ New


✔ Enh.


✔ Enh.

All to One Bundling If All to One Bundling is supported, Carrier Ethernet 2.0 requires that it only applies to Port based services such as EP-LAN.

✔ ✔

Enh.


Carrier Ethernet 1.0 and 2.0 require that all untagged and priority tagged Service Frames at the UNI map to the same EVC as is used for all other Service Frames for EP-LAN and requires to specify the CE-VLAN ID for untagged and priority tagged Service Frames in the range of 1-4094 for EVP-LAN.

✔ ✔ ✔ ✔

Maximum Number of EVCs Carrier Ethernet 2.0 requires that the maximum number of EVCs per UNI be 1 for EP-LAN and be greater or equal to 1 for EVP-LAN.

✔ ✔

Enh. ✔

✔ Enh.

Ingress BWP per UNI If ingress BWP per UNI is supported, Carrier Ethernet 2.0 requires configuration granularities per UNI Type 1 IA.

✔ ✔

Enh. ✔

✔ Enh.

Egress BWP per UNI Egress BWP per UNI is a new attribute of Carrier Ethernet 2.0. If egress BWP per UNI is supported, CE 2.0 requires requires configuration granularities per UNI Type 2 IA. ✔

New ✔ New


Enh. ✔

✔ Enh.

E-LAN - UNI Service Attributes


✔ Enh.


10



1.0 2.0 1.0 2.0

UNI EVC ID Carrier Ethernet 1.0 and 2.0 require the UNI EVC ID to be a string formed by the concatenation of the UNI ID and the EVC ID.

✔ ✔ ✔ ✔

CE-VLAN ID / EVC Map Carrier Ethernet 2.0 requires that all Service Frames at the UNI map to a single multipoint-to-multipoint EVC for EP-LAN and to specify mapping table for EVP-LAN.

✔ ✔

Enh. ✔

✔ Enh.

Ingress BWP Per EVC If ingress BWP per EVC is supported, Carrier Ethernet 2.0 requires configuration granularities per UNI Type 1 IA.

✔ ✔

Enh. ✔

✔ Enh.

Ingress BWP Per CoS ID If ingress BWP per CoS ID is supported, Carrier Ethernet 2.0 requires configuration granularities per UNI Type 1 IA.

✔ ✔

Enh. ✔

✔ Enh.

Egress BWP Per EVC Egress BWP per EVC is a new attribute of Carrier Ethernet 2.0. If egress BWP per EVC is supported, CE 2.0 requires requires configuration granularities per UNI Type 2 IA.

✔ New ✔

New

Egress BWP Per CoS ID Egress BWP per CoS ID is a new attribute of Carrier Ethernet 2.0. If egress BWP per CoS is supported, CE 2.0 requires requires configuration granularities per UNI Type 2 IA.

✔ New ✔

New

E-LAN - EVC per UNI Service Attributes and SOAM Frames Handling


Connectivity Check messages Carrier Ethernet 2.0 requires that all CCM frames at the default Test and Subscriber MEG levels be tunneled.

✔ New ✔

New



✔ New ✔

New



✔ New ✔

New



✔ New ✔

New



✔ New ✔

New

Multicast Loopback messages Carrier Ethernet 2.0 requires that all multicast Loopback frames at the default Test and Subscriber MEG levels be tunneled. ✔

New ✔ New


✔ Enh.


11



1.0 2.0 1.0 2.0

EVC Type Carrier Ethernet 1.0 and 2.0 require that the EVC Type be multipoint-to-multipoint.

✔ ✔ ✔ ✔

EVC ID Carrier Ethernet 1.0 and 2.0 require that the EVC ID be an arbitrary string, unique across the MEN, for the EVC supporting the service instance.

✔ ✔ ✔ ✔

UNI List Carrier Ethernet 1.0 and 2.0 require that the UNI List be all UNIs associated with the EVC and that the UNI type be Root for each UNI.

✔ ✔ ✔ ✔

Maximum Number of UNIs Carrier Ethernet 1.0 and 2.0 require that the Maximum Number of UNIs be greater or equal to 2.

✔ ✔ ✔ ✔

EVC MTU Size UNI MTU Size is a new attribute of Carrier Ethernet 2.0. CE 2.0 requires the EVC MTU size to be greater or equal to 1522 bytes.

✔ New ✔

New

CE-VLAN ID Preservation Carrier Ethernet 1.0 and 2.0 require that CE-VLAN ID Preservation be Yes for EP-LAN and be either Yes or No for EVP-LAN.

✔ ✔ ✔ ✔

CE-VLAN CoS Preservation Carrier Ethernet 2.0 requires that CE-VLAN CoS Preservation be Yes for EP-LAN and be either Yes or No for EVP-LAN.

✔ ✔

Enh. ✔

✔ Enh.


Carrier Ethernet 1.0 and 2.0 require that Unicast, Multicast and Broadcast Service Frames be deliver unconditionally or conditionally. If delivered conditionally, CE 2.0 requires to specify the delivery criteria.

✔ ✔ ✔ ✔


Enh. ✔

✔ Enh.

EVC Performance Carrier Ethernet 2.0 requires at least one CoS, to specify the CoS ID(s) and to list values/objectives for each applicable performance attribute. MEF 23.1 does not specify performance objectives for multipoint-to-multipoint services.

✔ ✔ ✔ ✔

E-LAN - EVC Service Attributes


✔ Enh.


12 12

Carrier Ethernet 2.0 E-Tree Service Type

• Carrier Ethernet 2.0 EP-Tree and EVP-Tree services as defined in MEF 6.1 can be used to create a broad range of rooted-multipoint services.

• A Carrier Ethernet 2.0 EP-Tree service uses dedicated root and leaf UNIs and provides a high degree of transparency such that Service Frames are identical at both the source and destination UNIs. All-to-one bundling at the UNIs minimizes the coordination between the Subscriber and Service Provider on the definition of the CE-VLAN ID/EVC Map at each UNI.

• A Carrier Ethernet 2.0 EVP-Tree service uses root and leaf UNIs and allows for service multiplexing and bundling enabling the support of multiple EVCs at the UNI and the mapping of more than one CE-VLAN ID per EVC.

Carrier Ethernet 2.0 EVP-Tree Service

Carrier Ethernet 2.0 EP-Tree Service

Leaf

Leaf

Leaf Root

UNI

UNI

Root

CE

UNI

UNI CE

UNI

UNI

CE

CE

CE CE

Root

Leaf Leaf

Leaf

UNI

UNI CE CE

Carrier Ethernet Network Carrier Ethernet Network

13


What’s new in Carrier Ethernet 2.0 EP-Tree EVP-Tree

1.0 2.0 1.0 2.0

UNI Identifier Carrier Ethernet 2.0 requires that the UNI Identifier be an arbitrary text string to identify the UNI. ✔

New ✔ New

Physical Medium Carrier Ethernet 2.0 requires the UNI Physical Medium to be one of the PHYs listed in IEEE 802.3-2005, except PON interfaces. ✔

New ✔ New

Speed and Mode Carrier Ethernet 2.0 requires the UNI Speed to be 10 Mbps, 100 Mbps, 10/100 Mbps Auto-neg, 10/100/1000 Auto-neg, 1 Gbps or 10 Gbps in Full Duplex mode. ✔

New ✔ New

MAC Layer Carrier Ethernet 2.0 requires the MAC Layer to be IEEE 802.3-2005. ✔ New ✔

New


New ✔ New


new


new

All to One Bundling If All to One Bundling is supported, Carrier Ethernet 2.0 requires that it only applies to Port based services such as EP-LAN. ✔

New


Carrier Ethernet 2.0 requires that all untagged and priority tagged Service Frames at the UNI map to the same EVC as is used for all other Service Frames for EP-Tree and requires to specify the CE-VLAN ID for untagged and priority tagged Service Frames in the range of 1-4094 for EVP-Tree.

✔ New ✔

New

Maximum Number of EVCs Carrier Ethernet 2.0 requires that the maximum number of EVCs per UNI be 1 for EP-Tree and be greater or equal to 1 for EVP-Tree. ✔

New ✔ New

Ingress BWP per UNI If ingress BWP per UNI is supported, Carrier Ethernet 2.0 requires configuration granularities per UNI Type 1 IA. ✔

New ✔ New

Egress BWP per UNI Egress BWP per UNI is a new attribute of Carrier Ethernet 2.0. If egress BWP per UNI is supported, CE 2.0 requires requires configuration granularities per UNI Type 2 IA.

✔ New ✔

New

L2CP Processing Carrier Ethernet 2.0 requires that L2CP processing be as specified in MEF 6.1.1. ✔ New ✔

New

E-Tree - UNI Service Attributes


✔ Enh.


14



1.0 2.0 1.0 2.0

UNI EVC ID Carrier Ethernet 2.0 requires the UNI EVC ID to be a string formed by the concatenation of the UNI ID and the EVC ID.

✔ New ✔

New

CE-VLAN ID / EVC Map Carrier Ethernet 2.0 requires that all Service Frames at the UNI map to a single rooted-multipoint EVC for EP-Tree and to specify mapping table for EVP-Tree. ✔

New ✔ New

Ingress BWP Per EVC If ingress BWP per EVC is supported, Carrier Ethernet 2.0 requires configuration granularities per UNI Type 1 IA. ✔

New ✔ New

Ingress BWP Per CoS ID If ingress BWP per CoS ID is supported, Carrier Ethernet 2.0 requires configuration granularities per UNI Type 1 IA. ✔

New ✔ New

Egress BWP Per EVC Egress BWP per EVC is a new attribute of Carrier Ethernet 2.0. If egress BWP per EVC is supported, CE 2.0 requires requires configuration granularities per UNI Type 2 IA.

✔ New ✔

New

Egress BWP Per CoS ID Egress BWP per CoS ID is a new attribute of Carrier Ethernet 2.0. If egress BWP per CoS is supported, CE 2.0 requires requires configuration granularities per UNI Type 2 IA.

✔ New ✔

New

E-Tree - EVC per UNI Service Attributes and SOAM Frames Handling


Connectivity Check messages Carrier Ethernet 2.0 requires that all CCM frames at the default Test and Subscriber MEG levels be tunneled. ✔

New ✔ New



✔ New ✔

New



✔ New ✔

New



✔ New ✔

New



✔ New ✔

New

Multicast Loopback messages Carrier Ethernet 2.0 requires that all multicast Loopback frames at the default Test and Subscriber MEG levels be tunneled.

✔ New ✔

New


✔ Enh.


15



1.0 2.0 1.0 2.0

EVC Type Carrier Ethernet 2.0 requires that the EVC Type be rooted-multipoint. ✔ New ✔

New

EVC ID Carrier Ethernet 2.0 requires that the EVC ID be an arbitrary string, unique across the MEN, for the EVC supporting the service instance.

✔ New ✔

New

UNI List Carrier Ethernet 2.0 requires that the UNI List be all UNIs associated with the EVC and that the UNI Type for at least 1 UNI be Root and that all UNIs that are not UNI Type Root be UNI Type Leaf.

✔ New ✔

New

Maximum Number of UNIs Carrier Ethernet 2.0 requires that the Maximum Number of UNIs be greater or equal to 2. ✔

New ✔ New

EVC MTU Size UNI MTU Size is a new attribute of Carrier Ethernet 2.0. CE 2.0 requires the EVC MTU size to be greater or equal to 1522 bytes. ✔

New ✔ New

CE-VLAN ID Preservation Carrier Ethernet 2.0 requires that CE-VLAN ID Preservation be Yes for EP-Tree and be either Yes or No for EVP-Tree. ✔

New ✔ New

CE-VLAN CoS Preservation Carrier Ethernet 2.0 requires that CE-VLAN CoS Preservation be Yes for EP-Tree and be either Yes or No for EVP-Tree. ✔

New ✔ New


Carrier Ethernet 2.0 requires that Unicast, Multicast and Broadcast Service Frames be deliver unconditionally or conditionally. If delivered conditionally, CE 2.0 requires to specify the delivery criteria.

✔ New ✔

New

L2CP Processing Carrier Ethernet 2.0 requires that L2CP processing be as specified in MEF 6.1.1. ✔ New ✔

New

EVC Performance Carrier Ethernet 2.0 requires at least one CoS, to specify the CoS ID(s) and to list values/objectives for each applicable performance attribute. MEF 23.1 does not specify performance objectives for rooted-multipoint services.

✔ New ✔

New

E-Tree - EVC Service Attributes


✔ Enh.


16 16

Carrier Ethernet 2.0 E-Access Service Type • Carrier Ethernet 2.0 Access EPL and Access EVPL services as defined in MEF 33 can be used to create a

broad range of access services.

• A Carrier Ethernet 2.0 Access EPL service interconnects a dedicated UNI and an ENNI. It provides a high degree of transparency such that Service Frames are delivered unchanged at the ENNI with the addition of an S-VLAN tag and the ENNI Frames are delivered unchanged at the UNI except for the removal of the S-VLAN tag.

• A Carrier Ethernet 2.0 Access EVPL service uses a UNI that can support multiple service instances. The Operator and Service Provider coordinate on defining the OVC End Point Map for each OVC at the UNI and for the value of the S-VLAN ID that maps to each OVC End Point at the ENNI. Access EVPL provides a high degree of transparency such that Service Frames are delivered unchanged at the ENNI with the addition of an S-VLAN tag and the ENNI Frames are delivered unchanged at the UNI except for the removal of the S-VLAN tag.

Carrier Ethernet 2.0

Access EPL Service

Carrier Ethernet 2.0

Access EVPL Service

End-User

ENNI UNI

Access EPL

End-User

UNI Carrier Ethernet

Access Service Provider

End-User

ENNI

UNI

Access EVPL

End-User

UNI

Retail Service

Provider

Retail Service

Provider

Carrier Ethernet Access Service Provider

17


What’s new in Carrier Ethernet 2.0 Access EPL Access EVPL

1.0 2.0 1.0 2.0

UNI Identifier Carrier Ethernet 2.0 requires the UNI ID to be any string. ✔ New ✔

New

Physical Medium Carrier Ethernet 2.0 requires the Physical Medium to be a standard Ethernet PHY defined in IEEE 802.3-2005 or IEEE 802.3ae-2002. ✔

New ✔ New

Speed and Mode Carrier Ethernet 2.0 requires the UNI Speed to be 10 Mbps, 100 Mbps, 10/100 Mbps Auto-neg, 1 Gbps or 10 Gbps in Full Duplex mode. ✔

New ✔ New

MAC Layer Carrier Ethernet 2.0 requires the MAC Layer to be IEEE 802.3-2005. ✔ New ✔

New

UNI MTU Size Carrier Ethernet 2.0 requires the UNI MTU Size to be Integer greater or equal 1522 bytes. ✔

New ✔ New


Carrier Ethernet 2.0 requires that the CE-VLAN ID for untagged and priority tagged be a value from 1-4094 for Access EPL and requires to specify if untagged and priority tagged frames are to be supported for Access EVPL and if supported, the CE-VLAN ID for untagged and priority tagged Service Frames is to be included in the OVC Endpoint Map.

✔ New ✔

New

Maximum Number of OVCs per UNI Carrier Ethernet 2.0 requires that the maximum number of OVCs per UNI be 1 for Access EPL and be greater or equal to 1 for Access EVPL.

✔ New ✔

New

Maximum Number of CE-VLAN IDs per OVC

Carrier Ethernet 2.0 requires that the OVC Endpoint Map support a value equal to 1 for Access EVPL and that it should support values greater than 1. This attribute is not specified for Access EPL.

✔ New

Ingress BWP per UNI Carrier Ethernet 2.0 requires to not specify Ingress BWP per UNI.

Egress BWP per UNI Carrier Ethernet 2.0 requires to not specify Egress BWP per UNI.

E-Access - UNI Service Attributes


✔ Enh.


18

ENNI Service Attributes


1.0 2.0 1.0 2.0

Operator ENNI Identifier Carrier Ethernet 2.0 requires that the Operator ENNI Identifier be a string that is unique across the Operator MEN. ✔

New ✔ New

Physical Layer Carrier Ethernet 2.0 requires that the Physical Layer be one of the following PHYs in full duplex mode: 1000Base-SX, 1000Base-LX, 1000Base T, 10GBase-SR, 10GBase-LX4, 10GBase-LR, 10GBase-ER, 10GBase-SW, 10GBase-LW, 10GBase-EW.

✔ New ✔

New

Frame Format

An ENNI Frame can have zero or more VLAN tags. Carrier Ethernet 2.0 requires that when an ENNI Frame has a single tag, that tag is an S-Tag. When an ENNI Frame has two tags, the outer tag is an S-Tag and the next tag is a C-Tag as defined in IEEE Std 802.1ad-2005.

✔ New ✔

New

Number of Links Carrier Ethernet 2.0 requires that the number of links be an integer with value equal to 1 or 2. ✔

New ✔ New

Protection Mechanism Carrier Ethernet 2.0 requires that the protection mechanism be Link Aggregation, none, or other.

✔ New ✔

New

ENNI MTU Size Carrier Ethernet 2.0 requires that the ENNI MTU Size be an integer number of bytes greater or equal to 1526.

✔ New ✔

New

End Point Map Carrier Ethernet 2.0 requires that each S-VLAN ID value associated with an instance of Access EPL or Access EVPL Service map to a distinct End Point, of Type OVC. ✔

New ✔ New

Maximum Number of OVCs Carrier Ethernet 2.0 requires that the Maximum Number of OVCs be an integer greater or equal to 1. ✔

New ✔ New

Maximum Number of OVC End Points per OVC

Carrier Ethernet 2.0 requires that the Maximum Number of OVC EPs be an integer greater or equal to 1. ✔

New ✔ New

E-Access - ENNI Service Attributes


✔ Enh.


19

OVC Per UNI Service Attributes


1.0 2.0 1.0 2.0

UNI OVC ID Carrier Ethernet 2.0 requires that the UNI OVC ID be a string formed by the concatenation of the UNI identifier and the OVC identifier. ✔

New ✔ New

OVC EP Map

Carrier Ethernet 2.0 requires that the OVC EP Map contain all CE-VLAN ID values {1, 2, …4095} mapped to a single OVC EP for Access EPL and requires to specify the mapping table of CE-VLAN ID to OVC EP for Access EVPL which must not contain all CE-VLAN ID values mapped to a single OVC EP.

✔ New ✔

New

Class of Service Identifier for Service Frames

Carrier Ethernet 2.0 requires that the CoS ID for Service Frames be the OVC EP to which the Service Frame is mapped and that the OVC have a single CoS Name. ✔

New ✔ New

Ingress BWP per OVC EP at a UNI

Carrier Ethernet 2.0 requires the support of Ingress BWP per OVC EP at the UNI and requires configuration to support CIR values up to 70% of the UNI speed, in the following increments:

1 – 10 Mb/s, increments of 1 Mb/s 10 – 100 Mb/s, increments of 10 Mb/s 100 – 1000 Mb/s, increments of 100 Mb/s 1 – 10 Gb/s, increments of 1 Gb/s

These required CIR increments are subject to the limit imposed by the UNI speed. MAY support other values of CIR. MUST allow configuration of EIR = 0, EBS = 0, CF = 0, Color Mode = “color blind”. MAY support other values of EIR, EBS, CF, and Color Mode. MUST have CBS >= 12176 bytes. MUST NOT be combined with any other type of ingress bandwidth profile.

✔ New ✔

New

Ingress BWP per CoS ID at a UNI Carrier Ethernet 2.0 requires to not use Ingress BWP per CoS ID at a UNI.

Egress BWP per OVC EP at a UNI Carrier Ethernet 2.0 requires to not specify Egress BWP per OVC EP at a UNI.

Egress BWP Per CoS ID at a UNI Carrier Ethernet 2.0 requires to not specify Egress BWP per CoS ID at a UNI.

E-Access - OVC Per UNI Service Attributes


✔ Enh.


20

OVC Per ENNI Service Attributes


1.0 2.0 1.0 2.0

OVC EP ID Carrier Ethernet 2.0 requires that the OVC EP ID be a string that is unique across the Operator MEN. ✔

New ✔ New

CoS ID for ENNI Frames Carrier Ethernet 2.0 requires that the CoS ID for ENNI Frames be the OVC EP to which the ENNI Frame is mapped and that the OVC have a single CoS Name which is associated with the entire set of S-Tag PCP values {0-7}.

✔ New ✔

New

Ingress BWP per OVC EP

Carrier Ethernet 2.0 requires the support of Ingress BWP per OVC EP and requires configuration to support CIR values up to 70% of the ENNI speed, in the following increments:

1 – 10 Mb/s, increments of 1 Mb/s 10 – 100 Mb/s, increments of 10 Mb/s 100 – 1000 Mb/s, increments of 100 Mb/s 1 – 10 Gb/s, increments of 1 Gb/s.

These required CIR increments are subject to the limit imposed by the UNI speed. MAY support other values of CIR. MUST allow configuration of EIR = 0, EBS = 0, CF = 0, Color Mode = “color aware”. MAY support other values of EIR, EBS, CF, and Color Mode. MUST have CBS >= 12176 bytes. MUST NOT be combined with any other type of ingress bandwidth profile.

✔ New ✔

New

Ingress BWP per ENNI CoS ID Carrier Ethernet 2.0 requires to not use Ingress BWP per ENNI CoS ID.

Egress BWP per OVC EP Carrier Ethernet 2.0 requires to not specify Egress BWP per OVC EP.

Egress BWP per ENNI CoS ID Carrier Ethernet 2.0 requires to not specify Egress BWP per ENNI CoS ID

E-Access - OVC Per ENNI Service Attributes


✔ Enh.


21

OVC Service Attributes


1.0 2.0 1.0 2.0

OVC Identifier Carrier Ethernet 2.0 requires that the OVC Identifier be a string that is unique across the Operator MEN. ✔

New ✔ New

OVC Type Carrier Ethernet 2.0 requires that the OVC Type be Point-to-Point. ✔ New ✔

New

OVC EP List Carrier Ethernet 2.0 requires that the OVC EP List contain exactly 2 OVC EPs, one OVC EP at the UNI and one at the ENNI. ✔

New ✔ New

Maximum Number of UNI OVC EP Carrier Ethernet 2.0 requires that the Maximum Number of UNI OVC EP be 1. ✔ New ✔

New

Maximum Number ENNI OVC EP Carrier Ethernet 2.0 requires that the Maximum Number of ENNI OVC EP be 1. ✔ New ✔

New

OVC MTU Size Carrier Ethernet 2.0 requires that the OVC MTU Size be an integer number of bytes greater or equal to 1526. ✔

New ✔ New

CE-VLAN ID Preservation Carrier Ethernet 2.0 requires that the CE-VLAN ID Preservation be Yes. ✔ New ✔

New

CE-VLAN CoS ID Value Preservation Carrier Ethernet 2.0 requires that the CE-VLAN CoS ID Preservation be Yes. ✔ New ✔

New

S-VLAN ID Preservation Carrier Ethernet 2.0 requires that the S-VLAN ID Preservation be not applicable for E-Access services as there is only one ENNI in the service instance.

S-VLAN CoS ID Value Preservation Carrier Ethernet 2.0 requires that the S-VLAN CoS ID Preservation be not applicable for E-Access services as there is only one ENNI in the service instance.

Color Forwarding Carrier Ethernet 2.0 requires that Color Forwarding be yes when ingress BWP at the UNI has EIR = 0, so that frames egressing at ENNI be marked green.

✔ New ✔

New

Service Level Specification Carrier Ethernet 2.0 requires that the SLS to list values/objectives for each applicable performance attribute. Applicable service performance attributes and objectives are specified in MEF 23.1.

✔ New ✔

New

Unicast, Multicast and Broadcast Frame Delivery

Carrier Ethernet 2.0 requires that Unicast, Multicast and Broadcast frames be delivered unconditionally for Access EPL and deliver unconditionally or conditionally for Access EVPL. If delivered conditionally, CE 2.0 requires to specify the delivery criteria.

✔ New ✔

New

E-Access - OVC Service Attributes


✔ Enh.


22

SOAM Frames Handling What’s new in Carrier Ethernet 2.0 Access EPL Access EVPL

1.0 2.0 1.0 2.0

Connectivity Check messages Carrier Ethernet 2.0 requires that the Access EPL and Access EVPL Services be configurable to tunnel all SOAM frames at the default Test and Subscriber MEG levels as defined in MEF 30, section 7.1.

✔ New ✔

New

Linktrace messages Carrier Ethernet 2.0 requires that the Access EPL and Access EVPL Services be configurable to tunnel all SOAM frames at the default Test and Subscriber MEG levels as defined in MEF 30, section 7.1.

✔ New ✔

New

Loopback messages Carrier Ethernet 2.0 requires that the Access EPL and Access EVPL Services be configurable to tunnel all SOAM frames at the default Test and Subscriber MEG levels as defined in MEF 30, section 7.1.

✔ New ✔

New

E-Access - Service OAM Frames Handling


✔ Enh.


23

End of Technical Foundation

More at mef.net

https://www.mef.net

Carrier Ethernet 2.0 Services - MEF...2012/06/08 · •Carrier Ethernet 2.0 EP-LAN and EVP-LAN...

Documents

Transcript of Carrier Ethernet 2.0 Services - MEF...2012/06/08 · •Carrier Ethernet 2.0 EP-LAN and EVP-LAN...