<?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-16">
   <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="February" day="25" year="2018" />
      <abstract>
	 <t>   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.



	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-nvo3-hpvr2nve-cp-req-16" />
   
</reference>
