Requirements for Ethernet VPN (EVPN), May 2014
- File formats:
- A. Sajassi
- l2vpn (rtg)
Discuss this RFC: Send questions or comments to firstname.lastname@example.org
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 4844.