MEF CE 2.0 Document

Carrier Ethernet 2.
0 Services
Technical Foundation Document
A Comparison of Services Attributes for CE 1.0 and CE 2.0 by Service Type
Version 2
June 2012
Document Editor, Isabelle Morency, Iometrix

1
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
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
Whats new in Carrier Ethernet 2.0
EPL
1.0
2.0
Attribute 1
Carrier Ethernet 2.0 requires Attribute 1 to be
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
Enh.
Enh.
EVPL
1.0
2.0
Enh.
New
New attribute introduced in CE 2.0

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
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

EVPL Services
UNI
UNI
UNI
UNI
CE
CE
Carrier Ethernet Network
CE
CE
CE
UNI
E-Line - UNI Service Attributes

UNI
Service Attributes
UNI Identifier
Physical Medium
Speed and Mode
MAC Layer

Carrier Ethernet 1.0 and 2.0 require that the UNI Identifier be an arbitrary text string to
identify the UNI.
Carrier Ethernet 2.0 requires the UNI Physical Medium to be one of the PHYs listed in IEEE
802.3-2005, except PON interfaces.
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.
Carrier Ethernet 2.0 requires the MAC Layer to be IEEE 802.3-2005.
EPL
1.0
2.0
Enh.
Enh.
EVPL
1.0 2.0
Enh.
Enh.
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.
If Service Multiplexing is supported, Carrier Ethernet 2.0 requires the support of a
Service Multiplexing
minimum number of EVCs based on the UNI Speed per UNI Type 1 IA.
If Bundling is supported, Carrier Ethernet 2.0 requires the support of a minimum number
Bundling
of CE-VLAN IDs based on the UNI Speed per UNI Type 1 IA.
If All to One Bundling is supported, Carrier Ethernet 2.0 requires that it only applies to Port
All to One Bundling
based services such as EPL.
Carrier Ethernet 1.0 and 2.0 require that all untagged and priority tagged Service Frames
CE-VLAN ID for untagged and
at the UNI map to the same EVC as is used for all other Service Frames for EPL and
priority tagged Service
requires to specify the CE-VLAN ID for untagged and priority tagged Service Frames in the
Frames
range of 1-4094 for EVPL.
Carrier Ethernet 2.0 requires that the maximum number of EVCs per UNI be 1 for EPL and
Maximum Number of EVCs
be greater or equal to 1 for EVPL.
If ingress BWP per UNI is supported, Carrier Ethernet 2.0 requires configuration
Ingress BWP per UNI
granularities per UNI Type 1 IA.
Egress BWP per UNI is a new attribute of Carrier Ethernet 2.0. If egress BWP per UNI is
Egress BWP per UNI
supported, CE 2.0 requires requires configuration granularities per UNI Type 2 IA.
New
Enh.
L2CP Processing
UNI MTU Size
Carrier Ethernet 2.0 requires that L2CP processing be as specified in MEF 6.1.1.
New New attribute introduced in CE 2.0

Attribute introduced in CE 1.0 and enhanced in CE
Enh. 2.0
Enh.
Enh.
Enh.
New
Enh.
Enh.
Enh.
Enh.
New
Enh.
E-Line - EVC per UNI Service Attributes and SOAM Frames Handling
EVC per UNI
Service Attributes
Egress BWP Per EVC
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.
Carrier Ethernet 2.0 requires that all Service Frames at the UNI map to a single pointto-point EVC for EPL and to specify mapping table of CE-VLAN IDs to EVC ID for EVPL.
If ingress BWP per EVC is supported, Carrier Ethernet 2.0 requires configuration
If ingress BWP per CoS ID is supported, Carrier Ethernet 2.0 requires configuration
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.
UNI EVC ID
CE-VLAN ID / EVC Map
Ingress BWP Per EVC
Ingress BWP Per CoS ID
SOAM Frames Handling
Carrier Ethernet 2.0 requires that all CCM frames at the default Test and Subscriber
MEG levels be tunneled.
Where at least one MIP is configured at the default Test or Subscriber MEG level,
Linktrace messages with at least one
Carrier Ethernet 2.0 requires that Linktrace frames with the corresponding target MAC
MIP configured
DA and MEG level be peered or discarded.
Where no MIPs are configured at the default Test or Subscriber MEG level, Carrier
Linktrace messages without any MIPs
Ethernet 2.0 requires that Linktrace frames with the corresponding target MAC DA and
configured
MEG level be tunneled.
Unicast Loopback messages with at
Carrier Ethernet 2.0 requires that Loopback frames with the corresponding target
least one MIP configured
unicast MAC DA and MEG level be peered or discarded.
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.
Carrier Ethernet 2.0 requires that all multicast Loopback frames at the default Test and
Multicast Loopback messages
Subscriber MEG levels be tunneled.
Connectivity Check messages

Enh. 2.0
EPL
EVPL
1.0
2.0
1.0
2.0
Enh.
Enh.
Enh.
Enh.
Enh.
Enh.
1.0
2.0
1.0
2.0
New
New
New
New
New
New
New
New
New
New
New
New
E-Line - EVC Service Attributes

EVC
Service Attributes
EPL
1.0
2.0
EVPL
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
CE-VLAN CoS Preservation
Unicast, Multicast and Broadcast

Service Frame Delivery
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.
Carrier Ethernet 2.0 requires that CE-VLAN CoS Preservation be Yes for EPL and
be either Yes or No for EVPL.
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.
L2CP Processing
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. 2.0
Enh.
Enh.
Enh.
Enh.
Enh.
Enh.
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.
EP-LAN Service

EVP-LAN Service
Internet
UNI
ISP POP
UNI
CE
UNI
CE
UNI
CE
CE
UNI
CE
UNI
CE
E-LAN - UNI Service Attributes

UNI
Service Attributes
UNI Identifier
Physical Medium
Speed and Mode
MAC Layer

Carrier Ethernet 1.0 and 2.0 require that the UNI Identifier be an arbitrary text string to
identify the UNI.
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.
EP-LAN
EVP-LAN
1.0
2.0
1.0
2.0
Enh.
Enh.
Enh.
Enh.
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.
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.
If Bundling is supported, Carrier Ethernet 2.0 requires the support of a minimum number of
Bundling
CE-VLAN IDs based on the UNI Speed per UNI Type 1 IA.
All to One Bundling
based services such as EP-LAN.
Carrier Ethernet 1.0 and 2.0 require that all untagged and priority tagged Service Frames at
CE-VLAN ID for untagged and
the UNI map to the same EVC as is used for all other Service Frames for EP-LAN and requires
priority tagged Service
to specify the CE-VLAN ID for untagged and priority tagged Service Frames in the range of 1Frames
4094 for EVP-LAN.
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.
If ingress BWP per UNI is supported, Carrier Ethernet 2.0 requires configuration granularities
Ingress BWP per UNI
per UNI Type 1 IA.
Egress BWP per UNI
New
Enh.
L2CP Processing
UNI MTU Size

Enh. 2.0
Enh.
Enh.
New
Enh.
New
Enh.
Enh.
Enh.
Enh.
New
Enh.
E-LAN - EVC per UNI Service Attributes and SOAM Frames Handling
EVC per UNI
Service Attributes
UNI EVC ID
Ingress BWP Per EVC
Egress BWP Per EVC

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.
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.
Egress BWP per EVC is a new attribute of Carrier Ethernet 2.0. If egress BWP per EVC is
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.
EP-LAN
EVP-LAN
1.0
2.0
1.0
2.0
Enh.
Enh.
Enh.
New
1.0
Enh.
Enh.
New
New
New
2.0
1.0
2.0
New

New
MIP configured
New
configured
New

New


New

Enh. 2.0
Enh.
New
New
New
New
New
New
10
E-LAN - EVC Service Attributes

EVC
Service Attributes
EP-LAN
EVP-LAN
1.0
2.0
1.0
2.0
EVC Type
Carrier Ethernet 1.0 and 2.0 require that the EVC Type be multipoint-tomultipoint.
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.
Carrier Ethernet 1.0 and 2.0 require that the Maximum Number of UNIs be
greater or equal to 2.
EVC MTU Size
New
New
Carrier Ethernet 1.0 and 2.0 require that CE-VLAN ID Preservation be Yes for EPLAN and be either Yes or No for EVP-LAN.
Carrier Ethernet 2.0 requires that CE-VLAN CoS Preservation be Yes for EP-LAN
and be either Yes or No for EVP-LAN.

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.
L2CP Processing
EVC Performance
values/objectives for each applicable performance attribute. MEF 23.1 does
not specify performance objectives for multipoint-to-multipoint services.

Enh. 2.0
Enh.
Enh.
Enh.
Enh.
11
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.
EP-Tree Service
UNI
UNI

EVP-Tree Service
CE
CE
Root
Root
Leaf
CE
Root
UNI
Leaf
Leaf
UNI
CE
UNI
CE
Leaf
Leaf
UNI
Leaf
UNI
CE
UNI
CE
CE
12
E-Tree - UNI Service Attributes

UNI
Service Attributes
UNI Identifier
Physical Medium
Speed and Mode
MAC Layer
UNI MTU Size
Bundling
All to One Bundling
1.0
2.0
Carrier Ethernet 2.0 requires that the UNI Identifier be an arbitrary text string to identify the
UNI.
Carrier Ethernet 2.0 requires the UNI Speed to be 10 Mbps, 100 Mbps, 10/100 Mbps Autoneg, 10/100/1000 Auto-neg, 1 Gbps or 10 Gbps in Full Duplex mode.
New
New
New
New
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.
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.
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.
based services such as EP-LAN.
Carrier Ethernet 2.0 requires that all untagged and priority tagged Service Frames at the UNI
CE-VLAN ID for untagged and map to the same EVC as is used for all other Service Frames for EP-Tree and requires to
priority tagged Service Frames specify the CE-VLAN ID for untagged and priority tagged Service Frames in the range of 14094 for EVP-Tree.
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.
If ingress BWP per UNI is supported, Carrier Ethernet 2.0 requires configuration granularities
Ingress BWP per UNI
per UNI Type 1 IA.
Egress BWP per UNI
L2CP Processing
EP-Tree

Enh. 2.0
EVP-Tree
1.0
2.0
New
New
New
New
New
New
new
new
New
New
New
New
New
New
New
New
New
New
New
13
E-Tree - EVC per UNI Service Attributes and SOAM Frames Handling
EVC per UNI
Service Attributes
UNI EVC ID
Ingress BWP Per EVC
Egress BWP Per EVC
EP-Tree
EVP-Tree
1.0
2.0
1.0
2.0
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.
Carrier Ethernet 2.0 requires that all Service Frames at the UNI map to a single rootedmultipoint EVC for EP-Tree and to specify mapping table for EVP-Tree.
Egress BWP per EVC is a new attribute of Carrier Ethernet 2.0. If egress BWP per EVC is
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
New
New
New
New
New
New
New
New
New
New
1.0
2.0
1.0
2.0
New

New
MIP configured
New
configured
New

New


New

Enh. 2.0
New
New
New
New
New
New
14
E-Tree - EVC Service Attributes

EVC
Service Attributes
EP-Tree
1.0
2.0
Carrier Ethernet 2.0 requires that the EVC Type be rooted-multipoint.
New
Carrier Ethernet 2.0 requires that the EVC ID be an arbitrary string, unique
across the MEN, for the EVC supporting the service instance.
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
Carrier Ethernet 2.0 requires that the Maximum Number of UNIs be greater or
equal to 2.
New
EVC MTU Size
New
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
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

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
L2CP Processing
New
EVC Performance
values/objectives for each applicable performance attribute. MEF 23.1 does
not specify performance objectives for rooted-multipoint services.
New
EVC Type
EVC ID
UNI List

Enh. 2.0
EVP-Tree
1.0
2.0
New
New
New
New
New
New
New
New
New
New
15
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.
Access EPL Service

Access EVPL Service
Carrier Ethernet
UNI
Access Service Provider
Carrier Ethernet
UNI
Access Service Provider
End-User
End-User
ENNI
ENNI
UNI
Retail
Service
Provider
Retail
Service
Provider
UNI
End-User
End-User
Access EPL
Access EVPL
16
E-Access - UNI Service Attributes

UNI
Service Attributes
Access EPL
1.0
2.0
UNI Identifier
Carrier Ethernet 2.0 requires the UNI ID to be any string.
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
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
MAC Layer
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
CE-VLAN ID for untagged and priority
and priority tagged frames are to be supported for Access EVPL and if supported,
tagged Service Frames
the CE-VLAN ID for untagged and priority tagged Service Frames is to be included
in the OVC Endpoint Map.
New
Access EVPL
1.0
2.0
New
New
New
New
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.

Enh. 2.0
17
E-Access - ENNI Service Attributes

ENNI
Service Attributes
Operator ENNI Identifier

Carrier Ethernet 2.0 requires that the Operator ENNI Identifier be a string that is
unique across the Operator MEN.
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.
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.
Physical Layer
Frame Format
Access EPL
1.0
2.0
New
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
Protection Mechanism
Carrier Ethernet 2.0 requires that the protection mechanism be Link Aggregation,
none, or other.
New
ENNI MTU Size
Carrier Ethernet 2.0 requires that the ENNI MTU Size be an integer number of bytes
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
Maximum Number of OVCs
Carrier Ethernet 2.0 requires that the Maximum Number of OVCs be an integer
New
New
Maximum Number of OVC End Points Carrier Ethernet 2.0 requires that the Maximum Number of OVC EPs be an integer
per OVC

Enh. 2.0
Access EVPL
1.0
2.0
New
New
New
New
New
New
New
New
New
18
E-Access - OVC Per UNI Service Attributes

OVC Per UNI
Service Attributes
Access EPL
1.0
2.0
Access EVPL
1.0
2.0
New
New
New
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
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
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
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
1 10 Gb/s, increments of 1 Gb/s
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.
Ingress BWP per OVC EP at a

UNI
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.
Egress BWP Per CoS ID at a UNI Carrier Ethernet 2.0 requires to not specify Egress BWP per CoS ID at a UNI.

Enh. 2.0
19
E-Access - OVC Per ENNI Service Attributes

OVC Per ENNI
Service Attributes
Access EPL
1.0
2.0
Access EVPL
1.0
2.0
New
New
OVC EP ID
Carrier Ethernet 2.0 requires that the OVC EP ID be a string that is unique across the
Operator MEN.
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
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 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.
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

Enh. 2.0
20
E-Access - OVC Service Attributes

OVC
Service Attributes
Access EPL
1.0
2.0
Access EVPL
1.0
2.0
New
New
New
New
New
New
New
OVC Identifier
Carrier Ethernet 2.0 requires that the OVC Identifier be a string that is unique across
the Operator MEN.
New
OVC Type
Carrier Ethernet 2.0 requires that the OVC Type be Point-to-Point.
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
Maximum Number of UNI OVC EP
Carrier Ethernet 2.0 requires that the Maximum Number of UNI OVC EP be 1.
New
Maximum Number ENNI OVC EP
Carrier Ethernet 2.0 requires that the Maximum Number of ENNI OVC EP be 1.
New
OVC MTU Size
Carrier Ethernet 2.0 requires that the OVC MTU Size be an integer number of bytes
New
Carrier Ethernet 2.0 requires that the CE-VLAN ID Preservation be Yes.
New
CE-VLAN CoS ID Value Preservation
Carrier Ethernet 2.0 requires that the CE-VLAN CoS ID Preservation be Yes.
New
New
Carrier Ethernet 2.0 requires that the S-VLAN ID Preservation be not applicable for EAccess services as there is only one ENNI in the service instance.
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.
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.
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.
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
New
New
New
New
S-VLAN ID Preservation
S-VLAN CoS ID Value Preservation

Color Forwarding
Service Level Specification
Frame Delivery

Enh. 2.0
21
E-Access - Service OAM Frames Handling

Access EPL
1.0
2.0
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
Linktrace messages
New
Loopback messages
New

Enh. 2.0
Access EVPL
1.0
2.0
New
New
New
22
End of Technical Foundation

More at mef.net
23

MEF CE 2.0 Document

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

MEF CE 2.0 Document

Încărcat de

Drepturi de autor:

Formate disponibile

Carrier Ethernet 2.

Document Editor, Isabelle Morency, Iometrix

Carrier Ethernet 2.0 Services Highlights

Carrier Ethernet 2.0 Services

Whats new in Carrier Ethernet 2.0

Carrier Ethernet 2.0 requires Attribute 1 to be

Carrier Ethernet 1.0 and 2.0 require Attribute 2 to support

Carrier Ethernet 2.0 requires Attribute 3 to be configurable as per

New attribute introduced in CE 2.0

Carrier Ethernet 2.0 E-Line Service Type

Carrier Ethernet 2.0

Carrier Ethernet Network

Carrier Ethernet Network

E-Line - UNI Service Attributes

Whats new in Carrier Ethernet 2.0

UNI MTU Size

New New attribute introduced in CE 2.0

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

Attribute not specified

Whats new in Carrier Ethernet 2.0

Egress BWP Per EVC

Egress BWP Per CoS ID

SOAM Frames Handling

Whats new in Carrier Ethernet 2.0

New New attribute introduced in CE 2.0

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

Attribute not specified

E-Line - EVC Service Attributes

Whats new in Carrier Ethernet 2.0

Maximum Number of UNIs

EVC MTU Size

Unicast, Multicast and Broadcast

New New attribute introduced in CE 2.0

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

Attribute not specified

Carrier Ethernet 2.0 E-LAN Service Type

Carrier Ethernet 2.0

Carrier Ethernet Network

E-LAN - UNI Service Attributes

Whats new in Carrier Ethernet 2.0

UNI MTU Size

New New attribute introduced in CE 2.0

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

Attribute not specified

SOAM Frames Handling

Whats new in Carrier Ethernet 2.0

Whats new in Carrier Ethernet 2.0

MEG levels be tunneled.

least one MIP configured

least one MIP configured

Multicast Loopback messages

Subscriber MEG levels be tunneled.

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

E-LAN - EVC Service Attributes

Whats new in Carrier Ethernet 2.0

Maximum Number of UNIs

EVC MTU Size

CE-VLAN CoS Preservation

Unicast, Multicast and Broadcast

New New attribute introduced in CE 2.0

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

Attribute not specified

Carrier Ethernet 2.0 E-Tree Service Type