[urn] Re: Registration request for AR URN Namespace
[email protected] (Dale R. Worley) Tue, 27 Jan 2026 19:53:42 -0500
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <[email protected]> |
> On 1/26/26 9:55 PM, [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]> 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]