Requirements for Metro Ethernet Forum (MEF) Ethernet-Tree (E-Tree) Support in Layer 2 Virtual Private Network (L2VPN)
RFC 7152
Document | Type | RFC - Informational (March 2014; No errata) | |
---|---|---|---|
Authors | Raymond Key , Simon DeLord , Frederic JOUNAY , Lu Huang , Zhihua Liu , Manuel Paul | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | Submitted to IESG for Publication | |
Document shepherd | Nabil Bitar | ||
Shepherd write-up | Show (last changed 2013-10-24) | ||
IESG | IESG state | RFC 7152 (Informational) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Adrian Farrel | ||
Send notices to | (None) | ||
IANA | IANA review state | IANA OK - No Actions Needed | |
IANA action state | No IANA Actions |
Internet Engineering Task Force (IETF) R. Key, Ed. Request for Comments: 7152 S. Delord Category: Informational Telstra ISSN: 2070-1721 F. Jounay Orange CH L. Huang China Mobile Z. Liu China Telecom M. Paul Deutsche Telekom March 2014 Requirements for Metro Ethernet Forum (MEF) Ethernet-Tree (E-Tree) Support in Layer 2 Virtual Private Network (L2VPN) Abstract This document provides functional requirements for the support of Metro Ethernet Forum (MEF) Ethernet Tree (E-Tree) in multipoint Layer 2 Virtual Private Network solutions (referred to as simply "L2VPN"). It is intended that potential solutions will use these requirements as guidelines. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7152. Key, et al. Informational [Page 1] RFC 7152 Requirement E-Tree in L2VPN March 2014 Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction ....................................................3 1.1. Conventions Used in This Document ..........................3 2. IETF Multipoint Ethernet L2VPN Services .........................3 2.1. VPLS .......................................................3 2.2. Ethernet Virtual Private Network (E-VPN) ...................3 3. MEF Multipoint Ethernet Services ................................4 3.1. Similarities between E-LAN and E-Tree ......................4 3.2. Differences between E-LAN and E-Tree .......................4 3.3. E-Tree Use Cases ...........................................5 3.4. Generic E-Tree Service .....................................6 4. Problem Statement ...............................................6 4.1. Motivation .................................................6 4.2. Leaf-to-Leaf Communication Restriction .....................6 5. Requirements ....................................................7 5.1. Functional Requirements ....................................7 5.2. Applicability ..............................................8 5.3. Backward Compatibility .....................................8 5.4. External Network Network Interface (ENNI) ..................8 6. Security Considerations .........................................8 7. Contributors ....................................................8 8. Acknowledgements ................................................9 9. References ......................................................9 9.1. Normative References .......................................9 9.2. Informative References ....................................10 Appendix A. Frequently Asked Question .............................11 A.1. Are E-Tree Requirements Addressed in the Virtual Private Multicast Service (VPMS) Requirements? ...............11 Key, et al. Informational [Page 2] RFC 7152 Requirement E-Tree in L2VPN March 2014Show full document text