[urn] Re: Registration request for AR URN Namespace

Hi Peter,

No worries, we’ve discussed internally and we’re OK with the text that you’ve suggested to we’ve no added it to the registration form. Given this is likely our last revision, I’ve dropped the "v" reference in the filename as well.

Regards
Quoc

From: Peter Saint-Andre <[email protected]>
Sent: Saturday, 7 March 2026 00:11
To: Quoc Pham <[email protected]>
Cc: [email protected]; Sharon Jonnalagadda <[email protected]>
Subject: Re: [urn] Re: Registration request for AR URN Namespace

On 3/5/26 5: 34 PM, Peter Saint-Andre wrote: > On 3/5/26 11: 53 AM, Dale R. Worley wrote: >> "Quoc@ registry. godaddy" <Quoc=40registry. godaddy@ dmarc. ietf. org> writes: >>> Do you have an estimated update as to when we would
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd

On 3/5/26 5:34 PM, Peter Saint-Andre wrote:

> On 3/5/26 11:53 AM, Dale R. Worley wrote:

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

>>> Do you have an estimated update as to when we would expect a

>>> publication onto

>>> https://urldefense.com/v3/__https://www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml?__;!!Hj18uoVe_Lnx!vd0gsCUmZXxmGFH7GsDpwA_xTKi2dc05t7sXR2Ku4zm8RqE2wjX82uPsJ-EORtoJIoSrWeTGopnnJPMUJ8SdUEA$<https://urldefense.com/v3/__https:/www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml?__;!!Hj18uoVe_Lnx!vd0gsCUmZXxmGFH7GsDpwA_xTKi2dc05t7sXR2Ku4zm8RqE2wjX82uPsJ-EORtoJIoSrWeTGopnnJPMUJ8SdUEA$>

>>

>> "gdr_namespace_v5.txt" looks good to me.  I recommend we approve it.

>

> Agreed. My apologies if I have dropped the ball on this. Given that

> other review team members seem to have been comfortable with this

> request, I will proceed with IANA.



While performing my customary final review and cleanup on the

registration request before sending it to IANA, I noticed that the

completed template does not include a section on Resolution as required

by RFC 8141. My apologies for catching this so late in the process. If

the registrant does not envision resolution of GDR URNs, I would suggest

the following text:



###



Resolution:



   It is not foreseen that URNs within this namespace will undergo

   resolution and GoDaddy Registry does not plan to operate any

   resolution services for "gdr" URNs.



###



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-03-10

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,
  according to the following syntax:

  extension = 1*( ALPHA / DIGIT / "-" / "." / "_" / "~")

  
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:

  Using the "gdr" namespace to name the GoDaddy EPP extensions ensures
  that they do not clash with any EPP extensions defined by other
  organizations.


Resolution:

   It is not foreseen that URNs within this namespace will undergo
   resolution and GoDaddy Registry does not plan to operate any
   resolution services for "gdr" URNs.


Documentation:

  https://godaddyregistry.github.io/