RFC 9014: Interconnect Solution for Ethernet VPN (EVPN) Overlay Networks
In plain English — editorial summary, not part of the RFC
This document describes how Network Virtualization Overlays (NVOs) can be connected to a Wide Area Network (WAN) in order to extend the Layer 2 connectivity required for some tenants. The solution analyzes the interaction between NVO networks running Ethernet Virtual Private Networks (EVPNs) and other Layer 2 VPN (L2VPN) technologies used in the WAN, such as Virtual Private LAN Services (VPLSs), VPLS extensions for Provider Backbone Bridging (PBB-VPLS), EVPN, or PBB-EVPN. It also describes how the existing technical specifications apply to the interconnection and extends the EVPN procedures needed in some cases. In particular, this document describes how EVPN routes are processed on Gateways (GWs) that interconnect EVPN-Overlay and EVPN-MPLS networks, as well as the Interconnect Ethernet Segment (I-ES), to provide multihoming. This document also describes the use of the Unknown MAC Route (UMR) to avoid issues of a Media Access Control (MAC) scale on Data Center Network Virtualization Edge (NVE) devices.
Document record
- Document ID
- RFC9014
- Published
- May 2021
- Authors
- J. Rabadan; S. Sathappan; W. Henderickx; A. Sajassi; J. Drake
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9015BGP Control Plane for the Network Service Header in Service Function ChainingCurrent
June 2021
- RFC 9013OSPF Advertisement of Tunnel EncapsulationsCurrent
April 2021
- RFC 9012The BGP Tunnel Encapsulation AttributeUpdated
April 2021
- RFC 9016Flow and Service Information Model for Deterministic Networking (DetNet)Current
March 2021
- RFC 9017Special-Purpose Label TerminologyCurrent
April 2021
- RFC 9010Routing for RPL (Routing Protocol for Low-Power and Lossy Networks) LeavesUpdated
April 2021
- RFC 9009Efficient Route InvalidationCurrent
April 2021
- RFC 9008Using RPI Option Type, Routing Header for Source Routes, and IPv6-in-IPv6 Encapsulation in the RPL Data PlaneCurrent
April 2021
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?