[decade] draft-ohlman-decade-add-use-cases-reqs-00

Börje Ohlman <borje.ohlman@ericsson.com> Mon, 01 March 2010 15:39 UTC

Return-Path: <borje.ohlman@ericsson.com>
X-Original-To: decade@core3.amsl.com
Delivered-To: decade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BB69028C3EC for <decade@core3.amsl.com>; Mon, 1 Mar 2010 07:39:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.072
X-Spam-Level:
X-Spam-Status: No, score=-2.072 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, SARE_SUB_OBFU_Q1=0.227]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2QFzeBPQFcRY for <decade@core3.amsl.com>; Mon, 1 Mar 2010 07:39:16 -0800 (PST)
Received: from mailgw9.se.ericsson.net (mailgw9.se.ericsson.net [193.180.251.57]) by core3.amsl.com (Postfix) with ESMTP id 9EEFB28C335 for <decade@ietf.org>; Mon, 1 Mar 2010 07:39:12 -0800 (PST)
X-AuditID: c1b4fb39-b7c2dae000007b99-c8-4b8bdf9f8785
Received: from esessmw0197.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw9.se.ericsson.net (Symantec Brightmail Gateway) with SMTP id 32.8D.31641.F9FDB8B4; Mon, 1 Mar 2010 16:39:11 +0100 (CET)
Received: from ESESSCMS0360.eemea.ericsson.se ([169.254.2.240]) by esessmw0197.eemea.ericsson.se ([153.88.115.87]) with mapi; Mon, 1 Mar 2010 16:39:02 +0100
From: Börje Ohlman <borje.ohlman@ericsson.com>
To: "decade@ietf.org" <decade@ietf.org>
Date: Mon, 01 Mar 2010 16:39:01 +0100
Thread-Topic: draft-ohlman-decade-add-use-cases-reqs-00
Thread-Index: Acq5U3XlpmcWnqvfSPq9XAQOhF6YWQAAQ0TQ
Message-ID: <CD61166E765D0C48AF3A8E778B8C009503BA771B50@ESESSCMS0360.eemea.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [decade] draft-ohlman-decade-add-use-cases-reqs-00
X-BeenThere: decade@ietf.org
X-Mailman-Version: 2.1.9
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/listinfo/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: Mon, 01 Mar 2010 15:39:16 -0000

Please find our new draft in the IETF drafts depository:
https://datatracker.ietf.org/doc/draft-ohlman-decade-add-use-cases-reqs/

Best regards,
	Börje Ohlman. et al 

-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] 
Sent: den 1 mars 2010 16:26
To: Börje Ohlman
Cc: ove.strandberg@nsn.com; cdannewitz@upb.de; andersl@sics.se; roberta.maglione@telecomitalia.it
Subject: New Version Notification for draft-ohlman-decade-add-use-cases-reqs-00 


A new version of I-D, draft-ohlman-decade-add-use-cases-reqs-00.txt has been successfuly submitted by Borje Ohlman and posted to the IETF repository.

Filename:	 draft-ohlman-decade-add-use-cases-reqs
Revision:	 00
Title:		 Requirements for accessing data in network storage
Creation_date:	 2010-03-01
WG ID:		 Independent Submission
Number_of_pages: 8

Abstract:
So far, the intended scope of the DECoupled Application Data Enroute
(DECADE) working group has mainly been focused on peer-to-peer (P2P) applications.  There are however many non-P2P-based application that could also benefit from in-network storage.  The target of DECADE should thus specify a protocol that is also suitable for generic applications with certain characteristics and not only P2P applications.  This document enumerates a number of requirements that should be considered during the design and implementation of this protocol.
                                                                                  


The IETF Secretariat.