|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 62
|
|
Title:
|
Managed Access E-Line Service Implementation Agreement
This Implementation Agreement (IA) defines an Access E-Line Service that includes a specific set of management and Class of Service capabilities. The service defined in this IA is based on applicable functionality and associated requirements from existing MEF specifications, including:
• Access E-Line Services, as defined in MEF 51 [15]
• Key Service Attributes not covered in MEF 51 [15], as specified in MEF 26.2 [11]
• General SOAM and SOAM Fault Management, as specified in MEF 30.1 [12]
• SOAM Performance Monitoring, as specified in MEF 35.1 [13]
• Latching Loopback, as specified in MEF 46 [14]
|
|
|
2.
|
Status of approval:
|
|
|
Approved in 2018
|
|
3.
|
Justification for the specific reference:
|
|
|
The Ethernet service attributes and service definitions from MEF 63 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:
|
|
|
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] IEEE Std 802.1Q – 2014, IEEE Standard for Local and metropolitan area net-works-- Bridges and Bridged Networks, December 2014./
[2] IETF RFC 2119, Key words for use in RFCs to Indicate Requirement Levels, March 1997./
[3] IETF RFC 8174, Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words, May 2017./
[4] ITU-T, Recommendation G.8013/Y.1731, Global information infrastructure, in-ternet protocol aspects and next-generation networks, Internet protocol aspects – Operation, administration and maintenance, August 2015./
[5] MEF Forum, MEF 6.2, Ethernet Services Definitions - Phase 3, July 2014./
[6] MEF Forum, MEF 10.3, Ethernet Services Attributes Phase 3, October 2013./
[7] MEF Forum, MEF 10.3.1, Composite Performance Metric (CPM) Amendment to MEF 10.3, February 2015./
[8] MEF Forum, MEF 10.3.2, Amendment to MEF 10.3 - UNI Resiliency Enhance-ment, November 2015./
[9] MEF Forum, MEF 11, User Network Interface (UNI) Requirements and Frame-work, November 2004./
[10] MEF Forum, MEF 26.1, External Network Network Interface (ENNI) – Phase 2, January 2012./
[11] MEF Forum, MEF 26.2, External Network Network Interfaces (ENNI) and Opera-tor Service Attributes, August 2016./
[12] MEF Forum, MEF 30.1, Service OAM Fault Management Implementation Agree-ment: Phase 2, April 2013./
[13] MEF Forum, MEF 35.1, Service OAM Performance Monitoring Implementation Agreement, May 2015./
[14] MEF Forum, MEF 46, Latching Loopback Protocol and Functionality, July 2014./
[15] MEF Forum, MEF 51, OVC Services Definitions, July 2015./
|
|
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
|
|
