[decade] RFC 6646 on DECoupled Application Data Enroute (DECADE) Problem Statement
rfc-editor@rfc-editor.org Tue, 10 July 2012 00:07 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: decade@ietfa.amsl.com
Delivered-To: decade@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F3F711E8111; Mon, 9 Jul 2012 17:07:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.203
X-Spam-Level:
X-Spam-Status: No, score=-102.203 tagged_above=-999 required=5 tests=[AWL=0.397, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nnv+P-DryKfU; Mon, 9 Jul 2012 17:07:19 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id AFAA811E8100; Mon, 9 Jul 2012 17:07:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4CA20B1E004; Mon, 9 Jul 2012 17:07:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120710000742.4CA20B1E004@rfc-editor.org>
Date: Mon, 09 Jul 2012 17:07:42 -0700
Cc: decade@ietf.org, rfc-editor@rfc-editor.org
Subject: [decade] RFC 6646 on DECoupled Application Data Enroute (DECADE) Problem Statement
X-BeenThere: decade@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "To start the discussion on DECoupled Application Data Enroute, to discuss the in-network data storage for p2p applications and its access protocol" <decade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/decade>, <mailto:decade-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/decade>
List-Post: <mailto:decade@ietf.org>
List-Help: <mailto:decade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/decade>, <mailto:decade-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Jul 2012 00:07:20 -0000
A new Request for Comments is now available in online RFC libraries. RFC 6646 Title: DECoupled Application Data Enroute (DECADE) Problem Statement Author: H. Song, N. Zong, Y. Yang, R. Alimi Status: Informational Stream: IETF Date: July 2012 Mailbox: haibin.song@huawei.com, zongning@huawei.com, yry@cs.yale.edu, ralimi@google.com Pages: 12 Characters: 25124 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-decade-problem-statement-06.txt URL: http://www.rfc-editor.org/rfc/rfc6646.txt 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. This document is a product of the Decoupled Application Data Enroute Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC