IETF Logo Mail Archive

Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Wed, 13 June 2012 06:29 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EEBB221F8716 for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 23:29:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.208
X-Spam-Level:
X-Spam-Status: No, score=-99.208 tagged_above=-999 required=5 tests=[AWL=-0.618, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_31=0.6, J_CHICKENPOX_51=0.6, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 eT8aTgjUPo7V for <ietf@ietfa.amsl.com>; Tue, 12 Jun 2012 23:29:05 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 313C621F8497 for <ietf@ietf.org>; Tue, 12 Jun 2012 23:29:04 -0700 (PDT)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id q5D6StTv002860 for <ietf@ietf.org>; Wed, 13 Jun 2012 15:28:55 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 432f_9d76_0d0ae7ce_b521_11e1_9956_001d096c566a; Wed, 13 Jun 2012 15:28:55 +0900
Received: from [IPv6:::1] ([133.2.210.1]:50545) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15D1DD4> for <ietf@ietf.org> from <duerst@it.aoyama.ac.jp>; Wed, 13 Jun 2012 15:28:59 +0900
Message-ID: <4FD83322.70203@it.aoyama.ac.jp>
Date: Wed, 13 Jun 2012 15:28:50 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: [decade] FW: Last Call: <draft-farrell-decade-ni-07.txt> (Naming Things with Hashes) to Proposed Standard
References: <E33E01DFD5BEA24B9F3F18671078951F23A88B0C@szxeml534-mbx.china.huawei.com> <CAGnGFMKjv2QR+ebynnC2GktpYf2QEx73n+0_ZZeyJrAmTYDnjg@mail.gmail.com> <CABkgnnVga6Dn5cVQA+AFzd=4LN9Y65YcJEwUiiwVJeSqg=mS0Q@mail.gmail.com> <4FD29389.5060900@cs.tcd.ie> <tslboktwbzv.fsf@mit.edu> <4FD2AAB3.4010305@cs.tcd.ie> <4FD71D6A.9070101@it.aoyama.ac.jp> <4FD7231F.1050903@cs.tcd.ie>
In-Reply-To: <4FD7231F.1050903@cs.tcd.ie>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Jonathan A Rees <rees@mumble.net>, Sam Hartman <hartmans-ietf@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 06:29:06 -0000

Hello Stephen,

On 2012/06/12 20:08, Stephen Farrell wrote:
>
> So would it work to add this:
>
> "
>     Note that relative ni URIs can occur, for example as shown in
>     Figure 5.  In such cases, user agents MUST construct the absolute URI
>     as they would in the case of an HTTP URL, that is, in the example
>     shown the absolute URI for "this third document" would be
>     "ni://example.com/sha-256-128;...".

This looks fine, except that it contains a MUST when it can just refer 
to RFC 3986. So I would suggest the following text:

    Note that relative ni URIs can occur. In such cases, the algorithm
    in Section 5 of RFC 3986 applies. As an example, in Figure 5, the
    absolute URI for "this third document" is
    "ni://example.com/sha-256-128;...".



>       <html>
>        <head>
>          <title>ni: relative URI test</title>
>          <base href="ni://example.com">
>        </head>
>
>        <body>
>          <p>Please check<a href="sha-256;f4OxZX...">this document</a>.
>            And<a href="sha-256;UyaQV...">this other document</a>.
>            And<a href="sha-256-128;...">this third document</a>.
>          </p>
>        </body>
>       </html>
>
>                  Figure 5: Example HTML with relative ni URI
>
> "
>
> Better suggestions welcome.
> Ta,

I tried to look "Ta" up on the Web, but there were just too many 
potential explanations. What are you using it for?


Regards,   Martin.

> S.

v2.30.2 | Report a Bug | By Email | System Status