[urn] Re: Registration request for AR URN Namespace
| Newsgroups | gmane.ietf.urn |
|---|---|
| Message-ID | <PH0PR02MB9364B142382D8E5446BA7EC1BD6BA@PH0PR02MB9364.namprd02.prod.outlook.com> |
Hi Dale, Done! Please refer to the attached and hopefully "send it". Regards Quoc From: Dale R. Worley <[email protected]> Sent: Tuesday, 17 February 2026 14:21 To: Quoc Pham <[email protected]> Cc: [email protected]; [email protected]; Sharon Jonnalagadda <[email protected]> Subject: Re: [urn] Re: Registration request for AR URN Namespace "Quoc@ registry. godaddy" <Quoc@ registry. godaddy> writes: > The Key Value example that I provided is a extension we intend to > submit to allow for additional data to be recorded against domain > names. For example a registered ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. ZjQcmQRYFpfptBannerEnd "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> writes: > The Key Value example that I provided is a extension we intend to > submit to allow for additional data to be recorded against domain > names. For example a registered business number. So the values are the > Key (for the attribute) and the value for, well the value supplied by > the client. > > We don’t have an intention in setting a key value in the URN itself. > > So … it will be: > > urn:gdr:params:xml:ns:variant-1.0 > urn:gdr:params:xml:ns:kvlist-1.0 > > (sorry I released I may have posted an incorrect example in the past > where the "ns" was missing from the full URN.). > > With that clarification, is version 4 of the document acceptable in > its current form? > > Or should we update it to: > > extension = 1*( ALPHA / DIGIT / "-" / "." / "_" / "~") Definitely update to the latter -- it gives the syntax definition of <extension>, which the registration needs to do. Dale _______________________________________________ urn mailing list -- [email protected] To unsubscribe send an email to [email protected]
gdr_namespace_v5.txt
(text/plain, 2.5 KB)
Namespace Registration for GoDaddy Registry EPP Extensions Namespace Identifier: gdr Version: 1.0 Date: 2026-02-09 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, the syntax will follow the unreserved construct as follows: unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~" 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. Documentation: https://godaddyregistry.github.io/