<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.yizhou-nvo3-hpvr2nve-cp-req" target="https://datatracker.ietf.org/doc/html/draft-yizhou-nvo3-hpvr2nve-cp-req-00">
   <front>
      <title>Hypervisor to NVE Control Plane Requirements</title>
      <author initials="Y." surname="Li" fullname="Yizhou Li">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="L." surname="Yong" fullname="Lucy Yong">
         <organization>Huawei Technologies</organization>
      </author>
      <author initials="L." surname="Kreeger" fullname="Larry Kreeger">
         <organization>Cisco</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>EMC</organization>
      </author>
      <date month="May" day="15" year="2014" />
      <abstract>
	 <t>   This document describes the control plane protocol requirements when
   NVE is not co-located with the hypervisor on a server. A control
   plane protocol (or protocols) between a hypervisor and its associated
   external NVE(s) is used for the hypervisor to populate its virtual
   machines states to the NVE(s) for further handling. This document
   illustrates the functionalities required by such control plane
   signaling protocols and outlines the high level requirements to be
   fulfiled. Virtual machine states and state transitioning are
   summarized to help clarifying the needed requirements.



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