|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 30.1
|
|
Title:
|
Service OAM Fault Management Implementation Agreement: Phase 2
This document specifies an Implementation Agreement (IA) for Service Operations, Administra-tion, and Maintenance (OAM) that builds upon the framework and requirements specified by MEF 17 [16]. In particular, this IA specifies Service OAM requirements for Maintenance Entity Groups (MEGs) and for Fault Management (FM). Service OAM in general and FM in particular are defined in IEEE 802.1Q [3] and ITU-T Y.1731 [7]. This IA details how to use these func-tions to achieve the MEF requirements of Service OAM in general and Service OAM FM in particular.
|
|
|
2.
|
Status of approval:
|
|
|
Approved in 2013
|
|
3.
|
Justification for the specific reference:
|
|
|
The Ethernet OAM definitions in MEF 30.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:
|
|
|
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] IEEE 802.1ag, "Virtual Bridged Local Area Networks -- Amendment 5: Connectivity Fault Management", 2007 [Note: 802.1ag has been incorporated into and superseded by 802.1Q-2011.]/
[2] IEEE 802.1AX, "Link Aggregation", 2008/
[3] IEEE 802.1Q, "Virtual Bridged Local Area Networks", 2011/
[4] IEEE 802.3, “Carrier sense multiple access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications”, 2008/
[5] IETF RFC 2119, “Key words for use in RFCs to Indicate Requirement Levels”, 1997/
[6] ITU-T G.8021, “Characteristics of Ethernet Transport Network Equipment Functional Blocks”, 2012/
[7] ITU-T Y.1731, "OAM functions and mechanisms for Ethernet based Networks", 2011/
[8] MEF 4, “Metro Ethernet Network Architecture Framework – Part 1: Generic Frame-work”, 2004/
[9] MEF 6.1, “Ethernet Services Definition – Phase 2”, 2008/
[10] MEF 7.1, “EMS-NMS Information Model – Phase 2”, 2009/
[11] MEF 10.2, “Ethernet Service Attributes – Phase 2”, 2009/
[12] MEF 12.1, “Carrier Ethernet Network Architecture Framework Part 2: Ethernet Ser-vices Layer”, 2010/
[13] MEF 12.1.1, “Carrier Ethernet Network Architecture Framework Part 2: Ethernet Services Layer, - External Interface Extensions”, 2011/
[14] MEF 13, “User Network Interface (UNI) Type 1 Implementation Agreement”, 2005/
[15] MEF 16, “Ethernet Local Management Interface”, 2006/
[16] MEF 17, “Service OAM Requirements and Framework – Phase 1”, 2007/
[17] MEF 20, “UNI Type II Implementation Agreement”, 2008/
[18] MEF 23.1, “Carrier Ethernet Class of Service – Phase 2”, 2012/
[19] MEF 26.1, “External Network Network Interface (ENNI) – Phase 2”, 2012/
[20] MEF 28, “External Network Network Interface (ENNI) Support for UNI Tunnel Ac-cess and Virtual UNI”, 2010/
[21] MEF 31, “Service OAM Fault Management Definition of Managed Objects”, 2011/
[22] MEF 31.0.1, “Amendment to Service OAM SNMP MIB for Fault Management”, 2012/
[23] MEF 32, “Requirements for Service Protection Across External Interfaces”, 2011/
[24] MEF 35, “Service OAM Performance Monitoring Implementation Agreement”, 2012/
[25] MEF 38, “Service OAM Fault Management YANG Modules”, 2012
|
|
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
|
|
