Re: review requested: "example" NID

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Tue, 08 January 2013 04:19 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: urn-nid@ietfa.amsl.com
Delivered-To: urn-nid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3F4021F8757 for <urn-nid@ietfa.amsl.com>; Mon, 7 Jan 2013 20:19:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.044
X-Spam-Level:
X-Spam-Status: No, score=-105.044 tagged_above=-999 required=5 tests=[AWL=-5.255, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, 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 AWHlb533wrkB for <urn-nid@ietfa.amsl.com>; Mon, 7 Jan 2013 20:19:29 -0800 (PST)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 3C94C21F8751 for <urn-nid@ietf.org>; Mon, 7 Jan 2013 20:19:28 -0800 (PST)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id r084JP0Q028931 for <urn-nid@ietf.org>; Tue, 8 Jan 2013 13:19:26 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 3f72_90fc_9626476a_594a_11e2_aacb_001d096c566a; Tue, 08 Jan 2013 13:19:24 +0900
Received: from [IPv6:::1] ([133.2.210.1]:57091) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S1627792> for <urn-nid@ietf.org> from <duerst@it.aoyama.ac.jp>; Tue, 8 Jan 2013 13:19:25 +0900
Message-ID: <50EB9E48.7000307@it.aoyama.ac.jp>
Date: Tue, 08 Jan 2013 13:19:20 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <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: Peter Saint-Andre <stpeter@stpeter.im>
Subject: Re: review requested: "example" NID
References: <50EB9B1C.2060103@stpeter.im>
In-Reply-To: <50EB9B1C.2060103@stpeter.im>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: urn-nid@ietf.org
X-BeenThere: urn-nid@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: discussion of new namespace identifiers for URNs <urn-nid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/urn-nid>
List-Post: <mailto:urn-nid@ietf.org>
List-Help: <mailto:urn-nid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/urn-nid>, <mailto:urn-nid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jan 2013 04:19:30 -0000

On 2013/01/08 13:05, Peter Saint-Andre wrote:
> For review here, as extracted from draft-saintandre-urn-example-01...


> 2.8.  Process for Identifier Resolution
>
>     Example URNs are not intended to be resolved, and the namespace is
>     not and probably never will be registered with a Resolution Discovery
>     System.

Just a question: What if somebody, in some system, registers this so 
that it resolves to an explanation that these are only examples?

Regards,    Martin.