[urn] Re: Request to register urn:glue

Peter Saint-Andre <[email protected]> Fri, 6 Mar 2026 08:18:07 -0700
Newsgroups gmane.ietf.urn
Message-ID <[email protected]>
[dropping IANA for now while we work out the details]

On 3/4/26 2:31 PM, Michael Jones wrote:
> FYI, the registration request is now in the IANA Considerations section 
> of the published -07 draft at https://www.ietf.org/archive/id/draft- 
> ietf-spice-glue-id-07.html#name-urn-namespace-registration <https:// 
> www.ietf.org/archive/id/draft-ietf-spice-glue-id-07.html#name-urn- 
> namespace-registration>.

Overall this request seems unobjectionable in its conception.

However, I have some comments...

It's unclear to me why the I-D talks about "GLUE URIs" when they're 
really URNs (yes, URNs are URIs, but why not be more specific?).

Have the authors conferred with the LEI folks about the fact that now we 
have two different ways to represent Legal Entity Identifiers in URN form?

To my mind, the IANA Considerations section, along with the document as 
a whole, contains a number of small confusions about exactly what it is 
doing. For instance, Section 7.1 states:

    This specification establishes the IANA "GLUE Authority Identifier
    URN" registry creating a URN namespace for Authority Identifiers for
    GLobal Unique Enterprise (GLUE) Identifiers.

As far as I can see, that registry will contain authority identifiers 
and Section 7.1 does not request creation of a URN namespace - that's 
what you're doing in Section 7.2.

Similarly:

    Each entry registers the URN for an Authority Identifier within the
    "urn:glue:" namespace.  The organization responsible for the
    Authority Identifier is recorded.

No, it doesn't register a URN, it registers an Authority Identifier, 
which when preceded by the string "urn:glue:" and succeeded by the 
External Identifier results in a URN. You could consider the Authority 
Identifier to be a kind of sub-namespace, but that phrasing too could 
lead to confusion.

If the authors accept this concern, then they should make appropriate 
(but relatively small) changes throughout the document, but mainly in 
Section 7.1. I leave the details as an exercise for the authors.

Also:

    This specification registers the following URN in the IANA "Formal
    URN Namespaces" registry [IANA.URN] established by [RFC8141].

No, it "registers the following URN namespace" (see also above).

Precision is not unimportant in these matters.

Peter

_______________________________________________
urn mailing list -- [email protected]
To unsubscribe send an email to [email protected]