Requirements for Ethernet VPN (E-VPN)
draft-ietf-l2vpn-evpn-req-00

The information below is for an old version of the document
Document Type Expired Internet-Draft (l2vpn WG)
Last updated 2012-10-01 (latest revision 2012-03-30)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state Expired
Consensus Boilerplate Unknown
Telechat date
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
https://www.ietf.org/archive/id/draft-ietf-l2vpn-evpn-req-00.txt

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.

Authors

Ali Sajassi (sajassi@cisco.com)
Samer Salam (ssalam@cisco.com)
Clarence Filsfils (cfilsfil@cisco.com)

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