[urn] Re: Registration request for AR URN Namespace

Hi Peter,

Ah yes, sorry about that, full xmlns should have been written xmlns="urn:gdr:params:xml:ns:variant-1.0

Regarding the other point, what I mean with best effort is that when we develop our own extensions, we will check the IANA repository and the published EPPs the ensure that we avoid naming any new extensions to be the same.

E.g. RFC3915 is xmlns="urn:itef:params:xml:ns:rgp-1.0. If for some reason we have our own "RGP" extension where it’s an abbreviation for something completely different and plan to use xmlns="urn:gdr:params:xml:ns:rgp-1.0 … we will look to change that to something else (specifically rgp-1.0).

Thank you for your point on uniqueness, I wanted to express that we will take care in what extensions we create so they are "similar" to others that already exist and create confusion. OK I will remove that text.

Here it is attached and hopefully it makes sense, also I do appreciate the "wordiness", it’s been an educational process for both Sharon and I.

Regards
Quoc

From: Peter Saint-Andre <[email protected]>
Sent: Thursday, 22 January 2026 01:02
To: Quoc Pham <[email protected]>
Cc: [email protected]; Sharon Jonnalagadda <[email protected]>
Subject: Re: [urn] Re: Registration request for AR URN Namespace

On 1/20/26 10: 00 PM, Quoc@ registry. godaddy wrote: > Hi Peter, > > Question: Is 32 characters enough to represent these variants > (presumably they > > will be A-labels, not U-labels)? > > Answer: variant isn’t a place
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd

On 1/20/26 10:00 PM, [email protected]<mailto:[email protected]> wrote:

> Hi Peter,

>

> Question: Is 32 characters enough to represent these variants

> (presumably they

>

> will be A-labels, not U-labels)?

>

> Answer: variant isn’t a place holder of a label, it’s the extension name

> itself, for instance the variant extension names space would be

> xmlns="urn:ar:params:xml:ns:variant-1.0"



Thanks for clarifying that!



(Presumably changing 'ar' to 'gdr' there.)



> Statement: Thankfully, uniqueness applies to the full URN, so if you

> guarantee uniqueness within the 'gdr' namespace then we don't need to

> worry about the uniqueness of extension strings across other namespaces.

>

> Response: Do you want me to remove the statement about uniqueness?



It seems to me that you might be able to remove the statement about the

global uniqueness of specific portions of 'gdr' URNs (e.g., the

<variant> and <kvlist> extensions), unless this is important to you and

to the ecosystem of registrars.



What we care about most is the GodDaddy Registrar's commitment to

ensuring the uniqueness of URNs that you create. My impression is that

you won't be creating hundreds or thousands of URNs. Instead, you're

going to create a pretty limited number of URNs (maybe a few dozen?)

which represent "extensions" that are specific to your registry system.

In that case, guaranteeing uniqueness should be fairly straightforward.



To be clear, the phrase "best effort" in your current text caused

concern for me, because I think GoDaddy Registrar can do better than

that for a few dozen extensions. If the phrase "best effort" applies to

the uniqueness of extension names (not full URNs) across the universe of

registrars, then that is perhaps nice to have for GodDaddy and the

registrar industry, but from a URN perspective that doesn't really

matter to us. :-)



Does this make sense? Sorry to have replied in such a wordy fashion.



Peter

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

Namespace Registration for GoDaddy Registry EPP Extensions

Namespace Identifier:  

  gdr

Version: 

  1.0

Date: 

  2026-01-22

Registrant: 

  GoDaddy Registry.
  Email: [email protected]
  Address: 100 S. Mill Ave, Suite 1600, 
  Tempe, Arizona, 85281, USA
  Web URL: https://registry.godaddy/

Purpose:

  GoDaddy Registry is a Registry Service Provider (RSP) for Generic Top Level 
  Domains (gTLDs) and Country Code Top Level Domains (ccTLDs). Certain TLDs 
  have specific and special requirements where the standard Extensible 
  Provisioning protocol (EPP) RFCs related
  are unable to satisfy. GoDaddy Registry enables these requirements to be
  supported by developing extensions that can be used by Registrars to
  facilitate the exchange of data between the Registrar and Registry in 
  support of these requirements.
  
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.
  
Assignment:

  Assignment is self assigned by GoDaddy Registry. These extensions will work
  only when used directly with the GoDaddy Registry Domain Name Registry
  System. Each extension will be unique and provide its own distinct
  functionality.

Security and Privacy:
  There are no additional security considerations beyond the security model
  described in RFC5730 defining the security gates with operating an EPP 
  service for Registrar to Registry communication.

Interoperability:

  The "gdr" namespace ensures that there is no clash with any of the published
  EPP RFCs extenions which follow the syntax 
  "urn:gdr:params:xml:ns:<extension>".
 
Documentation:

  https://godaddyregistry.github.io/