|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 6.1.1
|
|
Title:
|
Layer 2 Control Protocol Handling Amendment to MEF 6.1, January 2012. This document replaces Section 8 of MEF 6.1
|
|
|
2.
|
Status of approval:
|
|
|
Approved in 2012.
|
|
3.
|
Justification for the specific reference:
|
|
|
The processing of layer 2 control protocols introduced in this Recommendation is defined for each of the Ethernet services in a companion set of Recommendations ITU-T G.8011.x/Y.1307.x based on MEF 6.1.1
|
|
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:
|
|
|
MEF 6.1.1 amends MEF 6.1.
MEF 10.1 is the base service attributes for the service definitions in MEF 6.1 and in MEF 6.1.1.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
The following references are from the base MEF 6.1:/
[1] MEF Technical Specification MEF 6, “Ethernet Services Definitions - Phase I”, June 2004/
[2] MEF Technical Specification, MEF 10.1, “Ethernet Services Attributes - Phase 2”, November 2006/
[3] IEEE 802.1D-2004, “Part 3: Media Access Control (MAC) Bridges”/
[4] IEEE 802.1Q – 2005, “Virtual Bridged Local Area Networks”/
[5] IEEE 802.3-2005, “Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications”/
[6] RFC 2119, “Key words for use in RFCs to Indicate Requirement Levels”, S. Bradner/
[7] IEEE 802.1X – 2004, “Port-Based Network Access Control”/
[8] IEEE 802.1AB-2005, “Station and Media Access Control, Connectivity Discovery”/
[9] MEF Technical Specification MEF 16, “Ethernet Local Management Interface”, January 2006/
[10] IEEE 802.1ad-2005, “Virtual Bridged Local Area Networks – Amendment 4: Provider Bridges”/
[11] IEEE 802.1ag-2007, “Virtual Bridged Local Area Networks – Amendment 5: Connectivity Fault Management”/
[12] MEF Technical Specification MEF 4, “Metro Ethernet Network Architecture Framework - Part 1: Generic Framework”, May 2004/
[13] ITU-T Recommendation G.8011.1/Y.1307.1, “Ethernet Private Line”/
[14] ITU-T Recommendation G.8011.2/Y.1307.2, “Ethernet Virtual Private Line Service”/
[15] ITU-T Recommendation Y.1731, “OAM functions and mechanisms for Ethernet based networks”/
[16] MEF Technical Specification MEF 17, “Service OAM Requirements & Framework – Phase 1”, April 2007/
[17] IEEE 802.1ak-2007, “Virtual Bridged Local Area Networks, Amendment 07: Multiple Registration Protocol”
|
|
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
|
