RFC 8394

Split Network Virtualization Edge (Split-NVE) Control-Plane Requirements, May 2018

File formats:
icon for text file icon for PDF icon for HTML
Y. Li
D. Eastlake 3rd
L. Kreeger
T. Narten
D. Black
nvo3 (rtg)

Cite this RFC: TXT  |  XML  |   BibTeX

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

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

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


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.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.

Advanced Search