Browse Prior Art Database

Requirements for Ethernet VPN (EVPN) (RFC7209)

IP.com Disclosure Number: IPCOM000236922D
Original Publication Date: 2014-May-01
Included in the Prior Art Database: 2014-May-22
Document File: 30 page(s) / 34K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Sajassi: AUTHOR [+6]

Abstract

Virtual Private LAN Service (VPLS), as defined in [RFC4664], [RFC4761], and [RFC4762], is a proven and widely deployed technology. However, the existing solution has a number of limitations when it comes to redundancy, multicast optimization, and provisioning simplicity. Furthermore, new applications are driving several new requirements for other L2VPN services such as Ethernet Tree (E-Tree) and Virtual Private Wire Service (VPWS).

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 8% of the total text.

Internet Engineering Task Force (IETF)                        A. Sajassi Request for Comments: 7209                                         Cisco Category: Informational                                      R. Aggarwal ISSN: 2070-1721                                                   Arktan                                                                J. Uttaro                                                                     AT&T                                                                 N. Bitar                                                                  Verizon                                                            W. Henderickx                                                           Alcatel-Lucent                                                                 A. Isaac                                                                Bloomberg                                                                 May 2014

                   Requirements for Ethernet VPN (EVPN)

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 Virtual Private LAN Service (VPLS)    solution.  In particular, multihoming with all-active forwarding is    not supported, and there's no existing solution to leverage    Multipoint-to-Multipoint (MP2MP) Label Switched Paths (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 (EVPN) solution, which    addresses the above issues.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publicati...