|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 30
|
|
Title:
|
Service OAM Fault Management Implementation Agreement - January 2011. This document specifies an Implementation Agreement (IA) for Service Operations, Administration, and Maintenance (OAM) that builds upon the Fault Management (FM) framework and requirements specified by [MEF 17]. FM functions are defined in [ITU-T Y.1731].
|
|
|
2.
|
Status of approval:
|
|
|
Approved in 2011
|
|
3.
|
Justification for the specific reference:
|
|
|
While the functions are defined in G.8013/Y.1731, Carrier Ethernet services networks are are supported by a SOAM FM framework as defined in MEF 30. This Recommendation describes services that would require support using this OAM.
|
|
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" -- see http://metroethernetforum.org/page_loader.php?p_id=2031
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[IEEE 802.1Q] Virtual Bridged Local Area Networks, 2005/
[IEEE 802.1ag] Virtual Bridged Local Area Networks – Amendment 5: Connectivity Fault Management, 2007/
[IETF RFC 2119] Key Words for use in RFCs to Indicate Requirement Levels/
[ITU-T Y.1731] OAM Functions and Mechanisms for Ethernet-based Networks, 2008/
[ITU-T G.8021] Characteristics of Ethernet Transport Network Equipment Functional Blocks, 2007/
[MEF 4] Metro Ethernet Network Architecture Framework – Part 1: Generic Framework/
[MEF 6.1] Ethernet Services Definition – Phase 2/
[MEF 7.1] EMS-NMS Information Model – Phase 2/
[MEF 10.2] Ethernet Service Attributes – Phase 2/
[MEF 12.1] Carrier Ethernet Network Architecture Framework Part 2: Ethernet Ser-vices Layer – Phase 2/
[MEF 16] Ethernet Local Management Interface/
[MEF 17] Service OAM Requirements and Framework – Phase 1/
[MEF 20] UNI Type II Implementation Agreement/
[MEF 23] Carrier Ethernet Class of Service – Phase 1/
[MEF 26] External Network Network Interface (ENNI) – Phase 1
|
|
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
|
