|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 22.3.1
|
|
Title:
|
MEF 22.3.1 Amendment to MEF 22.3 Transport Services for Mobile Networks
This document specifies changes to the baseline document [MEF 22.3] to include the requirements for Ethernet Services that can be used as transport for 5G mobile networks. The services and requirements in this document are based on the Services defined in [b-MEF 6.2] as well as the Service Attributes defined in [b-MEF 10.3].
|
|
|
2.
|
Status of approval:
|
|
|
Approved in 2020
|
|
3.
|
Justification for the specific reference:
|
|
|
Amendment to MEF 22.3 Transport Services for Mobile Networks adds new information related to 5G mobile networks.
|
|
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 in support of MBH.
|
|
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 22.3.1 is an amendment to MEF 22.3 which is an implementation agreement that applies and extends MEF 6.2 and MEF 10.3 for Transport Services for Mobile Networks
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] MEF 22.3, Transport Services for Mobile Networks, January 2018/
[2] MEF 6.2, EVC Ethernet Services Definition Phase 3, August 2014/
[3] MEF 10.3, Ethernet Services Attributes Phase 3, October 2013 (Superseded by MEF 10.4 [4])/
[4] MEF 10.4, Subscriber Ethernet Service Attributes, December 2018/
[5] MEF 26.2, External Network Network Interface (ENNI) and Operator Service Attributes, August 2016/
[6] MEF 33, Ethernet Access Services Definitions, January 2012 (Superseded by MEF 51.1 [8])/
[7] MEF 51, OVC Services Definitions, August 2015 (Superseded by MEF 51.1 [8])/
[8] MEF 51.1, Operator Ethernet Service Definitions, 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
|
