|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
MEF 151
|
|
Title:
|
Cross-Connection Service Attributes
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 2024
|
|
3.
|
Justification for the specific reference:
|
|
|
MEF 151 specifies cross-connection service attributes.
|
|
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™-2022, IEEE Standard for Local and metropolitan area networks — Bridges and Bridged Networks, 2022/
[2] IEEE Std 802.3™-2022, IEEE Standard for Ethernet, 2022/
[3] IETF RFC 2119, Key words for use in RFCs to Indicate Requirement Levels, by Scott Bradner, March 1997/
[4] IETF RFC 8174, Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words, by B Leiba, May 2017, Copyright © 2017 IETF Trust and the persons identified as the document authors. All rights reserved./
[5] ISO 7498, Information technology – Open Systems Interconnection – Basic Reference Model: The Basic Model --- Part 1, November 1994/
[6] MEF 51.1, Operator Ethernet Service Definition, December 2018/
[7] MEF 61.1.1, Amendment to MEF 61.1: UNI Access Link Trunks, IP Addresses, and Mean Time to Repair Performance Metric, July 2022/
[8] MEF 63, Subscriber Layer 1 Service Attributes, August 2018/
[9] MEF 130, Device Physical and Environmental Service Attributes, February 2023
|
|
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
|
