|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 35
|
|
Title:
|
Service OAM Performance Monitoring Implementation Agreement, April 2012. This document specifies an Implementation Agreement (IA) for Service Operations, Administration, and Maintenance (SOAM) that satisfies and extends the Performance Monitoring (PM) framework and requirements described in MEF 17. Existing PM functions are defined by ITU-T Y.1731.
|
|
|
2.
|
Status of approval:
|
|
|
Approved in 2012
|
|
3.
|
Justification for the specific reference:
|
|
|
The Ethernet service OAM definitions in MEF 35 complement ITU-T G.8013 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 35 is part of a set of MEF Techcnical Specifications branded as "Carrier Ethernet 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] International Telecommunication Union, Recommendation Y.1731 Revision 1 (02/2011), "OAM functions and mechanisms for Ethernet based Networks"./
[2] International Telecommunication Union, Recommendation Y.1563 (01/2009), "Ethernet frame transfer and availability performance"./
[3] International Telecommunication Union, Recommendation G.8010 (02/2004), “Architecture of Ethernet layer networks”./
[4] International Telecommunication Union, Recommendation G.8021 (10/2010), "Characteristics of Ethernet transport network equipment functional blocks"./
[5] International Telecommunication Union, Recommendation G.8021 Amendment 1 (02/2011), “Characteristics of Ethernet transport network equipment functional blocks”./
[6] International Telecommunication Union, Recommendation G.7710 (07/2007), "Common Equipment Management Function Requirements"./
[7] International Telecommunication Union, Recommendation M.3400 (02/2000), “TMN management functions”./
[8] Bradner, S., Key words for use in RFCs to Indicate Requirement Levels, RFC 2119, March 1997. (Normative)/
[9] MEF Technical Specification MEF 4, "Metro Ethernet Network Architecture Framework - Part 1: Generic Framework", May 2004./
[10] MEF Technical Specification MEF 6.1, "Ethernet Services Definitions - Phase 2", April 2008./
[11] MEF Technical Specification MEF 7.1, "EMS-NMS Information Model Phase 2", October 2009./
[12] MEF Technical Specification MEF 10.2, "Ethernet Services Attributes Phase 2", October 2009./
[13] MEF Technical Specification MEF 10.2.1, “Performance Attributes Amendment to MEF 10.2”, January 2011./
[14] MEF Technical Specification MEF 12.1, “Carrier Ethernet Network Architecture Framework, Part 2: Ethernet Services Layer – Base Elements”, April 2010./
[15] MEF Technical Specification MEF 15, "Requirements for Management of Metro Ethernet Phase 1 Network Elements", November 2005./
[16] MEF Technical Specification MEF 17, "Service OAM Requirements & Framework - Phase 1", April 2007./
[17] MEF Technical Specification MEF 20, "User Network Interface (UNI) Type 2 Implementation Agreement", July 2008./
[18] MEF Technical Specification MEF 23, "Carrier Ethernet Class of Service - Phase 1", June 2009./
[19] MEF Technical Specification MEF 23.1, “Carrier Ethernet Class of Service – Phase 2”, January 2012./
[20] MEF Technical Specification MEF 26, "External Network Network Interface (ENNI) - Phase 1", January 2010./
[21] MEF Technical Specification MEF 26.0.3, “Service Level Specification amendment to MEF 26”, October 2011./
[22] MEF Technical Specification MEF 30, "Service OAM Fault Management Implementation Agreement", January 2011./
[23] IEEE 802-2001, “IEEE Standard for Local and Metropolitan Area Networks: Overview and Architecture”, 2001/
[24] IEEE 802.1Q-2011, "Virtual Bridged Local Area Networks", 2011/
[25] ISO 8601, "Data elements and interchange formats - Information interchange - Representation of dates and times", Third Edition, December 1, 2004./
[26] RFC 5951, "Network Management Requirements for MPLS-based Transport Networks", September 2010.
|
|
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
|
|
