Virtual Network Auto-Provisioning Requirements
draft-gu-nvo3-auto-provisioning-reqs-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Zhongyu Gu , Ting Ao , Qiong Sun , Vic Liu , Bhumip Khasnabish | ||
Last updated | 2016-02-22 (Latest revision 2015-08-21) | ||
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
The automatic provisioning of services may be helpful for almost every kind of service because of short service time to market, less TCO, and so on. In NVO3, [RFC7365] and [RFC7364] all have some information on "Auto-provisioning/Service discovery" or "Dynamic Provisioning". Some further information should be helpful to clarify how automatic virtual network/service provisioning can be done in NVO3 partially if total automatic service provisioning is difficult. This document describes the general virtual network provisioning processes and discusses how VN can be automatically provided and related requirements.
Authors
Zhongyu Gu
Ting Ao
Qiong Sun
Vic Liu
Bhumip Khasnabish
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)