Split Network Virtualization Edge (Split-NVE) Control-Plane Requirements
RFC 8394

Received changes through RFC Editor sync (changed abstract to '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.')

Received changes through RFC Editor sync (created alias RFC 8394, changed title to 'Split Network Virtualization Edge (Split-NVE) Control-Plane Requirements', changed abstract to '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.', changed pages to 26, changed standardization level to Informational, changed state to RFC, added RFC published event at 2018-05-31, changed IESG state to RFC Published)