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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 28 July 2011 13:41 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 8188D21F8799 for <apps-discuss@ietfa.amsl.com>; Thu, 28 Jul 2011 06:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 tku5uA1uOJwy for <apps-discuss@ietfa.amsl.com>; Thu, 28 Jul 2011 06:41:29 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id 61B9D21F8640 for <apps-discuss@ietf.org>; Thu, 28 Jul 2011 06:41:29 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 41F55171C58; Thu, 28 Jul 2011 14:41:15 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; h= content-transfer-encoding:content-type:in-reply-to:references :subject:mime-version:user-agent:from:date:message-id:received :received:x-virus-scanned; s=cs; t=1311860474; bh=WhFqBW2XkRS9WS JVMHF5vjXTpNCByXI4xZLR1jsWozQ=; b=am7d6oKbuZ12dIJK2ijtsD12M3Pl1O Zkwz1TyqPom7oou8vhCb3/afXdxItvR8eq8Y5e+oRT8dGfz7amUIZsuiJCLCb4Bk XDjobh+zAeV0jinuyBi2slRj4G1HUWvw8JGgVqdYtGaHi2kqVaClvycWKOPPDk6T aqRynOdISx0+vHy9Lkhj+nE2MQvdqrsSjC1Zgxbr5V0O3601DKdBc3ta3bxTNBvJ r0WPatszlT2s+wQ04PV0Xed6dEXR1XrzsYs5ANil1/MxVTJufRL/jUaO7aIg69rV ZbMVh1CcUVOSw5kAvBig79pLUQu7xd4ugKjoyUnY57xxljeHb2TFip3g==
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from scss.tcd.ie ([127.0.0.1]) by localhost (scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10027) with ESMTP id kwu0CBJ9Y+mh; Thu, 28 Jul 2011 14:41:14 +0100 (IST)
Received: from [130.129.17.184] (dhcp-11b8.meeting.ietf.org [130.129.17.184]) by smtp.scss.tcd.ie (Postfix) with ESMTPSA id 58CDF171C59; Thu, 28 Jul 2011 14:41:08 +0100 (IST)
Message-ID: <4E3166F2.4020104@cs.tcd.ie>
Date: Thu, 28 Jul 2011 14:41:06 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.18) Gecko/20110617 Lightning/1.0b2 Thunderbird/3.1.11
MIME-Version: 1.0
To: Linyi Tian 01 <tianlinyi@huawei.com>
References: <CA56328E.2FE%tianlinyi@huawei.com>
In-Reply-To: <CA56328E.2FE%tianlinyi@huawei.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
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: Thu, 28 Jul 2011 13:41:30 -0000

On 28/07/11 02:25, Linyi Tian 01 wrote:
> 
> 
> On 11-7-27 上午11:49, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:
> 
>>
>> Hi,
>>
>> Yesterday, I presented a draft [1] on a URI scheme for naming
>> stuff to the decade WG. There's interest in that there but
>> the idea behind this is really broader than just decade so
>> if there's interest here, doing this work in the appsarea WG
>> would I think be much better.
>>
>> The scheme is basically like HTTP URIs with one additional
>> thing, which is that it specifies a way to include a hash
>> function output in the name (and the related input, in case
>> you want to verify something later) which seems to me to be
>> a generally useful thing that various protocols could use
>> in various ways. Hence the idea of bringing it here.
> 
> I am wondering how this would be used. Will it be used together with HTTP
> URIs? Is there any real life use case how I can use this URI.

There are two ways in which this could be used I think, one is
where a protocol carries a URI and then the new scheme could be
used. For HTTP URLs one could use the hash-string construct
within the pathname I guess and that might be useful to document
as an option.

As I said the decade wg are thinking about this for their protocol
work. There are also many HTTP URLs that contain hashes, the extent
to which it'd be useful for someone to be able to know what was input
to the hash is hard to tell. I suspect it'd be useful sometimes
though.

S.

> 
>>
>> So, comments appreciated,
>>
>> Thanks,
>> Stephen.
>>
>> [1] http://tools.ietf.org/html/draft-farrell-ni
>>
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
> 
> 
>