Date: Fri, 29 Mar 2024 06:25:07 +0000 (UTC) Message-ID: <1195384577.13133.1711693507031@wiki.mef.net> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_13132_2008573709.1711693507030" ------=_Part_13132_2008573709.1711693507030 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Carrier Ethernet Service Framework has two componen= ts:
MEF10.x defines three sets of generic attributes:
UNI Attributes (MEF 10.3) are characteristics of the User Network Interface (UNI) itself a= nd are applied to all services on the UNI.
Example
Physical Layer Service Attribute
If the UNI is a 100Mbps Full Duplex Ethernet, then that is what th= e services see.
EVC per UNI Attribu= tes (MEF 10.2 and MEF 10.3) are EVC<= /a> attributes that are associated with the specific UNI and can be differe= nt on other UNIs within the EVC.
Example
Ingress Bandwidth Profile Attribute
Each UNI in an EVC can have different policing values.
EVC Attributes are attribut= es that describe the EVC itself. They apply to the EVC across the entire ca= rrier network.
Example
EVC Connection Type Attribute
If the EVC is defined as point-to-point, then it must be that way = across the whole network.
MEF 6.x defines six C= arrier Ethernet Service types, three private service types and three vi= rtual private service types, by constraining the values in each of the thre= e sets of generic attributes to an appropriate set of values.
Example
An Ethernet Private Line service must have (note that these are just a s= ample, there are several other attributes):
DRAFT<= /p>