DECADE Requirements
draft-ietf-decade-reqs-08
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Gu Yingjie , David A. Bryan , Y. Richard Yang , Peng Zhang , Richard Alimi | ||
| Last updated | 2015-10-14 (Latest revision 2012-08-13) | ||
| Replaces | draft-gu-decade-reqs | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Informational | ||
| Formats | |||
| Stream | WG state | WG Document | |
| Document shepherd | Akbar Rahman | ||
| Shepherd write-up | Show Last changed 2012-08-24 | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Martin Stiemerling | ||
| IESG note | |||
| Send notices to | decade-chairs@ietf.org |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The target of the DECoupled Application Data Enroute (DECADE) system is to provide an open and standard in-network storage system for applications, primarily P2P (peer-to-peer) applications, to store, retrieve and manage their data. This draft enumerates and explains requirements, not only for storage and retrieval, but also for data management, access control and resource control, that should be considered during the design and implementation of a DECADE- compatible 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., a protocol used to read and write data from the storage system). The requirements in this document are intended to ensure that a DECADE-compatible system architecture includes all of the desired functionality for intended applications.
Authors
Gu Yingjie
David A. Bryan
Y. Richard Yang
Peng Zhang
Richard Alimi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)