Skip to main content

Requirements for Ethernet VPN (E-VPN)

Document Type Expired Internet-Draft (individual)
Authors Ali Sajassi , Samer Salam , Clarence Filsfils
Last updated 2011-07-11
Stream (None)
Intended RFC status (None)
Expired & archived
plain text htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)
This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at:


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.


Ali Sajassi
Samer Salam
Clarence Filsfils

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)