In a Split Network Virtualization Edge (Split-NVE) architecture, the
functions of the NVE (Network Virtualization Edge) are split across a
server and an external network equipment which 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.
Control plane protocol(s) 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.
Working Group Summary
The document was developed to provide input from the IETF community to help guide
the development of extensions for VDP (VSI Discovery and Configuration protocol) that
took place in parallel at the IEEE. The draft also describes how VDP is applicable
to these split-NVE scenarios.
There are no IPR declarations on the draft .
No concerns about the quality of the document. It represents
WG consensus, and it has been widely reviewed and discussed on the list over a
number of years. There was also close interaction between NVO3 and the IEEE during the
development of the draft and VDP, including liaisons and presentations at NVO3 WG
meetings by IEEE participants.
The document shepherd is Matthew Bocci (firstname.lastname@example.org).
The responsible Area Director is Alia Atlas (email@example.com).