NVO3 VDP Gap Analysis - VM-to-NVE Specific Control-Plane Requirements
draft-pt-nvo3-vdp-vm2nve-gap-analysis-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Joseph Pelissier , Patricia Thaler , Paul Bottorff | ||
| Last updated | 2014-12-21 (Latest revision 2014-06-19) | ||
| 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
[I-D.kreeger-nvo3-hypervisor-nve-cp-01] discusses requirements for Hypervisor-to-NVE Control Plane Protocol Functionality. The IEEE has developed a protocol called VSI Discovery Protocol (VDP) specified in [IEEE8021Qbg]. This protocol is intended to address the same basic problems at layer two as the Hypervisor-to-NVE protocol needs to address at layer three. Simply by adding the ability to carry layer three addresses to VDP using the extensibility features built into the protocol, VDP may be used as the Hypervisor-to-NVE Control Plane protocol.
Authors
Joseph Pelissier
Patricia Thaler
Paul Bottorff
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)