Re: [apps-discuss] proposing draft-farrell-ni as an appsarea wg item

Linyi Tian 01 <tianlinyi@huawei.com> Fri, 29 July 2011 16:48 UTC

Return-Path: <tianlinyi@huawei.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69B9D21F8B01 for <apps-discuss@ietfa.amsl.com>; Fri, 29 Jul 2011 09:48:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.228
X-Spam-Level:
X-Spam-Status: No, score=-3.228 tagged_above=-999 required=5 tests=[AWL=-0.475, BAYES_00=-2.599, MIME_CHARSET_FARAWAY=2.45, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
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 anO7bFqM+A8Z for <apps-discuss@ietfa.amsl.com>; Fri, 29 Jul 2011 09:48:53 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by ietfa.amsl.com (Postfix) with ESMTP id CB95521F8AFF for <apps-discuss@ietf.org>; Fri, 29 Jul 2011 09:48:52 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LP3003GOTDGKR@szxga04-in.huawei.com> for apps-discuss@ietf.org; Sat, 30 Jul 2011 00:48:52 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LP300MG9TDGRK@szxga04-in.huawei.com> for apps-discuss@ietf.org; Sat, 30 Jul 2011 00:48:52 +0800 (CST)
Received: from [130.129.86.170] (dhcp-56aa.meeting.ietf.org [130.129.86.170]) by szxml11-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LP300A08TDCLT@szxml11-in.huawei.com>; Sat, 30 Jul 2011 00:48:51 +0800 (CST)
Date: Fri, 29 Jul 2011 18:48:46 +0200
From: Linyi Tian 01 <tianlinyi@huawei.com>
In-reply-to: <4E329D48.3010509@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Peter Saint-Andre <stpeter@stpeter.im>
Message-id: <CA58B07C.439%tianlinyi@huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset="GB2312"
Content-transfer-encoding: quoted-printable
Thread-topic: [apps-discuss] proposing draft-farrell-ni as an appsarea wg item
User-Agent: Microsoft-MacOutlook/14.0.0.100825
Cc: Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] proposing draft-farrell-ni as an appsarea wg item
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jul 2011 16:48:53 -0000

On 11-7-29 下午1:45, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:

>
>
>On 29/07/11 01:34, Peter Saint-Andre wrote:
>> On 7/28/11 7:05 PM, Stephen Farrell wrote:
>>>
>>>
>>> On 28/07/11 21:51, Peter Saint-Andre wrote:
>>>
>>>>
>>>> I don't see the need for an authority component, but maybe I'm missing
>>>> something in the use cases.
>>>
>>> Within the information centric kind of stuff we do (as research, not
>>> ready for IETF prime time by any means) we have a need for a DNS or
>>> DNS-like authority. We also have use-cases for no authority part at
>>> all in that same space.
>>>
>>> I basically just allowed the hash-string for authority since it seemed
>>> like fun:-) That is, I have no concrete use case for that now.
>> 
>> It would be good to get an idea of the use cases people have. I've heard
>> about various folks who might want a hash URI scheme, but I haven't
>> heard about specific use cases they've got.
>
>Good plan. It'd be great to hear what similar requirements/use-cases
>exist,
>
>S.
>

Use cases are really important in this case. It is simply because we need
to understand in which environment it will be used in the correct way. If
no use cases why bother to do the technical work?

So I am looking forward to seeing use case and requirements too.

For urn based design, the URN may be too long since SHA256 will have 256
bytes hash value. Right?
urn:hash:sha256:NDc0NzgyMGVmOGQ3OGU0...

>
>
>> 
>> Peter
>>