|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 35.1
|
|
Title:
|
Service OAM Performance Monitoring Implementation Agreement
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 G.8013/Y.1731, and ITU-T G.8021 as
amended. This document details how to use these functions in order to achieve the requirements
of MEF SOAM PM.
|
|
|
2.
|
Status of approval:
|
|
|
Approved in 2015
|
|
3.
|
Justification for the specific reference:
|
|
|
The Ethernet service OAM definitions in MEF 35.1 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:
|
|
|
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] International Telecommunication Union, Recommendation G.8013/Y.1731 (11/2013),/
"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.8021 (05/2012), "Characteristics/
of Ethernet transport network equipment functional blocks"./
[4] International Telecommunication Union, Recommendation G.8021 Amendment 1/
(10/2012), “Characteristics of Ethernet transport network equipment functional/
blocks”./
[5] International Telecommunication Union, Recommendation G.8021 Amendment 2/
(08/2013), “Characteristics of Ethernet transport network equipment functional/
blocks”./
[6] International Telecommunication Union, Recommendation G.7710 (02/2012), "Common/
Equipment Management Function Requirements"./
[7] International Telecommunication Union, Recommendation M.3400 (02/2000), “TMN/
management functions”./
[8] IETF RFC 2119, “Key words for use in RFCs to Indicate Requirement Levels”, March/
1997./
[9] IETF RFC 5951, "Network Management Requirements for MPLS-based Transport/
Networks", September 2010./
[10] MEF Technical Specification MEF 4, "Metro Ethernet Network Architecture Framework/
- Part 1: Generic Framework", May 2004./
[11] MEF Technical Specification MEF 7.2, "Carrier Ethernet Management Information/
Model", April 2013./
[12] MEF Technical Specification MEF 10.3, "Ethernet Services Attributes Phase 3", October/
2013./
[13] MEF Technical Specification MEF 12.2, “Carrier Ethernet Network Architecture/
Framework, Part 2: Ethernet Services Layer”, April 2014./
[14] MEF Technical Specification MEF 15, "Requirements for Management of Metro/
Ethernet Phase 1 Network Elements", November 2005./
[15] MEF Technical Specification MEF 17, "Service OAM Requirements & Framework -/
Phase 1", April 2007./
/
[16] MEF Technical Specification MEF 20, "User Network Interface (UNI) Type 2 Implementation/
Agreement", July 2008./
[17] MEF Technical Specification MEF 23.1, “Carrier Ethernet Class of Service – Phase/
2”, January 2012./
[18] MEF Technical Specification MEF 26.1, "External Network Network Interface/
(ENNI) - Phase 2", January 2012./
[19] MEF Technical Specification MEF 30.1, "Service OAM Fault Management Implementation/
Agreement: Phase 2", April 2013./
[20] MEF Technical Specification MEF 30.1.1, “Amendment to MEF 30.1 – Correction to/
Requirement”, April 2014./
[21] MEF Technical Specification MEF 47, “Carrier Ethernet Services for Cloud Implementation/
Agreement”./
[22] IEEE 802.1Q-2014, "IEEE Standard for Local and Metropolitan Area Networks –/
Bridges and Bridged Networks", 2014/
[23] ISO 8601, "Data elements and interchange formats - Information interchange – Representation/
of dates and times", Third Edition, December 1, 2004./
[24] Telcordia GR-253 (09/2000), “SONET Transport Systems: Common Generic Criteria”./
[25] International Telecommunication Union, Recommendation X.738 (11/1993), " Information/
technology – Open Systems Interconnection – Systems management: Summarization/
function".
|
|
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
|
|
