{
  "number": 8394,
  "title": "Split Network Virtualization Edge (Split-NVE) Control-Plane Requirements",
  "authors": [
    "Y. Li",
    "D. Eastlake 3rd",
    "L. Kreeger",
    "T. Narten",
    "D. Black"
  ],
  "published": "2018-05",
  "status": "Informational",
  "stream": "IETF",
  "area": "rtg",
  "working_group": "nvo3",
  "pages": 26,
  "formats": [
    "TXT",
    "HTML"
  ],
  "abstract": "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 \"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.\n\nOne 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.",
  "keywords": [
    "NVO3",
    "VDP"
  ],
  "draft": "draft-ietf-nvo3-hpvr2nve-cp-req-17",
  "doi": "10.17487/RFC8394",
  "urls": {
    "html": "https://rfc.dk/rfc8394/",
    "text": "https://rfc.dk/rfc8394.txt",
    "rfc_editor": "https://www.rfc-editor.org/rfc/rfc8394",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8394/"
  },
  "text_modified": "2018-05-31T23:29:52.537664918Z"
}