|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 33
|
|
Title:
|
Ethernet Access Services Definition
This document defines Ethernet Access Services, which are OVC-based Ethernet services in contrast to the EVC-based services which are defined in MEF 6.1 Technical Specification "Ethernet Services Definitions"[1]. This document uses the UNI service attributes and parameters options defined in the MEF 6.1 and ENNI and OVC service attributes defined in MEF 26 Technical Specification "External Network Network Interface (ENNI) - Phase 1" [8] and applies them to create new Ethernet access services between a UNI and an ENNI. These new carrier-to-carrier Ethernet access services enable Ethernet Service Providers to reach out-of-franchise customer locations through an Ethernet Access Provider's network, and deliver E-Line and E-LAN service types end to end. This document defines the UNI, OVC, OVC per UNI, OVC End Point per ENNI, and ENNI requirements for point-to-point OVC-based Ethernet services. In addition, an informative appendix is provided showing use
|
|
|
2.
|
Status of approval:
|
|
|
Approved in Januray 2012
|
|
3.
|
Justification for the specific reference:
|
|
|
The Ethernet access service definition in MEF 33 supplements 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:
|
|
|
MEF 30 is part of a set of MEF Techcnical Specifications branded as "Carrier Ethernet 2.0"
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] MEF Technical Specification MEF 6.1, "Ethernet Services Definitions - Phase 2", April, 2008./
[2] MEF Technical Specification, MEF 10.2, "Ethernet Services Attributes - Phase 2", October 2009./
[3] IEEE 802.3-2005, "Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications"/
[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", May 2004/
[7] ITU-T Recommendation Y.1731, "OAM functions and mechanisms for Ethernet based networks"/
[8] MEF Technical Specification MEF 26, "External Network to Network Interface (ENNI) - Phase 1", January 2010./
[9] MEF Technical Specification MEF 20, "User Network Interface (UNI) Type 2 Implementation Agreement," July 2008./
[10] MEF Technical Specification MEF 30, "Service OAM Fault Management Implementation Agreement," January 2011./
[11] IEEE 802.1ag-2007, "Virtual Bridged Local Area Networks Amendment 5: Connectivity Fault Management."/
[12] IEEE 802.1aj-2009. IEEE Standard for Local and metropolitan Area Networks - Virtual Bridged Local Area Networks Amendment 11: Two-Port Media Access Control (MAC) Relay. - December 2009./
[13] IEEE P802.1AB-REV/D6.0-2009. IEEE Standard for Local and metropolitan Area Networks - Station and Media Access Control Connectivity Discovery - June 2009./
[14] IEEE P802.1X-REV/D4.5 IEEE Draft Standard for Local and metropolitan Area Networks. Port-based Network Access Control. - October 2009./
[15] MEF Technical Specification MEF 26.0.2, "OVC Layer 2 Control Protocol Tunneling Amendment to MEF 26", January 2011./
[16] MEF Technical Specification MEF 23.1, "Carrier Ethernet Class of Service - Phase 2", (in progress) 2011./
[17] MEF Technical Specification MEF 26.0.3, "Service Level Specification Amendment to MEF 26", October 2011.
|
|
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
|
|
