|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 26.1
|
|
Title:
|
External Network Network Interface (ENNI) – Phase 2 - January 2012. This Technical Specification specifies: The requirements at the ENNI reference point as well as the interface functionality in sufficient detail to ensure interoperability between two Operator MENs including Link OAM. The connectivity attributes UNI to UNI, UNI to ENNI, and ENNI to ENNI such that multiple Operator MENs can be interconnected and the Ethernet Services and attributes in MEF 6.1 and MEF 10.2 can be realized.
|
|
|
2.
|
Status of approval:
|
|
|
Approved in 2012
|
|
3.
|
Justification for the specific reference:
|
|
|
referenced in Table 15-1C to illustrate relationship with Ethernet Connection types specified in G.8012.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 26.1 is part of a set of MEF Techcnical Specifications branded as "Carrier Etherent 2.0" -- see http://metroethernetforum.org/page_loader.php?p_id=2031
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] Metro Ethernet Forum, MEF 4, Metro Ethernet Network Architecture Framework– Part 1: Generic Framework, May 2004./
[2] S. Bradner, RFC 2119, Key words for use in RFCs to Indicate Requirement Levels, March 1997./
[3] IEEE Std 802.3 – 2005, Information technology – Telecommunications and information exchange between systems – Local and metropolitan area networks –/
Specific requirements – Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications, 9 December 2005./
[4] IEEE Std 802.1ad – 2005, IEEE Standard for Local and metropolitan Area Networks – Virtual Bridged Local Area Networks Amendment 4: Provider Bridges,/
May 2006./
[5] Metro Ethernet Forum, MEF 10.2, Ethernet Services Attributes Phase 2, October 2009./
[6] International Telecommunication Union, Recommendation Y.1731, OAM functions and mechanisms for Ethernet based Networks, February 2008./
External Network Network Interface (ENNI) – Phase 2/
[7] Metro Ethernet Forum, MEF 11, User Network Interface (UNI) Requirements and Framework, November 2004./
[8] Metro Ethernet Forum, MEF 20, User Network Interface (UNI) Type 2 Implementation Agreement, July 2008./
[9] Metro Ethernet Forum, MEF 6.1, Ethernet Services Definitions - Phase 2, April 2008./
[10] Metro Ethernet Forum, MEF 23.1, Carrier Ethernet Class of Service – Phase 2, January 2012./
[11] Metro Ethernet Forum, MEF 17, Metro Ethernet Forum, Service OAM Requirements & Framework – Phase 1, April 2007./
[12] IEEE Std 802.1ag – 2007, IEEE Standard for Local and metropolitan Area Networks – Virtual Bridged Local Area Networks Amendment 5: Connectivity Fault/
Management, December 2007./
[13] Metro Ethernet Forum, MEF 2, Metro Ethernet Forum, Requirements and Framework for Ethernet Service Protection in Metro Ethernet Networks, February/
2004./
[14] K. Nichols, S. Blake, F. Baker, and D. Black, RFC2474, Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers, December 1998./
[15] IEEE Std 802.1ah – 2008, IEEE Standard for Local and metropolitan Area Networks – Virtual Bridged Local Area Networks Amendment 7: Provider Backbone/
Bridges, August 2008./
[16] Metro Ethernet Forum, MEF 26, External Network Network Interface (ENNI) – Phase 1, January 2010./
[17] Metro Ethernet Forum, MEF 26.0.1, Corrected Figure 10 for MEF 26, July 2010./
[18] Metro Ethernet Forum, MEF 26.0.2, OVC Layer 2 Control Protocol Tunneling Amendment to MEF 26, July 2011./
[19] Metro Ethernet Forum, MEF 26.0.3, Service Level Specification Amendment to MEF 26, October 2011./
[20] Metro Ethernet Forum, MEF 28, External Network Network Interface (ENNI) Support for UNI Tunnel Access and Virtual UNI, October 2010./
[21] IEEE Std 802.1Q – 2011, IEEE Standard for Local and metropolitan area networks-- Media Access Control (MAC) Bridges and Virtual Bridged Local Area/
Networks, 2011./
[22] Metro Ethernet Forum, MEF 10.2.1, Performance Attributes Amendment to MEF 10.2, January 2011./
[23] International Telecommunication Union, Recommendation Y.1563, Global information infrastructure, internet protocol aspects and next-generation networks,/
Internet protocol aspects – Quality of service and network performance, Ethernet frame transfer and availability performance, 2009.
|
|
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
|
|
