|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 23.1
|
|
Title:
|
MEF 23.1 Carrier Ethernet Class of Service – Phase 2
This Implementation Agreement (IA) specifies a set of Class of Service Names called CoS
Labels that can be used by Operators, Service Providers and their Subscribers to indicate the
performance expectations to be associated with a given set of frames that comprise a CoS Frame
Set. This CoS IA includes standards for CoS and Color identification as well as performance
objectives and supporting requirements. The CoS Labels are envisioned as a subset of all of the
Class of Service Names an Operator may provide. The MEF CoS IA facilitates: Ethernet service
interoperability and consistency between Operators, use of a common CoS Label set for
Subscribers to utilize and use of performance objectives that support key applications. The terms
CoS Label, CoS Name, CoS Frame Set and others are defined in Section 2 of this IA.
|
|
|
2.
|
Status of approval:
|
|
|
Approved in 2012
|
|
3.
|
Justification for the specific reference:
|
|
|
The Ethernet class of service definitions in MEF 23.1 supplement MEF 6.2 to form the basis of this Recommendation.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
No known issues.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Commonly referenced all over the world for metro Ethernet services.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Commonly referenced all over the world for metro Ethernet services.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] MEF Technical Specification MEF 6.1, “Ethernet Services Definitions - Phase 2”/
[2] MEF Technical Specification, MEF 10.2, “Ethernet Services Attributes - Phase 2” and/
MEF 10.2.1, “Performance Attributes Amendment to MEF 10.2”/
[3] IEEE 802.1Q – 2005, “Virtual Bridged Local Area Networks”/
[4] RFC 2119, “Key words for use in RFCs to Indicate Requirement Levels”, S. Bradner/
[5] IEEE 802.1ad-2005, “Virtual Bridged Local Area Networks – Amendment 4: Provider/
Bridges”/
[6] MEF Technical Specification MEF 4, “Metro Ethernet Network Architecture Framework -/
Part 1: Generic Framework”/
[7] Inter-provider Quality of Service, MIT Communications Futures Program, 2006/
[8] ITU-T Recommendation Y.1541, “Network performance objectives for IP-based services”/
[9] MEF Technical Specification MEF 3, “Circuit Emulation Service Definitions, Framework/
and Requirements in Metro Ethernet Networks”/
[10] RFC 2597, “Assured Forwarding PHB Group”, Heinanen/
[11] ITU-T Recommendation I.356, “B-ISDN ATM layer cell transfer performance,” March/
2000/
[12] MEF Technical Specification MEF 13, “UNI Type 1 Implementation Agreement”/
[13] MEF Technical Specification MEF 26.1, “ENNI Phase 2”/
[14] MEF Technical Specification MEF 28, “ENNI Support of UNI Tunnel Access and Virtual/
UNI (VUNI)”/
[15] ITU-T Recommendation Y.1540, “Internet protocol data communication service – IP/
packet transfer and availability performance parameters”/
[16] MEF Technical Specification MEF 6.1.1, “Layer 2 Control Protocol Handling Amendment/
to MEF 6.1”/
[17] MEF Technical Specification MEF 12.1, “Carrier Ethernet Network Architecture/
Framework Part 2: Ethernet Services Layer - Basic Elements”/
[18] ITU-T Recommendation Y.1563, “Ethernet frame transfer and availability performance”/
[19] MEF Technical Specification MEF 23, “Carrier Ethernet Class of Service – Phase 1”/
[20] MEF Technical Specification MEF 26.0.2, “OVC Layer 2 Control Protocol Tunneling/
Amendment to MEF 26”
|
|
9.
|
Qualification of
MEF:
|
|
|
The MEF was recognized under the provisions of ITU-T Recommendation A.5 on 24 September 2002. Qualifying information is on file with TSB.
9.5 The IPR policy of the MEF may be found in Article 10 of the MEF Bylaws which are available on the MEF public WEB site metroethernetforum.org.
9.6 All MEF Technical Specifications, Implementation Agreements, and Test Specifications are approved by an electronic letter ballot of all MEF members. For a MEF document to pass an electronic letter ballot at least a quorum of members (defined by the MEF bylaws as 1/3 of the MEF membership) must vote Yes or No. In addition, of the Yes plus No votes at least 75% of the votes must be Yes.
9.7 All published MEF documents are available for download free of charge in PDF or WORD format from the MEF public WEB site www.metroethernetforum.org .
9.8 Each revision of a given MEF document has a different MEF number.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
