Re: [Uri-review] Two new URI schemes for review

Ted Hardie <ted.ietf@gmail.com> Fri, 04 May 2012 14:44 UTC

Return-Path: <ted.ietf@gmail.com>
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 4D66F21F8744 for <uri-review@ietfa.amsl.com>; Fri, 4 May 2012 07:44:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.324
X-Spam-Level:
X-Spam-Status: No, score=-4.324 tagged_above=-999 required=5 tests=[AWL=0.775, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-1, 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 5ZyFxkITxQik for <uri-review@ietfa.amsl.com>; Fri, 4 May 2012 07:44:24 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8BBCE21F87B4 for <uri-review@ietf.org>; Fri, 4 May 2012 07:44:24 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so2489294vbb.31 for <uri-review@ietf.org>; Fri, 04 May 2012 07:44:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ajGEmSrsuAVYWyIvNZJ2dEuhvNv+Q8oLgrFkvpxzdnE=; b=sXcBYDbhfpX18UtZZTMu8+EXr5TtTxox3WhfvWxth3cNrmRqnt/iNU5jrJ547LszvO hEP5VrbO1DxFn1ELuVLY9E8ZWA5jIo9QlqaS5vTpZF8TssyW+JxCPWK0A4bsmx+cMxeW XfrjL3jtwb4RKFWxllBJBH/62ZZv8KFB+4ErBGmE61pSKs5Fzkn7G1Qk4NcqOiby98uJ RBFRLFEv0pVIrHIzA77VJ/oj/f+GlSSfVFf+8jvQxzFrjzTBjeg7qJJO5iil7zd/ZXvY MoM1eSroYhz3sKOCG0ARYnC5bsZ0kcFnso3BPTVGGrhv1BH5EyZ0us2aOczwdyIIW+mR cEjw==
MIME-Version: 1.0
Received: by 10.52.89.106 with SMTP id bn10mr3166880vdb.116.1336142663812; Fri, 04 May 2012 07:44:23 -0700 (PDT)
Received: by 10.52.162.99 with HTTP; Fri, 4 May 2012 07:44:23 -0700 (PDT)
In-Reply-To: <4FA39FE9.5010306@tibco.com>
References: <4F9EB644.60309@cs.tcd.ie> <4FA39FE9.5010306@tibco.com>
Date: Fri, 04 May 2012 07:44:23 -0700
Message-ID: <CA+9kkMC=m44HFyA30Cj4mQB9zBS7n_xX2vn7hHJJwjD45-e8jQ@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Eric Johnson <eric@tibco.com>
Content-Type: text/plain; charset="ISO-8859-1"
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: Re: [Uri-review] 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: Fri, 04 May 2012 14:44:25 -0000

Hi Eric,

I had some similar questions about this, but I believe this text in Section 3:

      The optional authority component may assist
      applications in accessing the object named by an ni URI.

provides the explanation.  They are using the hierarchical portion to indicate
where you might access the object named by the non-hierarchical portion.

While this is probably okay, it suffers a bit from the lack of an
access method being indicated within the URI.  The provided method
(using .well-known and HTTP) could have been made extensible by
shifting the access method into a parameter.

Note that this is not an objection to the URI scheme going forward on
my part; it's a style preference for how to manage extensibility.

regards,

Ted



On Fri, May 4, 2012 at 2:22 AM, Eric Johnson <eric@tibco.com> 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/....?
>
> 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?
>
> Can I compute a "sha-512" relative to the given URI? (Answer: no)
>
> I conclude that this should not be a hierarchical scheme.
>
> 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