A Model for IPv6 Operation in OpenStack
draft-baker-openstack-ipv6-model-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Fred Baker , Chris Marino , Ian Wells , Rohit Agarwalla , Sebastian Jeuk , Gonzalo Salgueiro | ||
| Last updated | 2015-08-12 (Latest revision 2015-02-08) | ||
| 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 is an overview of a network model for OpenStack, designed to dramatically simplify scalable network deployment and operations. Requirements Language The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in [RFC2119]. Design Principle Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away. Antoine de Saint-Exupery
Authors
Fred Baker
Chris Marino
Ian Wells
Rohit Agarwalla
Sebastian Jeuk
Gonzalo Salgueiro
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)