RFC 6646: DECoupled Application Data Enroute (DECADE) Problem Statement
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC6646
- Published
- July 2012
- Authors
- H. Song; N. Zong; Y. Yang; R. Alimi
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6817Low Extra Delay Background Transport (LEDBAT)Current
December 2012
- RFC 6392A Survey of In-Network Storage SystemsCurrent
October 2011
- RFC 6972Problem Statement and Requirements of the Peer-to-Peer Streaming Protocol (PPSP)Current
July 2013
- RFC 6940REsource LOcation And Discovery (RELOAD) Base ProtocolCurrent
January 2014
- RFC 7086Host Identity Protocol-Based Overlay Networking Environment (HIP BONE) Instance Specification for REsource LOcation And Discovery (RELOAD)Current
January 2014
- RFC 7177Transparent Interconnection of Lots of Links (TRILL): AdjacencyUpdated
May 2014
- RFC 7263An Extension to the REsource LOcation And Discovery (RELOAD) Protocol to Support Direct Response RoutingCurrent
June 2014
- RFC 7264An Extension to the REsource LOcation And Discovery (RELOAD) Protocol to Support Relay Peer RoutingCurrent
June 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?