Hi James, I agree. For the purposes of moving through the ICANN RSP RST, and not to pollute the EPP Extension Registry with numerous copies of the same thing, we will just reference the Identity Digital's submission.
I have a few reservations based on the fact their Legal Disclaimer basically copyrights a previously open standard, but given there is a grant to use it for EPP purposes we accept that potential risk. As for the new IDN extension(s) that folks are working on, we will be more than happy to review and help out where we can. Thanks, Don CLASSIFICATION:CONFIDENTIAL -----Original Message----- From: Gould, James <[email protected]> Sent: August 15, 2025 7:21 AM To: Don Slaunwhite <[email protected]>; [email protected]; [email protected] Cc: [email protected] Subject: Re: [regext] Re: [EXT] Re: idnmap extension Don, Based on my review of the registered Identity Digital idnmap extension, it's a duplicate of the IETF idnmap-02, down to the XML namespace and XML schema. Identity Digital can confirm this. If there are implementations of idnmap-02, then there is an existing matching registration in the EPP Extension Registry, registered by Identity Digital. This assumes that a registration by any RSP will meet the ICANN requirement and that the RSPs can stick with idnmap-02 / idnmap - Identity Digital in the meantime. The preliminary recommendation from the IDN Extensibility and Extension Tiger Team is to consolidate and standardize the IDN extensions (IDN Language Tag, IDN Mapping, IDN Table Mapping, Related Domain, Strict Bundling, and the new Domain Variant). REGEXT could look to create one mechanism for identifying and validating the needed IDN table Id or language (e.g., IDN Table), passing the IDN table id or language in a create (e.g., IDN Language Tag and IDN Mapping), and managing the related IDN variants (e.g., Related Domain, Strict Bundling, and Domain Variant) to reduce the duplication in the EPP Extension Registry. I see the need for more than one EPP extension to address the IDN requirements. Please review the writeup done thus far at https://docs.google.com/document/d/1WR00oB43XZCDqD0zvRvRajuWAq_9wQ3c0RrFKlGC3So on the referenced IDN extensions as well as the other EPP extensions being analyzed to make recommendations for RPP and recently to make recommendations for EPP. Thanks, -- JG James Gould Fellow Engineer [email protected] <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/[email protected]> 703-948-3271 12061 Bluemont Way Reston, VA 20190 Verisign.com <http://verisigninc.com/> On 8/14/25, 4:44 PM, "Don Slaunwhite" <[email protected] <mailto:[email protected]>> wrote: Caution: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Folks, I'd like to provide a bit of background as to why I believe this is coming up. CIRA is going through ICANN RSP evaluation for Round 2. (and so is SIDN) As part of that, one of the requirements is that your IDN EPP extension must be registered with the IANA EPP Extension Registry. https://secure-web.cisco.com/1ivyCrKCsRl4RGL_OCe0RUgTAhtHhx34H9oNZCga0tApjKxF4u_vqJjcq06QyAIT87I3IplDmlgypuoZcPnkPpl5ZRTjKdTt8XV9jBvsAFJN33HTDOW0pSjUY-LY4CDoTAt7bOIWE75Wfku7wVL-lTrsMMBQheVY0pU4Wxk4Iw5Nbz-ssrfP1UACsNCig9BDUIjlIDnP9glOyD-BnUkqwNtqKlVFoMAMVv5MmtXanbAHGsxHW67WlvpWboP2he2bhReecSed8-sHbctDpODz_qg6orMIiltDvtfMMKPK_qpI/https%3A%2F%2Fwww.iana.org%2Fassignments%2Fepp-extensions%2Fepp-extensions.xhtml <https://secure-web.cisco.com/1ivyCrKCsRl4RGL_OCe0RUgTAhtHhx34H9oNZCga0tApjKxF4u_vqJjcq06QyAIT87I3IplDmlgypuoZcPnkPpl5ZRTjKdTt8XV9jBvsAFJN33HTDOW0pSjUY-LY4CDoTAt7bOIWE75Wfku7wVL-lTrsMMBQheVY0pU4Wxk4Iw5Nbz-ssrfP1UACsNCig9BDUIjlIDnP9glOyD-BnUkqwNtqKlVFoMAMVv5MmtXanbAHGsxHW67WlvpWboP2he2bhReecSed8-sHbctDpODz_qg6orMIiltDvtfMMKPK_qpI/https%3A%2F%2Fwww.iana.org%2Fassignments%2Fepp-extensions%2Fepp-extensions.xhtml> Now for years I think many organizations, CIRA included, have been using the draft idnmap-02 as our basis for our IDN EPP implementation. https://secure-web.cisco.com/1vEGI6v-pbRx4y8WfBe7T7t4tUGbzS2BiNO_st9cZc7hHb-B2p8UY-DPe5Po2Uheig8SwWEbuTdr2KXjydMRyaeYGG8MGhiVuOv458yM7b_t5MjWxU4DTzIiPsUf4mUwNBiwoe5hqHpFWxJPbKCHku3vyP11qIGwrSuEgUu9z8f4JgK5YfdhHYJcdmPhM9WhGQ0Ym0lpvUzW-EyuiEGu2Z7Xvepw5tCrHTOa0o6DaYCVzdJXiIc9hsqbtvGQubnABC5ut3ShaYkMi_5i8grBZ89LN1OWo-KdhQ0V723BAYx8/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-eppext-idnmap-02 <https://secure-web.cisco.com/1vEGI6v-pbRx4y8WfBe7T7t4tUGbzS2BiNO_st9cZc7hHb-B2p8UY-DPe5Po2Uheig8SwWEbuTdr2KXjydMRyaeYGG8MGhiVuOv458yM7b_t5MjWxU4DTzIiPsUf4mUwNBiwoe5hqHpFWxJPbKCHku3vyP11qIGwrSuEgUu9z8f4JgK5YfdhHYJcdmPhM9WhGQ0Ym0lpvUzW-EyuiEGu2Z7Xvepw5tCrHTOa0o6DaYCVzdJXiIc9hsqbtvGQubnABC5ut3ShaYkMi_5i8grBZ89LN1OWo-KdhQ0V723BAYx8/https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-eppext-idnmap-02> In previous RST testing for ICANN we just referenced the DRAFT RFC and everything was fine. But now ICANN is saying It must be registered in the EPP Extension Registry. And I assumed earlier on that at some point that DRAFT made it to RFC and was registered. But found out it wasn't. In order to move forward with Round 2 RST Testing, we need to be able to reference an EPP Extension in the table. We are in the process of writing up a new CIRA IDN EPP Extension which is derived from idnmap-02 and submit it for entry into the registry. Much like Identity Digital did. But realistically from a global point of view, it would be nice if the original DRAFT would move forward into full RFC and be submitted. Or even if you can submit the draft itself. (I'll be honest I'm not sure exactly what the rules are there.) That way we don't end up with a bunch of Backend Registry Operator specific EPP extensions (all based off of idnmap-02) in the registry, just to meet this requirement. Thoughts? Thanks, Don CLASSIFICATION:CONFIDENTIAL -----Original Message----- From: Maarten Wullink <[email protected] <mailto:[email protected]>> Sent: August 14, 2025 9:58 AM To: Francisco Obispo <[email protected] <mailto:[email protected]>> Cc: REGEXT Working Group <[email protected] <mailto:[email protected]>> Subject: [EXT] [regext] Re: idnmap extension Hi Francisco, As one of the authors, can you maybe elaborate a bit on why this document never reached RFC status? Would you mind if I or somebody else continues this document with the goal of getting it published as an RFC? Best, Maarten > Op 13 aug 2025, om 15:57 heeft Francisco Obispo <[email protected] > <mailto:[email protected]>> het volgende geschreven: > > Hi Marteen, > > Tucows Registry Services (TRS) is actively using it. > > Best, > > On 13 Aug 2025, at 8:33, Maarten Wullink wrote: > >> Hi, >> >> Has any other registry implemented the idnmap [1] extension? >> It’s currently only an expired draft, but we use it and are considering >> pushing it toward RFC status. >> Knowing of other deployments would help make the case. >> >> - >> Maarten >> >> >> >> [1] >> https://secure-web.cisco.com/1vEGI6v-pbRx4y8WfBe7T7t4tUGbzS2BiNO_st9c >> Zc7hHb-B2p8UY-DPe5Po2Uheig8SwWEbuTdr2KXjydMRyaeYGG8MGhiVuOv458yM7b_t5 >> MjWxU4DTzIiPsUf4mUwNBiwoe5hqHpFWxJPbKCHku3vyP11qIGwrSuEgUu9z8f4JgK5Yf >> dhHYJcdmPhM9WhGQ0Ym0lpvUzW-EyuiEGu2Z7Xvepw5tCrHTOa0o6DaYCVzdJXiIc9hsq >> btvGQubnABC5ut3ShaYkMi_5i8grBZ89LN1OWo-KdhQ0V723BAYx8/https%3A%2F%2Fd >> atatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-eppext-idnmap-02 >> <https://secure-web.cisco.com/1vEGI6v-pbRx4y8WfBe7T7t4tUGbzS2BiNO_st9 >> cZc7hHb-B2p8UY-DPe5Po2Uheig8SwWEbuTdr2KXjydMRyaeYGG8MGhiVuOv458yM7b_t >> 5MjWxU4DTzIiPsUf4mUwNBiwoe5hqHpFWxJPbKCHku3vyP11qIGwrSuEgUu9z8f4JgK5Y >> fdhHYJcdmPhM9WhGQ0Ym0lpvUzW-EyuiEGu2Z7Xvepw5tCrHTOa0o6DaYCVzdJXiIc9hs >> qbtvGQubnABC5ut3ShaYkMi_5i8grBZ89LN1OWo-KdhQ0V723BAYx8/https%3A%2F%2F >> datatracker.ietf.org%2Fdoc%2Fhtml%2Fdraft-ietf-eppext-idnmap-02> >> >> >> >> _______________________________________________ >> regext mailing list -- [email protected] <mailto:[email protected]> To >> unsubscribe send an email to [email protected] >> <mailto:[email protected]> _______________________________________________ regext mailing list -- [email protected] <mailto:[email protected]> To unsubscribe send an email to [email protected] <mailto:[email protected]> _______________________________________________ regext mailing list -- [email protected] <mailto:[email protected]> To unsubscribe send an email to [email protected] <mailto:[email protected]> _______________________________________________ regext mailing list -- [email protected] To unsubscribe send an email to [email protected]
