RFC 8365: A Network Virtualization Overlay Solution Using Ethernet VPN (EVPN)
In plain English — editorial summary, not part of the RFC
This document specifies how Ethernet VPN (EVPN) can be used as a Network Virtualization Overlay (NVO) solution and explores the various tunnel encapsulation options over IP and their impact on the EVPN control plane and procedures. In particular, the following encapsulation options are analyzed: Virtual Extensible LAN (VXLAN), Network Virtualization using Generic Routing Encapsulation (NVGRE), and MPLS over GRE. This specification is also applicable to Generic Network Virtualization Encapsulation (GENEVE); however, some incremental work is required, which will be covered in a separate document. This document also specifies new multihoming procedures for split-horizon filtering and mass withdrawal. It also specifies EVPN route constructions for VXLAN/NVGRE encapsulations and Autonomous System Border Router (ASBR) procedures for multihoming of Network Virtualization Edge (NVE) devices.
Document record
- Document ID
- RFC8365
- Published
- March 2018
- Authors
- A. Sajassi; J. Drake; N. Bitar; R. Shekhar; J. Uttaro; W. Henderickx
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rtg
- Pages
- 33
- Also known as
- —
- Updated by:
- RFC 9746
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8364PIM Flooding Mechanism (PFM) and Source Discovery (SD)Updated
March 2018
- RFC 8363GMPLS OSPF-TE Extensions in Support of Flexi-Grid Dense Wavelength Division Multiplexing (DWDM) NetworksCurrent
May 2018
- RFC 8362OSPFv3 Link State Advertisement (LSA) ExtensibilityCurrent
April 2018
- RFC 8361Transparent Interconnection of Lots of Links (TRILL): Centralized Replication for Active-Active Broadcast, Unknown Unicast, and Multicast (BUM) TrafficCurrent
April 2018
- RFC 8360Resource Public Key Infrastructure (RPKI) Validation ReconsideredCurrent
April 2018
- RFC 8370Techniques to Improve the Scalability of RSVP-TE DeploymentsCurrent
May 2018
- RFC 8359Network-Assigned Upstream LabelCurrent
March 2018
- RFC 8372MPLS Flow Identification ConsiderationsCurrent
May 2018
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?