Requirements for Ethernet VPN (E-VPN)
This is an older version of an Internet-Draft that was ultimately published as RFC 7209.
Expired & archived
|Authors||Ali Sajassi , Samer Salam , Clarence Filsfils|
|Last updated||2012-10-01 (Latest revision 2012-03-30)|
|RFC stream||Internet Engineering Task Force (IETF)|
GENART Telechat review (of -06) Ready with Nits
SECDIR Last Call review (of -05) Has Nits
|Additional resources||Mailing list discussion|
|Stream||WG state||WG Document|
|Send notices to||(None)|
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 VPLS solution. In particular, multi- homing with all-active forwarding is not supported and there's no existing solution to leverage MP2MP 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 (E-VPN) solution which addresses the above issues.
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)