Hypervisor to NVE Control Plane Requirements
draft-yizhou-nvo3-hpvr2nve-cp-req-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yizhou Li , Lucy Yong , Larry Kreeger , Dr. Thomas Narten , David L. Black | ||
| Last updated | 2014-11-16 (Latest revision 2014-05-15) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
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.
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.)