Requirements for Ethernet VPN (EVPN)
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 15
- 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.
- Publication Date
- 2014-05-01
- Status Note
- Informational
- DOI
10.17487/RFC7209- Link
- https://doi.org/10.17487/RFC7209
- Author(s)
- Ali SajassiRahul AggarwalJim UttaroDr. Nabil N. BitarWim HenderickxAldrin Isaac
- Keyword(s)
- L2VPN
Latest version of IETF RFC 7209
Document Versions — IETF RFC 7209
-
▶ IETF RFC 7209 (2014-05-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IEEE.STD802.1AX.2008 — 802.1AX EXTERNAL
- IEEE.STD802.1Q.2011 — 802.1Q EXTERNAL
- IETF RFC 2119 [Active*]
- IETF RFC 4364 [Active*]
- IETF RFC 4761 [Active*]
- IETF RFC 4762 [Active*]
- IETF RFC 6074 [Active*]
- T-REC-G.8032.2012 — G.8032 EXTERNAL
Bibliographic Reference(s)
- Martini, L., Salam, S., Sajassi, A., and S. Matsushima, "Inter-Chassis Communication Protocol for L2VPN PE Redundancy", Work in Progress, March 2014. EXTERNAL
- Metro Ethernet Forum, "Ethernet Service Definitions", MEF 6.1 Technical Specification, April 2008. EXTERNAL
- Kothari, B., Kompella, K., Henderickx, W., Balue, F., Uttaro, J., Palislamovic, S., and W. Lin, "BGP based Multi-homing in Virtual Private LAN Service", Work in Progress, July 2013. EXTERNAL
- IETF RFC 4664 [Active*]
- IETF RFC 6790 [Active*]
- IETF RFC 7117 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC7209.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 7209, Requirements for Ethernet VPN (EVPN). Available at https://doi.org/10.17487/RFC7209
Snippet:
IETF RFC 7209, Requirements for Ethernet VPN (EVPN). Available at https://doi.org/10.17487/RFC7209
HTML (ISO 690 compliant)
Preview:
IETF RFC 7209, Requirements for Ethernet VPN (EVPN). Available at https://doi.org/10.17487/RFC7209
Snippet:
<span class="citation"><cite>IETF RFC 7209</cite>, Requirements for Ethernet VPN (EVPN). Available at <a href="https://doi.org/10.17487/RFC7209" target="_blank" rel="noopener">https://doi.org/10.17487/RFC7209</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 7209, Requirements for Ethernet VPN (EVPN)
doi: 10.17487/RFC7209
url: https://doi.org/10.17487/RFC7209
doi: 10.17487/RFC7209
url: https://doi.org/10.17487/RFC7209
Snippet:
<li> <cite id="bib-rfc7209">IETF RFC 7209</cite>, Requirements for Ethernet VPN (EVPN) <span class="doi">10.17487/RFC7209</span> </li>
Referenced By
- IETF RFC 7432 [Active*]
- IETF RFC 8365 [Active*]
- IETF RFC 8466 [Active*]
- IETF RFC 9291 [Active*]