request for NID review: "iana"

Peter Saint-Andre <stpeter@stpeter.im> Thu, 08 November 2012 00:25 UTC

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 DCDEE21F8BB1 for <urn-nid@ietfa.amsl.com>; Wed, 7 Nov 2012 16:25:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level:
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, 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 UPVt-2FcXoOW for <urn-nid@ietfa.amsl.com>; Wed, 7 Nov 2012 16:25:00 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 2D43821F8BDA for <urn-nid@ietf.org>; Wed, 7 Nov 2012 16:25:00 -0800 (PST)
Received: from [130.129.84.156] (unknown [130.129.84.156]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 3A44340062; Wed, 7 Nov 2012 17:28:41 -0700 (MST)
Message-ID: <509AFBD8.7060703@stpeter.im>
Date: Wed, 07 Nov 2012 19:24:56 -0500
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: urn-nid@ietf.org
Subject: request for NID review: "iana"
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: Michelle Cotton <michelle.cotton@icann.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: Thu, 08 Nov 2012 00:25:01 -0000

The following is a formal namespace registration for the namespace ID
"iana". Review and feedback would be appreciated. The related I-D is:

https://datatracker.ietf.org/doc/draft-saintandre-iana-urn/

Peter

###

   Namespace ID:

      The Namespace ID "iana" is requested.

   Registration Information:

      Version 1
      Date: [[to be assigned by the RFC Editor]]

   Declared Registrant of the Namespace:

      Registering organization
         Organization: Internet Assigned Numbers Authority (IANA)
         Address: 4676 Admiralty Way, Suite 330
                  Marina del Rey, CA
                  90292-6601
                  USA

      Designated contact
         Role: IANA team
         Email: iana@iana.org

   Declaration of Syntactic Structure:

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

         urn:iana:{RegistryName}:{EntryName}

      The keywords have the following meaning:

         (1) the "RegistryName" is a required ASCII string that
         conforms to the URN syntax (RFC 2141) and defines a
         particular registry maintained by the IANA.

         (2) the "EntryName" is a required ASCII string that
         conforms to the URN syntax (RFC 2141) and defines a
         particular entry in the relevant registry.

      The IANA is responsible for managing the assignment of both
      "RegistryName" and "EntryName" strings.

   Relevant Ancillary Documentation:

      Information about IANA registration procedures can be found
      on the IANA website and in RFC 5226.

   Identifier Uniqueness Considerations:

      The IANA ensures the uniqueness of all IANA URNs by checking
      RegistryNames and EntryNames against existing names for both
      registries and entries.  The IANA directly ensures the
      uniqueness of the assigned strings and does not assign
      secondary responsibility for management of any sub-trees.
      In no case will the resulting URNs be re-assigned.

   Identifier Persistence Considerations:

      Through its existing registration procedures, the IANA
      ensures that registrants provide clear documentation of
      the entries in IANA registries.

   Process of Identifier Assignment:

      The processes and procedures for identifier assignment are
      documented on the IANA website and in RFC 5226.

   Process for Identifier Resolution:

      The namespace is not currently listed with a Resolution
      Discovery System (RDS).  However, nothing about the namespace
      prohibits the future definition of appropriate resolution
      methods or listing with an RDS.

   Rules for Lexical Equivalence:

      No special considerations; the rules for lexical
      equivalence specified in RFC 2141 apply.

   Conformance with URN Syntax:

      No special considerations.

   Validation Mechanism:

      None specified.

   Scope:

      Global.

###