DECADE Requirements
draft-gu-decade-reqs-05
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Gu Yingjie , David A. Bryan , Y. Richard Yang , Richard Alimi | ||
| Last updated | 2010-10-27 (Latest revision 2010-07-12) | ||
| Replaced by | draft-ietf-decade-reqs | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-decade-reqs | |
| 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 target of DECoupled Application Data Enroute (DECADE) is to provide an open and standard in-network storage system for applications, primarily P2P applications, to store, retrieve and manage their data. This draft enumerates and explains requirements, not only for store and retrieve, but also for data management, access control and resource control, that should be considered during the design and implementation of a DECADE system. These are requirements on the entire system, some of the requirements may eventually be implemented by an existing protocol with/without some extensions (e.g. the data transport level), but a user of DECADE as a complete architecture would be guaranteed such functionality.
Authors
Gu Yingjie
David A. Bryan
Y. Richard Yang
Richard Alimi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)