Requirements for Ethernet VPN
RFC 7209, “Requirements for Ethernet VPN”, is an Informational document published in May 2014 by A. Sajassi, R. Aggarwal, J. Uttaro, N. Bitar, W. Henderickx, A. Isaac. The canonical text is published by the RFC Editor.
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 7209 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7208 Sender Policy Framework for Authorizing Use of Domains in Email, Version 1
- RFC 7210 Database of Long-Lived Symmetric Cryptographic Keys
- RFC 7207 A Uniform Resource Name Namespace for Eurosystem Messaging
- RFC 7211 Operations Model for Router Keying
- RFC 7206 Requirements for an End-to-End Session Identification in IP-Based Multimedia Communication Networks
- RFC 7212 MPLS Generic Associated Channel Advertisement Protocol
- RFC 7205 Use Cases for Telepresence Multistreams
- RFC 7213 MPLS Transport Profile Next-Hop Ethernet Addressing