<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-nvo3-hpvr2nve-cp-req" target="https://datatracker.ietf.org/doc/html/draft-ietf-nvo3-hpvr2nve-cp-req-17">
   <front>
      <title>Split Network Virtualization Edge (Split-NVE) Control-Plane Requirements</title>
      <author initials="Y." surname="Li" fullname="Yizhou Li">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="D. E." surname="Eastlake" fullname="Donald E. Eastlake 3rd">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="L." surname="Kreeger" fullname="Larry Kreeger">
         <organization>Arrcus, Inc</organization>
      </author>
      <author initials="T." surname="Narten" fullname="Dr. Thomas Narten">
         <organization>IBM</organization>
      </author>
      <author initials="D. L." surname="Black" fullname="David L. Black">
         <organization>Dell EMC</organization>
      </author>
      <date month="March" day="13" year="2018" />
      <abstract>
	 <t>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 &quot;External NVE&quot;. 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 &quot;location&quot; 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.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-nvo3-hpvr2nve-cp-req-17" />
   
</reference>
