
From stpeter@stpeter.im  Mon Jan  7 20:05:41 2013
Return-Path: <stpeter@stpeter.im>
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 7BDB521F867D for <urn-nid@ietfa.amsl.com>; Mon,  7 Jan 2013 20:05:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 JEHhp7fKsh-c for <urn-nid@ietfa.amsl.com>; Mon,  7 Jan 2013 20:05:40 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 8C39621F866E for <urn-nid@ietf.org>; Mon,  7 Jan 2013 20:05:40 -0800 (PST)
Received: from [192.168.1.176] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 79AED4005D for <urn-nid@ietf.org>; Mon,  7 Jan 2013 21:10:45 -0700 (MST)
Message-ID: <50EB9B1C.2060103@stpeter.im>
Date: Mon, 07 Jan 2013 21:05:48 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: urn-nid@ietf.org
Subject: review requested: "example" NID
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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:05:41 -0000

For review here, as extracted from draft-saintandre-urn-example-01...

###

2.  Specification Template

2.1.  Namespace ID

   The Namespace ID "example" is requested.

2.2.  Registration Information

   Version 1

   Date: [to be assigned]

2.3.  Declared Registrant of the Namespace

   Registering organization: IETF

   Designated contact: IESG, iesg@ietf.org

2.4.  Declaration of Syntactic Structure

   The Namespace Specific String (NSS) of all URNs that use the
   "example" NID shall have the following structure:

   urn:example:{NSS}

   The NSS is a mandatory string of ASCII characters [RFC20] that
   conforms to the URN syntax requirements [RFC2141] and that provides a



Saint-Andre               Expires July 11, 2013                 [Page 3]

Internet-Draft                Example URNs                  January 2013


   name that is useful within the relevant documentation example, test
   suite, or other application.

2.5.  Relevant Ancillary Documentation

   See [RFC6648] for information about deprecation of the "x-"
   convention in protocol parameters and identifiers.

2.6.  Identifier Uniqueness Considerations

   Those who mint example URNs ought to strive for uniqueness in the
   namespace specific string portion of the URN.  However, such
   uniqueness cannot be guaranteed through the assignment process.  As a
   result, implementers are counselled against using example URNs for
   any purposes other than documentation, private testing, and truly
   experimental contexts.

2.7.  Identifier Persistence Considerations

   Once minted, an example URN is immutable.  However, it is simply a
   string and there is no guarantee that the documentation, test suite,
   or other application using the URN is immutable.

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.

2.9.  Rules for Lexical Equivalence

   No special considerations; the rules for lexical equivalence
   specified in [RFC2141] apply.

2.10.  Conformance with URN Syntax

   No special considerations

2.11.  Validation Mechanism

   None

2.12.  Scope

   Global

###


From duerst@it.aoyama.ac.jp  Mon Jan  7 20:19:29 2013
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.

From stpeter@stpeter.im  Mon Jan  7 20:28:45 2013
Return-Path: <stpeter@stpeter.im>
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 A06BC11E80A5 for <urn-nid@ietfa.amsl.com>; Mon,  7 Jan 2013 20:28:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=-0.150, BAYES_00=-2.599, 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 ww1JmBRYwpCr for <urn-nid@ietfa.amsl.com>; Mon,  7 Jan 2013 20:28:44 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 3D13711E8097 for <urn-nid@ietf.org>; Mon,  7 Jan 2013 20:28:43 -0800 (PST)
Received: from [192.168.1.176] (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 4A6FA4005D; Mon,  7 Jan 2013 21:33:49 -0700 (MST)
Message-ID: <50EBA084.3000506@stpeter.im>
Date: Mon, 07 Jan 2013 21:28:52 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Subject: Re: review requested: "example" NID
References: <50EB9B1C.2060103@stpeter.im> <50EB9E48.7000307@it.aoyama.ac.jp>
In-Reply-To: <50EB9E48.7000307@it.aoyama.ac.jp>
X-Enigmail-Version: 1.4.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
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:28:45 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 1/7/13 9:19 PM, "Martin J. Dürst" wrote:
> 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?

I had not considered that possibility, but I suppose it could happen!

Peter

- -- 
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEARECAAYFAlDroIMACgkQNL8k5A2w/vzMKQCbBKAN9WEqC8jxObdFMs74iPc2
nesAnjkhHgI+z+b1X9NevQxDG1RGevef
=yxo6
-----END PGP SIGNATURE-----
