Requirements for Ethernet VPN (E-VPN)
draft-ietf-l2vpn-evpn-req-01
Internet Working Group A. Sajassi
INTERNET-DRAFT Cisco
Category: Standards Track
R. Aggarwal
W. Henderickx Arktan
Alcatel-Lucent
N. Bitar
S. Salam Verizon
C. Filsfils
Cisco
Aldrin Isaac
J. Drake Bloomberg
Juniper Networks
J. Uttaro
AT&T
Expires: April 21, 2013 October 21, 2012
Requirements for Ethernet VPN (E-VPN)
draft-ietf-l2vpn-evpn-req-01.txt
Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Copyright and License Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
Sajassi, Aggarwal et al. Expires April 21, 2013 [Page 1]
INTERNET DRAFT Requirements for Ethernet VPN October 18, 2012
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
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.
Table of Contents
1. Specification of requirements . . . . . . . . . . . . . . . . . 4
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Redundancy Requirements . . . . . . . . . . . . . . . . . . . . 5
4.1. Flow-based Load Balancing . . . . . . . . . . . . . . . . 5
4.2. Flow-based Multi-pathing . . . . . . . . . . . . . . . . . 6
4.3. Geo-redundant PE Nodes . . . . . . . . . . . . . . . . . . 6
4.4. Optimal Traffic Forwarding . . . . . . . . . . . . . . . . 7
4.5. Flexible Redundancy Grouping Support . . . . . . . . . . . 7
4.6. Multi-homed Network . . . . . . . . . . . . . . . . . . . 7
5. Multicast Optimization Requirements . . . . . . . . . . . . . . 8
6. Ease of Provisioning Requirements . . . . . . . . . . . . . . . 8
7. New Service Interface Requirements . . . . . . . . . . . . . . 9
8. Fast Convergence . . . . . . . . . . . . . . . . . . . . . . . 10
9. Flood Suppression . . . . . . . . . . . . . . . . . . . . . . . 11
Show full document text