|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 12.1
|
|
Title:
|
Carrier Ethernet Network Architecture Framework Part 2: Ethernet Services Layer - Base Elements, April 2010
This document provides the architectural framework to model the Ethernet Services Layer of MEF compliant Carrier Ethernet Networks. It also introduces the base functional elements of the MEF architecture.
|
|
|
2.
|
Status of approval:
|
|
|
Approved in 2010
|
|
3.
|
Justification for the specific reference:
|
|
|
The services defined by this Recommendation do not refer to a particular network technology implementation and are supported by the Ethernet layer architecture model presented in MEF 12.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 12.1 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.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. December 2005. /
[3] IEEE Std 802.1D - 2004, IEEE Standard for Local and Metropolitan Area Networks: Media Access Control (MAC) Bridges. June 2004. /
[4] IEEE Std 802.1Q - 2005, IEEE Standards for Local and metropolitan area networks — Virtual Bridged Local Area Networks. 26 May 2006. /
[5] IEEE Std 802.1ad - 2005, IEEE Standard for Local and Metropolitan Area Networks — Virtual Bridged Local Area Networks — Amendment 4: Provider Bridges. May 2006. /
[6] IEEE Sts 802.1ag - 2007 IEEE Standard for Local and metropolitan area networks — Virtual Bridged Local Area Networks—Amendment 5: Connectivity Fault Management. December 2007. /
[7] IEEE Std 802.1ah - 2008 IEEE Standard for Local and Metropolitan Area Networks — Virtual Bridged Local Area Networks — Amendment 6: Provider Backbone Bridges. August 2008. /
[8] IEEE P802.1Qay - Provider Backbone Bridge Traffic Engineering. June 2009. /
[9] ITU-T Recommendation G.805 “Generic functional architecture of transport networks.” March 2002. /
[10] ITU-T Recommendation G.809 “Functional architecture of connectionless layer networks.” March 2003. /
[11] ITU-T Recommendation G.8010/Y.1306, “Architecture of Ethernet layer networks.” February 2004. /
[12] ITU-T Recommendation G.8021, “Characteristics of Ethernet transport network equipment functional blocks.” December 2007. /
[13] ITU-T Recommendation G.7041/Y.1303, “Generic Framing Procedure (GFP).” December 2003. /
[14] ITU-T Recommendation X.86, “Ethernet over LAPS.” February 2001. /
[15] ITU-T Recommendation Y.1731, “OAM functions and mechanisms for Ethernet based networks.” February 24 2006./
[16]ATM Forum, “LAN Emulation over ATM v1.0.” January 1995. /
[17]Metro Ethernet Forum, MEF 4, “MEN Architecture Framework – Part 1: Generic Framework.” May 2004./
[18]Metro Ethernet Forum, MEF 6, “Ethernet Services Definition, Phase1 1.” June 2004. /
[19]Metro Ethernet Forum, MEF 6.1, “Ethernet Services Definition, Phase 2.” November 2006. /
[20]Metro Ethernet Forum, MEF 10, “Ethernet Services Attributes, Phase 1.” November 2004. /
[21]Metro Ethernet Forum, MEF 10.2, “Ethernet Services Attributes, Phase 2.” April 2009. /
[22]Metro Ethernet Forum, MEF 12, “Metro Ethernet Network Architecture Framework – Part 2: Ethernet Services Layer.” April 2005. /
[23]Metro Ethernet Forum, MEF 13, “User Network Interface (UNI) Type 1.” November 2005. /
[24]Metro Ethernet Forum, MEF 17, “Service OAM Requirements and Framework – Phase I.” April 2007. /
[25]Metro Ethernet Forum, MEF 20, “User Network Interface (UNI) Type 2.” July 2008. /
[26]Metro Ethernet Forum, MEF 23, “Carrier Ethernet Class of Service”. June 2009. /
[27]Metro Ethernet Forum, MEF 26, “External Network-to-Network Interface”. January 2009. /
[28] IETF RFC 2684, “Multiprotocol Encapsulation over ATM Adaptation Layer.” September 1999. /
[29] IETF RFC 4448, “Encapsulation Methods for Transport of Ethernet over MPLS Networks.” April 2006. /
[30] IETF RFC 4761, “Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling.” January 2007. /
[31] IETF RFC 4762, “Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling.” January 2007.
|
|
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
|
|
