Re: IANA URN registration enquiry - Rules for Lexical Equivalence of NSS part

Peter Saint-Andre <stpeter@stpeter.im> Wed, 20 April 2011 03:34 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: urn-nid@ietfc.amsl.com
Delivered-To: urn-nid@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 5A96DE06AB for <urn-nid@ietfc.amsl.com>; Tue, 19 Apr 2011 20:34:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.452
X-Spam-Level:
X-Spam-Status: No, score=-102.452 tagged_above=-999 required=5 tests=[AWL=0.147, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id olohc7bl0Wwd for <urn-nid@ietfc.amsl.com>; Tue, 19 Apr 2011 20:34:51 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by ietfc.amsl.com (Postfix) with ESMTP id F25F9E0660 for <urn-nid@apps.ietf.org>; Tue, 19 Apr 2011 20:34:50 -0700 (PDT)
Received: from squire.local (dsl-175-253.dynamic-dsl.frii.net [216.17.175.253]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 4816A40D51; Tue, 19 Apr 2011 21:38:26 -0600 (MDT)
Message-ID: <4DAE5458.70309@stpeter.im>
Date: Tue, 19 Apr 2011 21:34:48 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: DTG Registration <registration@dtg.org.uk>
Subject: Re: IANA URN registration enquiry - Rules for Lexical Equivalence of NSS part
References: <AANLkTi=wsemN2=NcFZ9Rgki5kuPg2Ykd-z81d7SdK+CR@mail.gmail.com> <AANLkTin53VMG9VF0DXfcH4FeudWCbxVP4ofycopntNmY@mail.gmail.com> <A81C894800C709429D1973719CF7D3360243074D@sbs.dtg.org.uk> <A81C894800C709429D1973719CF7D336024B8319@sbs.dtg.org.uk>
In-Reply-To: <A81C894800C709429D1973719CF7D336024B8319@sbs.dtg.org.uk>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms060408030306010303090704"
Cc: Dave Walton <dave.walton@echostar.com>, urn-nid@apps.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: Wed, 20 Apr 2011 03:34:52 -0000

On 4/19/11 3:25 AM, DTG Registration wrote:
> Hello,
> 
> When declaring rules for lexical equivalence of NSS part, is this
> section valid if only the URN NID is being registered with IANA?

I assume you're referring to Appendix A of RFC 3406. Because the entire
text of that document is about the registration of a namespace
identifier with IANA (or, to be precise, "the processes by which a
collection of identifiers satisfying certain constraints can become a
bona fide URN namespace by obtaining a NID"), it's not clear to me what
you mean by your question "is this section valid if only the URN NID is
being registered with IANA?" Only the NID is ever registered with IANA
because specific URNs under that NID are issued by the administrative
entity that registers the NID in the first place. However, part of the
process of registering a NID is specifying the rules for lexical
equivalence. As with the other requirements of RFC 3406, defining the
rules for lexical equivalence will help the administrative entity to
clarify its processes and procedures regarding URN issuance, and also
will help developers of software for handling the issued URNs to
implement consistent parsing algorithms.

Did I misunderstand your question?

Peter

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