Requirements for Ethernet VPN (EVPN)
RFC 7209
Document | Type | RFC - Informational (May 2014; No errata) | |
---|---|---|---|
Authors | Wim Henderickx , Jim Uttaro , Ali Sajassi , Rahul Aggarwal , Nabil Bitar , Aldrin Isaac | ||
Last updated | 2015-10-14 | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | WG Document | |
Document shepherd | Giles Heron | ||
Shepherd write-up | Show (last changed 2013-09-03) | ||
IESG | IESG state | RFC 7209 (Informational) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Adrian Farrel | ||
Send notices to | (None) | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | No IANA Actions |
Internet Engineering Task Force (IETF) A. Sajassi Request for Comments: 7209 Cisco Category: Informational R. Aggarwal ISSN: 2070-1721 Arktan J. Uttaro AT&T N. Bitar Verizon W. Henderickx Alcatel-Lucent A. Isaac Bloomberg May 2014 Requirements for Ethernet VPN (EVPN) Abstract The widespread adoption of Ethernet L2VPN services and the advent of new applications for the technology (e.g., data center interconnect) have culminated in a new set of requirements that are not readily addressable by the current Virtual Private LAN Service (VPLS) solution. In particular, multihoming with all-active forwarding is not supported, and there's no existing solution to leverage Multipoint-to-Multipoint (MP2MP) Label Switched Paths (LSPs) for optimizing the delivery of multi-destination frames. Furthermore, the provisioning of VPLS, even in the context of BGP-based auto- discovery, requires network operators to specify various network parameters on top of the access configuration. This document specifies the requirements for an Ethernet VPN (EVPN) solution, which addresses the above issues. 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/rfc7209. Sajassi, et al. Informational [Page 1] RFC 7209 Requirements for Ethernet VPN May 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 2. Specification of Requirements ...................................4 3. Terminology .....................................................4 4. Redundancy Requirements .........................................5 4.1. Flow-Based Load Balancing ..................................5 4.2. Flow-Based Multipathing ....................................6 4.3. Geo-redundant PE Nodes .....................................7 4.4. Optimal Traffic Forwarding .................................7 4.5. Support for Flexible Redundancy Grouping ...................8 4.6. Multihomed Network .........................................8 5. Multicast Optimization Requirements .............................9 6. Ease of Provisioning Requirements ...............................9 7. New Service Interface Requirements .............................10 8. Fast Convergence ...............................................12 9. Flood Suppression ..............................................12 10. Supporting Flexible VPN Topologies and Policies ...............12 11. Security Considerations .......................................13 12. Normative References ..........................................13 13. Informative References ........................................14 14. Contributors ..................................................15 Sajassi, et al. Informational [Page 2] RFC 7209 Requirements for Ethernet VPN May 2014Show full document text