RFC 6646

DECoupled Application Data Enroute (DECADE) Problem Statement, July 2012

Canonical URL:
File formats:
Plain TextPDF
H. Song
N. Zong
Y. Yang
R. Alimi
decade (tsv)

Cite this RFC: TXT  |  XML

DOI:  http://dx.doi.org/10.17487/RFC6646

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


Peer-to-peer (P2P) applications have become widely used on the Internet today and make up a large portion of the traffic in many networks. In P2P applications, one technique for reducing the transit and uplink P2P traffic is to introduce storage capabilities within the network. Traditional caches (e.g., P2P and Web caches) provide such storage, but they can be complex (e.g., P2P caches need to explicitly support individual P2P application protocols), and do not allow users to manage resource usage policies for content in the cache. This document discusses the introduction of in-network storage for P2P applications and shows the need for a standard protocol for accessing this storage. This document is not an Internet Standards Track specification; it is published for informational purposes.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.

Download PDF Reader

Search RFCs
Advanced Search