Re: [decade] Updated DECADE Charter again

Richard Alimi <richard.alimi@yale.edu> Fri, 19 March 2010 13:04 UTC

Return-Path: <richard.alimi@gmail.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 E8A723A6800 for <decade@core3.amsl.com>; Fri, 19 Mar 2010 06:04:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.009
X-Spam-Level:
X-Spam-Status: No, score=0.009 tagged_above=-999 required=5 tests=[AWL=-0.381, BAYES_20=-0.74, DNS_FROM_OPENWHOIS=1.13]
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 kwZ19px9typt for <decade@core3.amsl.com>; Fri, 19 Mar 2010 06:04:30 -0700 (PDT)
Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by core3.amsl.com (Postfix) with ESMTP id 032253A67FD for <decade@ietf.org>; Fri, 19 Mar 2010 06:04:29 -0700 (PDT)
Received: by qw-out-2122.google.com with SMTP id 5so432585qwd.31 for <decade@ietf.org>; Fri, 19 Mar 2010 06:04:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:from:to:subject:date :user-agent:cc:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=MZE5yRhRjYt/xvQbNoQqJAid7G7L1x/WOq6JrS8wBOk=; b=RGThQfkb+loKVEp8O3DrNsxU/aIp1H4WJFzKLlc71DBFDPTUuc9yn47U5GjrXimgvr 5mMdN4Sl5QJKEjt6PwMN/dH2gn0OjM2VK19SpQWhFcqmYSFXWoOb/cYU5AMkvu+5m8tc wRmOgKV49xAQpjO93mAJfjXboFQ6fA4lOhke8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=aXp0q+7Jm3SjMzg96rv2ZdXGc7EyznaPJCJ+WS/bNHj8NMzCBo3S+CGNg3S0WFRamT l9Sbn3093ve/q0uoq3yH1JyqMUJfRJyZ2hLzwCLbFzGdWCpXO+a0hVWiPWdkCbguX/Dp yIeS3LHW/W95PxZWNnocngKsf0BXpsEDMVonM=
Received: by 10.224.72.96 with SMTP id l32mr1193188qaj.127.1269003880045; Fri, 19 Mar 2010 06:04:40 -0700 (PDT)
Received: from p4p-7.localnet (p4p-7.cs.yale.edu [128.36.233.97]) by mx.google.com with ESMTPS id 23sm732000qyk.11.2010.03.19.06.04.38 (version=SSLv3 cipher=RC4-MD5); Fri, 19 Mar 2010 06:04:39 -0700 (PDT)
Sender: Richard Alimi <richard.alimi@gmail.com>
From: Richard Alimi <richard.alimi@yale.edu>
To: "Schmidt, Christian 1. (NSN - DE/Munich)" <christian.1.schmidt@nsn.com>
Date: Fri, 19 Mar 2010 09:04:37 -0400
User-Agent: KMail/1.13.1 (Linux/2.6.31-gentoo-r6; KDE/4.4.1; x86_64; ; )
References: <201003102225103593794@huawei.com> <201003181645.02197.richard.alimi@yale.edu> <B846208195B11F4EA16E16BE9DC8A9CC02AC5D06@DEMUEXC013.nsn-intra.net>
In-Reply-To: <B846208195B11F4EA16E16BE9DC8A9CC02AC5D06@DEMUEXC013.nsn-intra.net>
MIME-Version: 1.0
Content-Type: Text/Plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201003190904.38255.richard.alimi@yale.edu>
Cc: decade@ietf.org
Subject: Re: [decade] Updated DECADE Charter again
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: Fri, 19 Mar 2010 13:04:31 -0000

Hi Christian,

On Friday 19 March 2010 7:42:04 am Schmidt, Christian 1. (NSN - DE/Munich) 
wrote:
> Hi Richard,
> 
> Some questions/comments regarding the following section:
> > > The Working Group (WG) will have three primary tasks. First, the WG
> 
> will
> 
> > > identify target applications to appropriately scope the problem and
> > > requirements. P2P applications are the primary target, but
> 
> suitability
> 
> > > to other applications with similar requirements may be considered
> > > depending on additional complexity required to support such
> > > applications.
> 
> What application do you have in mind?

We do not have any specific ones in mind, but the objective here was to allow 
other applications to be put on the table, such as suggested in Section 2.1 of 
draft-ohlman-decade-add-use-cases-reqs-00. Since the goal of the WG would be 
to define the architecture for DECADE, I personally think it is fair to allow 
consideration of other use cases.  However, I believe the specific targets 
should be decided relatively early on (certainly before any necessary 
rechartering for protocol development).

That said, I believe we still must be careful: the WG would need to weigh the 
additional complexity required to meet such additional use cases. We wish to 
avoid creating a general-purpose system that is usable for arbitrary 
applications.

> Is it possible to narrow the scope, related to the planned applications?

This is a good question.  One possibility is the following: Any application 
that is considered should have the same overall goal and workload 
characteristics as P2P (namely, content distribution), and the ability to 
implement tasks such as searching, redirection, and replication within the 
application itself (instead of relying on in-network storage for such 
services).  That is, we are not talking about some "cloud storage" service 
here.

> Will the list be included in the problem statement, the requirement
> draft or the survey document?

My feeling is that the target applications should be put in the problem 
statement.

Thanks for the comments!

-- 
Richard Alimi
Department of Computer Science
Yale University