Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Authors:

A. Sajassi
R. Aggarwal
J. Uttaro
N. Bitar
W. Henderickx
A. Isaac

Stream:

IETF

Source:

l2vpn (rtg)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC7209

Discuss this RFC: Send questions or comments to the mailing listpals@ietf.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 7209

Abstract

The widespread adoption of Ethernet L2VPN services and the advent ofnew applications for the technology (e.g., data center interconnect)have culminated in a new set of requirements that are not readilyaddressable by the current Virtual Private LAN Service (VPLS)solution. In particular, multihoming with all-active forwarding is notsupported, and there's no existing solution to leverageMultipoint-to-Multipoint (MP2MP) Label Switched Paths (LSPs) foroptimizing the delivery of multi-destination frames. Furthermore, theprovisioning of VPLS, even in the context of BGP-based auto-discovery,requires network operators to specify various network parameters ontop of the access configuration. This document specifies therequirements for an Ethernet VPN (EVPN) solution, which addresses theabove issues.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.