Virtual Network Auto-Provisioning Requirements
draft-gu-nvo3-auto-provisioning-reqs-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Zhongyu Gu , Ting Ao , Qiong Sun , Vic Liu | ||
| Last updated | 2015-07-20 (Latest revision 2015-01-04) | ||
| RFC stream | (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
[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 NVO3 general virtual network provisioning processes and discusses how VN can be automatically provided and related requirements in or out of the scope of NVO3.
Authors
Zhongyu Gu
Ting Ao
Qiong Sun
Vic Liu
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)