Cloud Assets
draft-fisher-cloudassets-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Todd Fisher , Peter Walsh | ||
| Last updated | 2017-03-27 (Latest revision 2016-09-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
There is no standardized method to describe assets used in a cloud such that they can be moved from one cloud to the next independent of the underlying architecture. This document defines Cloud Assets as a lightweight description of cloud resources and proposes a standardization of Cloud Assets into three major categories: Resource Assets, Component Assets, and Composite Assets.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)