[urn] Re: Registration request for AR URN Namespace

Peter Saint-Andre <[email protected]> Tue, 10 Feb 2026 07:55:32 -0700
Newsgroups gmane.ietf.urn
Message-ID <[email protected]>
As the team lead, I'm just waiting a few days to see if other team 
members have any remaining concerns.

Peter

On 2/9/26 5:47 PM, [email protected] wrote:
> Huzzah! I wish that "ship it" is the official statement of approval, I 
> guess how long between now and our namespace is published onto https:// 
> www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml <https:// 
> www.iana.org/assignments/urn-namespaces/urn-namespaces.xhtml>?
> 
> Regards
> 
> Quoc
> 
> *From:*Peter Saint-Andre <[email protected]>
> *Sent:* Tuesday, 10 February 2026 03:00
> *To:* Quoc Pham <[email protected]>; Dale R. Worley <[email protected]>
> *Cc:* [email protected]; Sharon Jonnalagadda <[email protected]>
> *Subject:* Re: [urn] Re: Registration request for AR URN Namespace
> 
> Ship it! :-) On 2/8/26 8: 09 PM, Quoc@ registry. godaddy wrote: > Hi 
> Dale and Peter, > > Thank you both, I’ve made the updates and @Dale R. 
> Worley > <mailto: worley@ ariadne. com> I used your suggested rephrasing 
> (couldn’t > of
> 
> ZjQcmQRYFpfptBannerStart
> 
> *This Message Is From an External Sender *
> 
> This message came from outside your organization.
> 
> ZjQcmQRYFpfptBannerEnd
> 
> Ship it! :-)
> 
> On 2/8/26 8:09 PM, [email protected] <mailto:[email protected]> 
> wrote:
> 
>> Hi Dale and Peter,
> 
>> 
> 
>> Thank you both, I’ve made the updates and @Dale R. Worley 
> 
>> <mailto:[email protected] <mailto:[email protected]>> I used your 
> suggested rephrasing (couldn’t
> 
>> of said it better myself).
> 
>> 
> 
>> Please see the attached, hopefully this is the last revision.
> 
>> 
> 
>> Regards
> 
>> 
> 
>> Quoc
> 
>> 
> 
>> *From:*Dale R. Worley <[email protected] <mailto:[email protected]>>
> 
>> *Sent:* Wednesday, 28 January 2026 11:54
> 
>> *To:* Peter Saint-Andre <[email protected] <mailto:[email protected]>>
> 
>> *Cc:* Quoc Pham <[email protected] <mailto:[email protected]>>; 
> [email protected] <mailto:[email protected]>;
> 
>> [email protected] <mailto:[email protected]>; Sharon Jonnalagadda 
> <[email protected] <mailto:[email protected]>>
> 
>> *Subject:* Re: [urn] Re: Registration request for AR URN Namespace
> 
>> 
> 
>>> On 1/26/26 9: 55 PM, Quoc@ registry. godaddy wrote: >> Thank you for the clarity, we 
> 
>> only ever intent to set our extension to >> be made up if ALPHA, DIGIT, 
> 
>> hyphen and dot and now I fully understand >> the issue with US 7
> 
>> 
> 
>> ZjQcmQRYFpfptBannerStart
> 
>> 
> 
>> *This Message Is From an External Sender *
> 
>> 
> 
>> This message came from outside your organization.
> 
>> 
> 
>> ZjQcmQRYFpfptBannerEnd
> 
>> 
> 
>>> On 1/26/26 9:55 PM, [email protected] <mailto:[email protected]> 
> <mailto:[email protected] <mailto:[email protected]>> wrote:
> 
>> 
> 
>>>> Thank you for the clarity, we only ever intent to set our extension to 
> 
>> 
> 
>>>> be made up if ALPHA, DIGIT, hyphen and dot and now I fully understand 
> 
>> 
> 
>>>> the issue with US 7 bit ASCII. So if I was to include what you have 
> 
>> 
> 
>>>> listed in your emails, would that be acceptable (I know that you have 
> 
>> 
> 
>>>> tilde I your list but I guess we can keep that in there for our 
> 
>> 
> 
>>>> application in case)?
> 
>> 
> 
>> Peter Saint-Andre <[email protected] <mailto:[email protected] 
> <mailto:[email protected]%20%3cmailto:[email protected]>>> writes:
> 
>> 
> 
>>> That sounds good to me. The `unreserved` construct from RFC 3986 is 
> 
>> 
> 
>>> merely a convenience because it is well known. You can define your own 
> 
>> 
> 
>>> ABNF without the tilde if desired.
> 
>> 
> 
>> I agree with Peter here.  And getting a workable definition for
> 
>> 
> 
>> <extension> seems to be the only issue regarding the syntax section of
> 
>> 
> 
>> the registration.
> 
>> 
> 
>> There does seem to be a wording problem with the interoperability
> 
>> 
> 
>> section:
> 
>> 
> 
>>    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>".
> 
>> 
> 
>> I would phrase it something like:
> 
>> 
> 
>>    Using the "gdr" namespace to name the GoDaddy EPP extensions ensures
> 
>> 
> 
>>    that they do not clash with any EPP extensions defined by other
> 
>> 
> 
>>    organizations.
> 
>> 
> 
>> Dale
> 
>> 
> 

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