%% You should probably cite rfc7209 instead of this I-D. @techreport{ietf-l2vpn-evpn-req-00, number = {draft-ietf-l2vpn-evpn-req-00}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-l2vpn-evpn-req/00/}, author = {Ali Sajassi and Samer Salam and Clarence Filsfils}, title = {{Requirements for Ethernet VPN (E-VPN)}}, pagetotal = 12, year = 2012, month = mar, day = 30, 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 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.}, }