DECoupled Application Data Enroute (DECADE) Problem Statement
draft-song-decade-problem-statement-02
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Song Yongchao , Ning Zong , Y. Richard Yang , Richard Alimi | ||
| Last updated | 2010-10-27 (Latest revision 2010-07-12) | ||
| Replaced by | RFC 6646 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-decade-problem-statement | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 total amount of P2P traffic is to introduce storage capabilities within the network. Traditional caches (e.g., P2P and Web caches) provide such storage, but they are complex (due to explicitly supporting individual P2P application protocols) and they do not allow users to manage access to content in the cache. For example, Content Providers cannot easily control access and resource usage policies to satisfy their own requirements. This document discusses the introduction of in-network storage for P2P applications, shows the need for a standard protocol for accessing this storage, and identifies the scope of this protocol. The accessing protocol can also be used by other applications with similar requirements.
Authors
Song Yongchao
Ning Zong
Y. Richard Yang
Richard Alimi
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)