|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 65
|
|
Title:
|
Simplified Transit E-Line Service
This MEF Standard specifies a Simplified Transit E-Line (STEL) Service that constrains selected values of the ENNI Common Attributes, ENNI Service Attributes and Operator Ethernet Service Attributes specified in MEF 26.2 [5] to simplify ordering and provisioning for a common case of Transit E-Line Services defined in MEF 51.1 [7].
|
|
|
2.
|
Status of approval:
|
|
|
Approved in 2020
|
|
3.
|
Justification for the specific reference:
|
|
|
The Simplified Transit E-Line Service is used to make the Transit E-Line Service easier to configure.
|
|
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:
|
|
|
MEF 51.1, MEF 26.2
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] IETF RFC 2119, Key words for use in RFCs to Indicate Requirement Levels, March 1997/
[2] IETF RFC 8174, Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words, May 2017/
[3] MEF 6.3, Subscriber Ethernet Services Definitions, December 2019/
[4] MEF 10.4, Subscriber Ethernet Service Attributes, December 2018/
[5] MEF 26.2, External Network Network Interface (ENNI) – Phase 3, August 2016/
[6] MEF 43, Virtual NID (vNID) Functionality for E-Access Services, April 2014/
[7] MEF 51.1, Operator Ethernet Services Definitions, December 2018/
[8] MEF 62, Managed Access E-Line Service Implementation Agreement, May 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
|
