|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 47.1
|
|
Title:
|
Elastic Ethernet Services & Cloud Connectivity
This document identifies the requirements for MEF Ethernet Services and MEF External Interfaces (EIs such as UNIs) as well as a management interface for use in support of Cloud Services. This support includes elastic behavior of Ethernet Service attributes that can be modified during the lifetime of the service. Support for Cloud Services falls into two broad categories: 1) interconnection of a Cloud Provider's data centers (referred to as Data Center Interconnect - DCI), and 2) interconnection of Cloud Consumers (e.g. enterprises) and Cloud Provider data centers (referred to as Data Center Access - DCA). The services and requirements in this Implementation Agreement are based on the services defined in MEF 6.2 and the attributes defined in MEF 10.3 and this IA. Support of Cloud Services is addressed for a single Cloud Provider (CP) using one or more Carrier Ethernet Networks (CENs) and point-to-point Ethernet Services.
|
|
|
2.
|
Status of approval:
|
|
|
Approved in 2021
|
|
3.
|
Justification for the specific reference:
|
|
|
MEF 47.1 revises MEF 47, and describes and defines elastic Ethernet services.
|
|
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.1Q™ – 2018, (Revision of IEEE Std 802.1Q-2014) - IEEE Standard for Local and metropolitan area networks--Bridges and Bridged Networks, May 2018./
[2] RFC 2119. Key words for use in RFCs to Indicate Requirement Levels, March 1997./
[3] RFC 8174. Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words, May 2017./
[4] MEF 6.3, Subscriber Ethernet Services Definitions, November 2019./
[5] MEF 10.4, Subscriber Ethernet Services Attributes, December 2018./
[6] MEF 23.2, Carrier Ethernet Class of Service – Phase 3, August 2016./
[7] MEF 23.2.1, Models for Bandwidth Profiles with Token Sharing, January 2017./
[8] MEF 26.2, External Network Network Interfaces (ENNI) and Operator Service Attributes, August 2016./
[9] MEF 45.1, Layer 2 Control Protocol in Ethernet Services, December 2018./
[10] MEF 47, Carrier Ethernet Services for Cloud Implementation Agreement, October 2014./
[11] MEF 51.1, Operator Service Definitions, December 2018./
[12] MEF 55, Lifecycle Service Orchestration (LSO): Reference Architecture and Framework, March 2016.
|
|
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
|
