[urn] Re: Registration request for AR URN Namespace

Hi Dale,

Regarding an index, we’ll that on board and we can rearrange that page for sure. I am not quite following your explanation about the syntax, which is likely a lack of understanding on my side. Doing a little googling, the construct is:

urn:<Namespace Identifier>:<Namespace Specific String>

So would it be fair to state that based on the above format, our syntax would be:
<Namespace Identifier> = gdr:params:xml
<Namespace Specific String> = a US 7 bit ASCII string that represents the extension, for example "variant", "kvlist"
Full example: urn:gdr:params:xml:variant-1.0

Regards
Quoc


From: Dale R. Worley <[email protected]>
Sent: Thursday, 22 January 2026 13:46
To: Quoc Pham <[email protected]>
Cc: [email protected]; Sharon Jonnalagadda <[email protected]>
Subject: Re: [urn] Re: Registration request for AR URN Namespace

"Quoc@ registry. godaddy" <Quoc=40registry. godaddy@ dmarc. ietf. org> writes: > Yes, the URL that you are referring to will be the place. Once "gdr" > is registered, we will be making updates to all of our extensions > (which are right
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd

"[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> writes:

> Yes, the URL that you are referring to will be the place. Once "gdr"

> is registered, we will be making updates to all of our extensions

> (which are right now using "ar") to use "gdr" and registering them

> with IANA. We have one in progress which is awaiting the approval the

> "gdr" registration.



I just looked at https://urldefense.com/v3/__https://godaddyregistry.github.io/doc/index.html__;!!Hj18uoVe_Lnx!oMLHj18dpfx_1vyXP02R9yEoV44Oxok7FQ7X0TpTcJ_WfNIPOezqpGLe8o2509ooGYWuvBsxGjYSt2YzH7TY$<https://urldefense.com/v3/__https:/godaddyregistry.github.io/doc/index.html__;!!Hj18uoVe_Lnx!oMLHj18dpfx_1vyXP02R9yEoV44Oxok7FQ7X0TpTcJ_WfNIPOezqpGLe8o2509ooGYWuvBsxGjYSt2YzH7TY$>

again.  Since it's a web page linking to a couple of dozen web pages,

it's hard to get an overall sense for it.  But it seems to me that it

would be much better as documentation for the URNs if there was an index

that was a table of URNs (or URN groups, perhaps) to the pages that

defined how they are to be used.



Though I don't thing that should be gating for the namespace

registration.



But I do think the syntax description in the registration needs to be

made clearer.



    Syntax:



      urn:gdr:params:xml:ns:<extension>, where <extension> is the epp command

      extension. some examples include but not limited to:

      * <variant>: managing variants of internationalized domain names

      * <kvlist>: supplying a key value list to represent additional domain name

      registration details

      all extensions extend the base epp commands described in rfc5730.

      all extensions will be in us 7bit ascii and not exceed 32 characters.



The first sentence is good, but there's no syntax specification for

<extension>.  The following sentences suggest that "<variant>" and

"<kvlist>" could be values for the nonterminal <extension>, but that

makes no sense:



    urn:gdr:params:xml:ns:<variant>



is not a URN.



It would also help if the capitalization and punctuation were

standardized.



Dale

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