|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 12.2
|
|
Title:
|
Carrier Ethernet Network Architecture Framework Part 2: Ethernet Services Layer - Base Elements, May 2014
This document provides the architecture framework to model the Ethernet Services Layer of MEF compliant Carrier
Ethernet Networks. The Ethernet Service Layer architecture framework describes the high-level topological and
functional constructs used to model the various architectural components of the Ethernet Service Subscriber and
Provider networks, their associated functional elements, and their interconnect relationships. The architecture
framework also describes the relationship between Ethernet Services Layer interfaces, functional elements and their
reference points, and other architectural elements in the Transport Layer (TRAN) and Application (APP) Layers of
the MEF Generic Architecture Framework (MEF 4 [13]).
|
|
|
2.
|
Status of approval:
|
|
|
Approved in 2014
|
|
3.
|
Justification for the specific reference:
|
|
|
The Ethernet service architecture in MEF 12.2 complements ITU-T G.8010 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:
|
|
|
MEF 12.2 is the baseline architecture that ties together most MEF Technical Specifications
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] IETF RFC 2119, "Key words for use in RFCs to Indicate Requirement Levels." March 1997./
[2] IEEE Std 802.3TM – 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. December 2005./
[3] IEEE Std 802.1DTM - 2004, IEEE Standard for Local and Metropolitan Area Networks: Media Access Control/
(MAC) Bridges. June 2004./
[4] IEEE Std 802.1QTM - 2011, IEEE Standard for Local and metropolitan area networks — Media Access Control/
(MAC) Bridges and Virtual Bridge Local Area Networks. 31 August 2011./
[5] ITU-T Recommendation G.805 “Generic functional architecture of transport networks.” March 2002./
[6] ITU-T Recommendation G.809 “Functional architecture of connectionless layer networks.” March 2003./
[7] ITU-T Recommendation G.8010/Y.1306, “Architecture of Ethernet layer networks.” February 2004./
[8] ITU-T Recommendation G.8021, “Characteristics of Ethernet transport network equipment functional blocks.”/
December 2007./
[9] ITU-T Recommendation G.7041/Y.1303, “Generic Framing Procedure (GFP).” December 2003./
[10] ITU-T Recommendation X.86, “Ethernet over LAPS.” February 2001./
[11] ITU-T Recommendation Y.1731, “OAM functions and mechanisms for Ethernet based networks.” February/
2006./
[12] ATM Forum, “LAN Emulation over ATM v1.0.” January 1995./
[13] Metro Ethernet Forum, MEF 4, “MEN Architecture Framework – Part 1: Generic Framework.” May 2004./
[14] Metro Ethernet Forum, MEF 6.1, “Ethernet Services Definition, Phase 2.” November 2006./
[15] Metro Ethernet Forum, MEF 6.1.1, “Layer 2 Control Protocol Handling Amendment to MEF 6.1.” January/
2012./
[16] Metro Ethernet Forum, MEF 10.3, “Ethernet Services Attributes, Phase 3.” October 2013./
[17] Metro Ethernet Forum, MEF 12, “Metro Ethernet Network Architecture Framework – Part 2: Ethernet Services/
Layer.” April 2005./
[18] Metro Ethernet Forum, MEF 12.1, “Metro Ethernet Network Architecture Framework – Part 2: Ethernet Services/
Layer – Base Elements.” April 2010./
[19] Metro Ethernet Forum, MEF 12.1.1, “Carrier Ethernet Network Architecture Framework - Part 2: Ethernet/
Services Layer - External Interface Extensions.” October 2011./
[20] Metro Ethernet Forum, MEF 13, “User Network Interface (UNI) Type 1.” November 2005./
[21] Metro Ethernet Forum, MEF 17, “Service OAM Requirements and Framework – Phase I.” April 2007./
[22] Metro Ethernet Forum, MEF 20, “User Network Interface (UNI) Type 2.” July 2008./
[23] Metro Ethernet Forum, MEF 23, “Carrier Ethernet Class of Service”. June 2009./
[24] Metro Ethernet Forum, MEF 26.1, “External Network-to-Network Interface (ENNI) – Phase 2.” January 2012./
[25] Metro Ethernet Forum, MEF 28, “External Network-Network Interface (ENNI) Support for UNI Tunnel Access/
and Virtual UNI.” October 2010./
[26] Metro Ethernet Forum, MEF 30.1, “Service OAM Fault Management Implementation Agreement.” April/
2013./
[27] Metro Ethernet Forum, MEF 33, “Ethernet Access Services Definition.” January, 2012./
[28] Metro Ethernet Forum, MEF 43, “Virtual NID (vNID) Functionality for E-Access Services.” April 2014./
[29] IETF RFC 2684, “Multiprotocol Encapsulation over ATM Adaptation Layer.” September 1999./
[30] IETF RFC 4448, “Encapsulation Methods for Transport of Ethernet over MPLS Networks.” April 2006./
[31] IETF RFC 4761, “Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling.” January/
2007./
[32] IETF RFC 4762, “Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling.”/
January 2007./
[33] IEEE Std 802-2001, IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture./
February 2002./
[34] ISO/IEC 8802-2: 1998, Information technology -- Telecommunications and information exchange between/
systems -- Local and metropolitan area networks -- Specific requirements -- Part 2: Logical link control.
|
|
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
|
|
