[Uri-review] draft-farrell-decade-ni (was: Two new URI schemes for review)

Graham Klyne <GK@ninebynine.org> Sun, 06 May 2012 08:17 UTC

Return-Path: <GK@ninebynine.org>
X-Original-To: uri-review@ietfa.amsl.com
Delivered-To: uri-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1539321F8491 for <uri-review@ietfa.amsl.com>; Sun, 6 May 2012 01:17:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.099
X-Spam-Level:
X-Spam-Status: No, score=-8.099 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4, URI_NOVOWEL=0.5]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Dqc--ug9-Dz for <uri-review@ietfa.amsl.com>; Sun, 6 May 2012 01:17:17 -0700 (PDT)
Received: from relay9.mail.ox.ac.uk (relay9.mail.ox.ac.uk [163.1.2.169]) by ietfa.amsl.com (Postfix) with ESMTP id CA48B21F846A for <uri-review@ietf.org>; Sun, 6 May 2012 01:17:12 -0700 (PDT)
Received: from smtp2.mail.ox.ac.uk ([163.1.2.205]) by relay9.mail.ox.ac.uk with esmtp (Exim 4.75) (envelope-from <GK@ninebynine.org>) id 1SQwe8-0006mZ-TG; Sun, 06 May 2012 09:16:48 +0100
Received: from gklyne.plus.com ([80.229.154.156] helo=Eskarina.local) by smtp2.mail.ox.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <GK@ninebynine.org>) id 1SQwe7-00006t-8m; Sun, 06 May 2012 09:16:48 +0100
Message-ID: <4FA62A44.4060101@ninebynine.org>
Date: Sun, 06 May 2012 08:37:40 +0100
From: Graham Klyne <GK@ninebynine.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: Eric Johnson <eric@tibco.com>
References: <4F9EB644.60309@cs.tcd.ie> <4FA39FE9.5010306@tibco.com>
In-Reply-To: <4FA39FE9.5010306@tibco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Oxford-Username: zool0635
Cc: uri-review@ietf.org, Barry Leiba <barryleiba@computer.org>, "draft-farrell-decade-ni@tools.ietf.org" <draft-farrell-decade-ni@tools.ietf.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: [Uri-review] draft-farrell-decade-ni (was: Two new URI schemes for review)
X-BeenThere: uri-review@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Proposed URI Schemes <uri-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uri-review>, <mailto:uri-review-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/uri-review>
List-Post: <mailto:uri-review@ietf.org>
List-Help: <mailto:uri-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uri-review>, <mailto:uri-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 May 2012 08:17:18 -0000

On 04/05/2012 10:22, Eric Johnson wrote:
> I looked at this proposal, and had three points of confusion.
>
> a) Why is this being done as a "hierarchical" URI scheme, when the URI is not,
> in fact, hierarchical?
>
> That is, why ni://example.com/....?

I think the document explains that.

And I even have a possible use-case for this in an application I'm working on - 
a hashed identifier where further information may be available from the given 
authority.

> When implementations that manipulate URIs encounter the :// after the scheme,
> that should be a signal for them to associate meaning to "relative" URIs, as in:
>
> base URI: ni://example.com/sha-256;f4OxZX_x_FO5LcGBSKHWXfwtSx-j1ncoSt3SABJtkGk
>
> ... what does it mean to do "index.html" relative to said URI?

The answer to that is clear from RFC 3986:  ni://example.com/index.html ... even 
if it's not very useful.

> Can I compute a "sha-512" relative to the given URI? (Answer: no)

I'm not sure I understand the question, but one might want to express an 
already-known sha-512 with respect to the same base.

> I conclude that this should not be a hierarchical scheme.

I don't see any harm, and some possible (small) benefits.

#g
--

> b) Why isn't this just a URN with a particular namespace identifier?
>
> As in:
>
> urn:nhi:example.com:sha-256:f4OxZX_x_FO5LcGBSKHWXfwtSx-j1ncoSt3SABJtkGk
>
> (where nhi I just made up, but stands for "named hashed id", because URNs
> require at least three letters for namespace ids)
>
> That seems like a better fit.
>
> c) Since there are more known SHA standards, why not declare them all in this
> initial proposal, so that sha-384, and sha-512 are already defined?
>
> -Eric.
>
> On 4/30/12 5:56 PM, Stephen Farrell wrote:
>> Hi,
>>
>> We have a draft [1] that requests two new URI schemes.
>>
>> The core WG are likely to want to use these we think
>> and possibly decade, but they're intended to be generally
>> useful as well.
>>
>> Barry Leiba is planning to AD sponsor this and Alexey
>> Melnikov will be shepherding so if you can cc them ase
>> well as the authors on any questions or comments that'd
>> be good.
>>
>> I hope the plan is to IETF LC this soon, once this
>> review and the .well-known registration review are
>> done.
>>
>> Thanks,
>> Stephen.
>>
>> [1] http://tools.ietf.org/html/draft-farrell-decade-ni-05
>> _______________________________________________
>> Uri-review mailing list
>> Uri-review@ietf.org
>> https://www.ietf.org/mailman/listinfo/uri-review
> _______________________________________________
> Uri-review mailing list
> Uri-review@ietf.org
> https://www.ietf.org/mailman/listinfo/uri-review
>