IETF Logo Mail Archive

Re: [decade] re-chartering

"Woundy, Richard" <Richard_Woundy@cable.comcast.com> Thu, 21 July 2011 14:49 UTC

Return-Path: <richard_woundy@cable.comcast.com>
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 BA69A21F8B0A for <decade@ietfa.amsl.com>; Thu, 21 Jul 2011 07:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.03
X-Spam-Level:
X-Spam-Status: No, score=-102.03 tagged_above=-999 required=5 tests=[AWL=-0.595, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V-gUmHQup0YZ for <decade@ietfa.amsl.com>; Thu, 21 Jul 2011 07:49:28 -0700 (PDT)
Received: from cable.comcast.com (copdcimo01.potomac.co.ndcwest.comcast.net [76.96.32.251]) by ietfa.amsl.com (Postfix) with ESMTP id 0185921F88DC for <decade@ietf.org>; Thu, 21 Jul 2011 07:49:27 -0700 (PDT)
Received: from ([24.40.55.40]) by copdcimo01.cable.comcast.com with ESMTP with TLS id 5503630.45589287; Thu, 21 Jul 2011 08:53:55 -0600
Received: from PACDCEXMB05.cable.comcast.com ([fe80::a5b0:e5c4:df1b:2367]) by pacdcexhub03.cable.comcast.com ([fe80::d1dd:b302:b617:3755%12]) with mapi id 14.01.0289.001; Thu, 21 Jul 2011 10:49:19 -0400
From: "Woundy, Richard" <Richard_Woundy@cable.comcast.com>
To: Börje Ohlman <Borje.Ohlman@ericsson.com>, Songhaibin <haibin.song@huawei.com>
Thread-Topic: [decade] re-chartering
Thread-Index: AQHMQULNa3T7B36KmEW5Crt3k4+ej5T24bYw
Date: Thu, 21 Jul 2011 14:49:18 +0000
Message-ID: <1CA25301D2219F40B3AA37201F0EACD1135D790F@PACDCEXMB05.cable.comcast.com>
References: <E33E01DFD5BEA24B9F3F18671078951F16D2AC@szxeml505-mbx.china.huawei.com> <D16A5CE9-BBBE-44A2-8707-486CBFD822E9@ericsson.com>
In-Reply-To: <D16A5CE9-BBBE-44A2-8707-486CBFD822E9@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.163.75.13]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "decade@ietf.org" <decade@ietf.org>
Subject: Re: [decade] re-chartering
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: Thu, 21 Jul 2011 14:49:28 -0000

Börje, thanks for your feedback. We will discuss the naming scheme of draft-farrell-ni in our WG session on Tuesday.

Folks, any additional feedback on the re-chartering discussion would be much appreciated. Thanks!

-- Rich

-----Original Message-----
From: decade-bounces@ietf.org [mailto:decade-bounces@ietf.org] On Behalf Of Börje Ohlman
Sent: Wednesday, July 13, 2011 5:54 AM
To: Songhaibin
Cc: decade@ietf.org
Subject: Re: [decade] re-chartering

I think the items listed below are the main items for the next period. Obviously the protocol issues are key things to complete. For the other two I want to make the following comments.

Regarding the naming scheme I want to promote the idea to select a naming scheme that can be generally applicable to naming any type of information objects and thus not making it DECADE specific. As was mentioned at the last IETF there is a draft proposing one possible such naming scheme, see http://datatracker.ietf.org/doc/draft-farrell-ni/
In the DECADE architecture draft it is proposed to use a hash of the information object to name them. I support this idea and the naming scheme proposed in our draft could definitely support such naming. It might add a slight overhead compared with using a plain hash, but it will add flexibility and possibility for future extensions. These features could be useful if there is a need to change a comprised hash algorithm in the future or for making DECADE work smoothly with other future features provided by e.g. ALTO or CDNI.

Regarding service discovery I think this is a very important issue that is key for making it possible to use DECADE in scenarios where users and hosts are roaming in the network.

		Börje


On 20 jun 2011, at 09.54, Songhaibin wrote:

> Dear all,
> 
> As we began our discussion about re-chartering from last IETF meeting. We would like to hear more thoughts and comments in the list. The topics include but not limit to what we talked at last meeting.
> 
> 1. protocols
> 2. Mandatory underlying protocol
> 3. Mandatory naming scheme
> 4. service discovery and etc.
> 
> What stuff should we work on in the next period in this WG in your opinion? Any special consideration?
> 
> BR,
> -Haibin and Rich
> _______________________________________________
> decade mailing list
> decade@ietf.org
> https://www.ietf.org/mailman/listinfo/decade

_______________________________________________
decade mailing list
decade@ietf.org
https://www.ietf.org/mailman/listinfo/decade

v2.23.0 | Report a Bug | By Email