|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 51
|
|
Title:
|
OVC Services Definitions
This document specifies Operator Virtual Connection (OVC) Services based mainly on the service
attributes defined in MEF 26.1 [7]; there are also some service attributes defined in this document
that go beyond MEF 26.1. The key service constructs are the OVC itself and the OVC End
Points at the External Interfaces (EIs) – the External Network Network Interface (ENNI) and the
User Network Interface (UNI). Per MEF 26.1 [7], at least one OVC End Point is at an ENNI.
Three General OVC Services are defined, based on OVC Type. In addition, two E-Access and
two E-Transit services are defined, based on OVC Type and the EIs involved.
|
|
|
2.
|
Status of approval:
|
|
|
Approved in 2015
|
|
3.
|
Justification for the specific reference:
|
|
|
MEF 51 contains the general OVC-based Services (O-Line, O-LAN, and O-Tree) along with Transit E-Line and Transit E-LAN Service definitions that are built on the general OVC-based Services. These for 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.1QTM – 2014, IEEE Standard for Local and metropolitan area networks –/
Media Access Control (MAC) Bridges and Virtual Bridge Local Area Networks, January/
2014/
[2] Internet Engineering Task Force RFC 2119. Key words for use in RFCs to Indicate Requirement/
Levels, March 1997/
[3] MEF Forum, MEF 4, Metro Ethernet Network Architecture Framework - Part 1: Generic/
Framework, May 2004/
[4] MEF Forum, MEF 6.2, EVC Ethernet Services Definitions Phase 3, July 2014/
[5] MEF Forum, MEF 10.3, Ethernet Services Attributes Phase 3, October 2013/
[6] MEF Forum, MEF 23.1, Carrier Ethernet Class of Service Phase 2, January 2012/
[7] MEF Forum, MEF 26.1, External Network Network Interface (ENNI), January 2012/
[8] MEF Forum, MEF 28, External Network Network Interface Support for UNI Tunnel Access/
and Virtual UNI, October 2010/
[9] MEF Forum, MEF 30.1, Service OAM Fault Management Implementation Agreement:/
Phase 2, April, 2013/
[10] MEF Forum, MEF 33, Ethernet Access Services Definition, January 2012/
[11] MEF Forum, MEF 35.1, Service OAM Performance Monitoring Implementation Agreement,/
April, 2015/
[12] MEF Forum, MEF 43, Virtual NID Functionality for E-Access Services, April 2014.
|
|
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
|
|
