[urn] Re: Registration request for AR URN Namespace

Peter Saint-Andre <[email protected]> Tue, 13 Jan 2026 10:55:47 -0700
Newsgroups gmane.ietf.urn
Message-ID <[email protected]>
Hi Quoc,

Thank you for the updated registration request.

I have two comments:

(1) In the "Syntax" section, please specify the syntax of the 
<extension> construct. What is the length, can it contain non-ASCII 
characters (suitably escaped), does it conform to one of the ABNF rules 
from RFC 8141 or RFC 3986, etc.?

(2) In the "Assignment" section, it would be nice to say something about 
guaranteeing uniqueness (presumably the GoDaddy Registry will make sure 
that <extension> constructs are unique).

Everything else looks good to me. Thanks for your flexibility about the 
namespace ID.

Peter

P.S. For ease of reference, I've pasted the registration request below.

###

Namespace Registration for GoDaddy Registry EPP Extensions

Namespace Identifier:

   gdr

Version:

   1.0

Date:

   2026-01-13

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.

Assignment:

   Assignment is self assigned by GoDaddy Registry. These extensions 
will work
   only when used directly with the GoDaddy Registry Domain Name Registry
   System.

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:ietf:params:xml:ns:<extension>".

Documentation:

   https://godaddyregistry.github.io/

###

On 1/12/26 11:38 PM, [email protected] wrote:
> Hi Peter (Happy New Year to you as well as whoever see this email),
> 
> Attached is the "gdr" namespace details.
> 
> Regards
> 
> Quoc
> 
> *From:*Peter Saint-Andre <[email protected]>
> *Sent:* Friday, 19 December 2025 01:37
> *To:* Quoc Pham <[email protected]>
> *Cc:* [email protected]; Sharon Jonnalagadda <[email protected]>
> *Subject:* Re: [urn] Re: Registration request for AR URN Namespace
> 
> Thanks, Quoc. URNs are forever, so there's no hurry. :-) On 12/17/25 
> 10: 09 PM, Quoc@ registry. godaddy wrote: > Hi Dale and Peter, > > Thank 
> you for your feedback, I am preparing an update, sorry for the delay. > 
>  > Regards >
> 
> ZjQcmQRYFpfptBannerStart
> 
> *This Message Is From an Untrusted Sender *
> 
> You have not previously corresponded with this sender.
> 
> ZjQcmQRYFpfptBannerEnd
> 
> Thanks, Quoc. URNs are forever, so there's no hurry. :-)
> 
> On 12/17/25 10:09 PM, [email protected] 
> <mailto:[email protected]> wrote:
> 
>> Hi Dale and Peter,
> 
>> 
> 
>> Thank you for your feedback, I am preparing an update, sorry for the delay.
> 
>> 
> 
>> Regards
> 
>> 
> 
>> Quoc
> 
>> 
> 
>> *From:*Dale R. Worley <[email protected] <mailto:[email protected]>>
> 
>> *Sent:* Thursday, 11 December 2025 03:30
> 
>> *To:* Quoc Pham <[email protected] <mailto:[email protected]>>
> 
>> *Cc:* [email protected] <mailto:[email protected]>; Sharon Jonnalagadda 
> <[email protected] <mailto:[email protected]>>
> 
>> *Subject:* Re: [urn] Registration request for AR URN Namespace
> 
>> 
> 
>> "Quoc@ registry. godaddy" <Quoc=40registry. godaddy@ dmarc. ietf. org> 
> 
>> writes: > ar_namespace_v1. txt As Peter noted (but mis-spoke), RFC 8141 
> 
>> requies that namespace names must have at least three characters: 3. It 
> 
>> MUST be more than two characters
> 
>> 
> 
>> ZjQcmQRYFpfptBannerStart
> 
>> 
> 
>> *This Message Is From an External Sender *
> 
>> 
> 
>> This message came from outside your organization.
> 
>> 
> 
>> ZjQcmQRYFpfptBannerEnd
> 
>> 
> 
>> "[email protected] <mailto:[email protected]> 
> <mailto:[email protected]%20%3cmailto:[email protected]%3e>"
> 
>> <[email protected] 
> 
>> <mailto:[email protected] 
> <mailto:[email protected]>>> writes:
> 
>> 
> 
>>> ar_namespace_v1.txt
> 
>> 
> 
>> As Peter noted (but mis-spoke), RFC 8141 requies that namespace names
> 
>> 
> 
>> must have at least three characters:
> 
>> 
> 
>>      3.  It MUST be more than two characters long, [...]
> 
>> 
> 
>> In regard to the application:
> 
>> 
> 
>>    Syntax:
> 
>> 
> 
>>    urn:ar:params:xml:ns:<extension>, where <extension> is the EPP command
> 
>> 
> 
>>    extension that delivers on specific requirements. All extensions 
> 
>> extend on
> 
>> 
> 
>>    the base EPP commands described in RFC5730.
> 
>> 
> 
>> It would be helpful if the acronym "EPP" was expanded at its first use
> 
>> 
> 
>> so the casual reader would understand what the overall purpose is.
> 
>> 
> 
>> The phrase "delivers on specific requirements" sounds like
> 
>> 
> 
>> marketing-speak.  What does it mean?
> 
>> 
> 
>> You need to provide the syntax for the nonterminal "extension".
> 
>> 
> 
>> Dale
> 
>> 
> 
>> 
> 
>> _______________________________________________
> 
>> urn mailing list -- [email protected] <mailto:[email protected]>
> 
>> To unsubscribe send an email to [email protected] <mailto:[email protected]>
> 

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