RFC 8394: Split Network Virtualization Edge (Split-NVE) Control-Plane Requirements
In plain English — editorial summary, not part of the RFC
In the Split Network Virtualization Edge (Split-NVE) architecture, the functions of the NVE are split across a server and a piece of external network equipment that is called an "External NVE". The server-resident control-plane functionality resides in control software, which may be part of hypervisor or container-management software; for simplicity, this document refers to the hypervisor as the "location" of this software. One or more control-plane protocols between a hypervisor and its associated External NVE(s) are used by the hypervisor to distribute its virtual-machine networking state to the External NVE(s) for further handling. This document illustrates the functionality required by this type of control-plane signaling protocol and outlines the high-level requirements. Virtual-machine states as well as state transitioning are summarized to help clarify the protocol requirements.
Document record
- Document ID
- RFC8394
- Published
- May 2018
- Authors
- Y. Li; D. Eastlake 3rd; L. Kreeger; T. Narten; D. Black
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 26
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8293A Framework for Multicast in Network Virtualization over Layer 3Current
January 2018
- RFC 7365Framework for Data Center (DC) Network VirtualizationCurrent
October 2014
- RFC 9469Applicability of Ethernet Virtual Private Network (EVPN) to Network Virtualization over Layer 3 (NVO3) NetworksCurrent
September 2023
- RFC 9721Extended Mobility Procedures for Ethernet VPN Integrated Routing and Bridging (EVPN-IRB)Current
April 2025
- RFC 8395Extensions to BGP-Signaled Pseudowires to Support Flow-Aware Transport LabelsCurrent
June 2018
- RFC 8393Operating the Network Service Header (NSH) with Next Protocol "None"Current
May 2018
- RFC 8397Transparent Interconnection of Lots of Links (TRILL) Multilevel Using Unique NicknamesCurrent
May 2018
- RFC 8390RSVP-TE Path Diversity Using Exclude RouteCurrent
July 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?