%% You should probably cite rfc8394 instead of this I-D.
@techreport{ietf-nvo3-hpvr2nve-cp-req-13,
    number =    {draft-ietf-nvo3-hpvr2nve-cp-req-13},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-nvo3-hpvr2nve-cp-req/13/},
    author =    {Yizhou Li and Donald E. Eastlake 3rd and Larry Kreeger and Dr. Thomas Narten and David L. Black},
    title =     {{Split Network Virtualization Edge (Split-NVE) Control Plane Requirements}},
    pagetotal = 24,
    year =      2018,
    month =     jan,
    day =       24,
    abstract =  {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.},
}