Skip to main content

Split-NVE Control Plane Requirements
draft-ietf-nvo3-hpvr2nve-cp-req-05

The information below is for an old version of the document.
Document Type Expired Internet-Draft (nvo3 WG)
Authors Yizhou Li , Lucy Yong , Larry Kreeger , Dr. Thomas Narten , David L. Black
Last updated 2017-02-24 (Latest revision 2016-08-23)
Stream Internet Engineering Task Force (IETF)
Formats
Expired & archived
plain text htmlized pdfized bibtex
Reviews
Stream WG state WG Document
Document shepherd (None)
IESG IESG state Expired
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)
This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-ietf-nvo3-hpvr2nve-cp-req-05.txt

Abstract

In a Split-NVE architecture, the functions of the NVE 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 a hypervisor or container management software; for simplicity, this draft refers to the hypervisor as the location of this software. A control plane protocol(s) between a hypervisor and its associated external NVE(s) is used for 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 clarifying the needed protocol requirements.

Authors

Yizhou Li
Lucy Yong
Larry Kreeger
Dr. Thomas Narten
David L. Black

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)