IETF Logo Mail Archive

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

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 28 July 2011 23:06 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 CA3B011E809B for <apps-discuss@ietfa.amsl.com>; Thu, 28 Jul 2011 16:06:17 -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 GZrMZ9qaB5xw for <apps-discuss@ietfa.amsl.com>; Thu, 28 Jul 2011 16:06:17 -0700 (PDT)
Received: from scss.tcd.ie (hermes.cs.tcd.ie [134.226.32.56]) by ietfa.amsl.com (Postfix) with ESMTP id 303EC11E8082 for <apps-discuss@ietf.org>; Thu, 28 Jul 2011 16:06:17 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hermes.scss.tcd.ie (Postfix) with ESMTP id 14349171C1A; Fri, 29 Jul 2011 00:06:13 +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=1311894372; bh=6Hluh+aYyukaMi jUFXKG1IWe5HVmXXjiahx2au08VAM=; b=qkBwdDFry/F5BZf84zONpraZIjxwqc mpn2jRivadFebrAvbKvgEC7uokxNnzHvNoLjV8afZ2s3YtpWaCPXKaqRMLY0uJ0r bjfDCBFIEoumpsvvOBEb+0lEun6vxwcqPCG7m0yWBaO1NxJgc6/VBSuXCgzkp4Ff yuSN2hFWIfBKDNL95RTk4tMIWPlnJZE5aohyIkI/Ip5cm2tTXJcsMaj9NYAhZy1t NlgEEVqvMbP0Cpyd0g0dKJmbeH/ntcfc1bDbilQWSiivHf103MDIO7Qh6KJH3Eo+ 6iqJiQbJgHBeQkb6cW3/ntYTgyQwtD3XofX0v3qgPfHg3ZFdBS1lnEeA==
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 bej9GHlvx8dn; Fri, 29 Jul 2011 00:06:12 +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 E59FE171C18; Fri, 29 Jul 2011 00:06:01 +0100 (IST)
Message-ID: <4E31EB51.5010408@cs.tcd.ie>
Date: Fri, 29 Jul 2011 00:05:53 +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: Peter Saint-Andre <stpeter@stpeter.im>
References: <CA56328E.2FE%tianlinyi@huawei.com> <4E3166F2.4020104@cs.tcd.ie> <4E31CBD3.8040200@stpeter.im>
In-Reply-To: <4E31CBD3.8040200@stpeter.im>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
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 23:06:17 -0000

On 28/07/11 21:51, Peter Saint-Andre wrote:

> 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 think that's useful input - thanks.

> 
> 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.

S.


> 
> Peter
>

v2.23.0 | Report a Bug | By Email