DECoupled Application Data Enroute Problem Statement
RFC 6646, “DECoupled Application Data Enroute Problem Statement”, is an Informational document published in July 2012 by H. Song, N. Zong, Y. Yang, R. Alimi. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 6646 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6645 IP Flow Information Accounting and Export Benchmarking Methodology
- RFC 6647 Email Greylisting: An Applicability Statement for SMTP
- RFC 6644 Rebind Capability in DHCPv6 Reconfigure Messages
- RFC 6648 Deprecating the "X-" Prefix and Similar Constructs in Application Protocols
- RFC 6643 Translation of Structure of Management Information Version 2 MIB Modules to YANG Modules
- RFC 6649 Deprecate DES, RC4-HMAC-EXP, and Other Weak Cryptographic Algorithms in Kerberos
- RFC 6642 RTP Control Protocol Extension for a Third-Party Loss Report
- RFC 6650 Creation and Use of Email Feedback Reports: An Applicability Statement for the Abuse Reporting Format