|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 51.1
|
|
Title:
|
OVC Services Definitions
This document specifies Operator Ethernet Services based on the Service Attributes defined in [MEF 26.2]. The key service constructs are the Operator Virtual Connection (OVC) 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.2], at least one OVC End Point is at an ENNI. Three General Operator Ethernet 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 2018
|
|
3.
|
Justification for the specific reference:
|
|
|
OVC is a construct used for external network to network interfaces and part of a Carrier Ethernet service.
|
|
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 Carrier Ethernet services.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Commonly referenced all over the world for Carrier 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 – 2018, IEEE Standard for Local and metropolitan area networks –Bridges and Bridged Networks, May 2018/
[2] IETF RFC 2119, Key words for use in RFCs to Indicate Requirement Levels, March 1997/
[3] IETF RFC 8174, Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words, May 2017/
[4] MEF 6.2, EVC Ethernet Services Definitions Phase 3, July 2014/
[5] MEF 10.4, Subscriber Ethernet Service Attributes, December 2018/
[6] MEF 26.1, External Network Network Interface (ENNI) - Phase 2, August 2016/
[7] MEF 26.2, External Network Network Interfaces (ENNI) and Operator Service Attributes, August 2016/
[8] MEF 30.1, Service OAM Fault Management Implementation Agreement: Phase 2, April 2013/
[9] MEF 33, Ethernet Access Services Definition, January 2012/
[10] MEF 35.1, Service OAM Performance Monitoring Implementation Agreement, April 2015/
[11] MEF 51, OVC Services Definitions, August 2015/
[12] MEF 45.1, Layer 2 Control Protocols in Ethernet Services, December 2018
|
|
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
|
