Re: [apps-discuss] proposing draft-farrell-ni as an appsarea wg item
Peter Saint-Andre <stpeter@stpeter.im> Thu, 28 July 2011 20:51 UTC
Return-Path: <stpeter@stpeter.im>
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 6F8D621F8B20 for <apps-discuss@ietfa.amsl.com>; Thu, 28 Jul 2011 13:51:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.561
X-Spam-Level:
X-Spam-Status: No, score=-102.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, 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 zVykpU3+Goix for <apps-discuss@ietfa.amsl.com>; Thu, 28 Jul 2011 13:51:33 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id C7CB021F8B1B for <apps-discuss@ietf.org>; Thu, 28 Jul 2011 13:51:33 -0700 (PDT)
Received: from dhcp-13ac.meeting.ietf.org (unknown [198.135.0.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 26787410E8; Thu, 28 Jul 2011 14:52:37 -0600 (MDT)
Message-ID: <4E31CBD3.8040200@stpeter.im>
Date: Thu, 28 Jul 2011 16:51:31 -0400
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
References: <CA56328E.2FE%tianlinyi@huawei.com> <4E3166F2.4020104@cs.tcd.ie>
In-Reply-To: <4E3166F2.4020104@cs.tcd.ie>
X-Enigmail-Version: 1.2
OpenPGP: url=https://stpeter.im/stpeter.asc
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 20:51:34 -0000
On 7/28/11 9:41 AM, Stephen Farrell wrote: > > > 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. I've heard about other folks who are interested in a very simple method for either a URN or a URI for identifying the output of a hash function. Possible examples of URNs and URIs: urn:hash:sha256:NDc0NzgyMGVmOGQ3OGU0... sha256:NDc0NzgyMGVmOGQ3OGU0... I don't think this should be a URN, because a URN namespace is managed. (In this sense RFC 4122 is misguided and deserves to be deprecated.) I don't see the need for an authority component, but maybe I'm missing something in the use cases. Peter -- Peter Saint-Andre https://stpeter.im/
- Re: [apps-discuss] proposing draft-farrell-ni as … Linyi Tian 01
- [apps-discuss] proposing draft-farrell-ni as an a… Stephen Farrell
- Re: [apps-discuss] proposing draft-farrell-ni as … Mykyta Yevstifeyev
- Re: [apps-discuss] proposing draft-farrell-ni as … Larry Masinter
- Re: [apps-discuss] proposing draft-farrell-ni as … Stephen Farrell
- Re: [apps-discuss] proposing draft-farrell-ni as … Linyi Tian 01
- Re: [apps-discuss] proposing draft-farrell-ni as … Peter Saint-Andre
- Re: [apps-discuss] proposing draft-farrell-ni as … Stephen Farrell
- Re: [apps-discuss] proposing draft-farrell-ni as … Peter Saint-Andre
- Re: [apps-discuss] proposing draft-farrell-ni as … Stephen Farrell
- Re: [apps-discuss] proposing draft-farrell-ni as … Barry Leiba
- Re: [apps-discuss] proposing draft-farrell-ni as … Linyi Tian 01