Sign in
Version 5.13.0, 2015-03-25
Report a bug

DECADE Requirements

Document type: Expired Internet-Draft (individual)
Document stream: IETF
Last updated: 2013-02-14 (latest revision 2012-08-13)
Intended RFC status: Informational
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document
Doc Shepherd Follow-up Underway
Document shepherd: Akbar Rahman
Shepherd Write-Up: Last changed 2012-08-24

IESG State: Expired (IESG: Dead)
Responsible AD: Martin Stiemerling
IESG Note: Akbar Rahman ( is the document shepherd.
Send notices to:,,

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:


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.


Gu Yingjie <>
David Bryan <>
Yang Yang <>
Peng Zhang <>
Richard Alimi <>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)