.JP Registry: DNAME aliasing for idn.idn?

I read this May 4, 2008 release from the Japan Registry Services entitles "DNAME Issues Regarding IDN TLD
Implementation".

For much of the last year only the term "aliasing" has been used by ICANN staffers, Tina Dam in particulary for the possiblity of converting idn.com, idn.net, idn.jp, idn.tv etc to also alias as idn.idn (equivalents).

Can someone from ICANN shed some light on what is going on with DNAME (solution proposed by Verisign), and also with the options for alising of .com etc. into the new idn.idn space.

Now that testing is done, and idn.idn are cueing up for major language releases in the forseeable future, are the various registrars... JPSR, CNNIC, Verisign etc. now open to begin to alias their gTLDs and ccTLDs into .idn should they choose to do so?

https://www.centr.org/main/4329-CTR/version/default/part/AttachmentData/...

Comments

Aliasing for idn.com, idn.net, idn.jp to equivalent as idn.idn.

Any news out of Cairo meeting towards the DNAME proposals or other alisaing options that might be provided to Verisign or JPRS for aliasing .com, .net, or .jp to the equivalent .idn?

Verisign published their DNAME proposal for mapping back in 2005, JPRS (Japan Registry) published their study on aliasing .jp earlier this year.

Are there any holdups or approvals required for them to move ahead via aliasing to move into the idn.idn space over the next year?

When can Verisign alias idn.com to idn.idn (.com equivalent)?

Hi Tina, thanks for the response. Can you provide any links to tests or trials regarding DNAME that indicate the issues with this proposal for aliasing. I have only read that other solutions were competing, and a final answer had not been selected. For those readers interested, below is the link to the DNAME aliasing proposal by Verisign:

http://icann.org/announcements/proposal-dname-equivalence-mapping-tld-12...

Also, are the registrars like Verisign, JPRS etc. free to alias .com, .net, .jp to the equivalent .idn versions or offer "both" versions to their customers if they choose. What further tests or clearances from ICANN are required for them to implement .idn? Thanks as always for being helpful and providing your insights, Bill

Will get back...

I have asked Tina Dam - ICANN's IDN Director - to get back to this query as soon as she has a second.

Kieren

DNAME and aliasing

Hi bwhhisc, thanks for your comment on DNAME and alaising. The reason I have been very careful about discussing alaising is that the question of aliasing is what needs to be defined and answered. Before we fully understand what people believe aliaising means and what kind of functionality they tie to aliasing, we really cannot talk about a solution.

However, I understand that as we are moving close to the finalization of the process for introduction of new gTLDs and the IDNC fast track for introduction of "IDN ccTLDs" the question about aliasing might be re-opened. And so it looks like we may need to let some things run in parallel. For that reason I talked to some individual from the technical community about their view on this topic. And whether it might be feasible to test how DNAME would work as an aliasing mechnism between two TLDs. The initial result was surprisingly not positive. I admit that I had expected it to work, but it did not in a laboratory environment. Some more discussions are going on in technical fora and it is possible that we will go ahead and examine the test further. However, this is where we stand today. Now, it is possible that there are other solutions to aliasing than DNAME that needs to be tried out. I believe it would be good to try to have/find a standard solution to aliasing functionality so that if aliasing is used then it is done the same way across all the TLDs using it.

I will raise the question again in technical fora and see if they have examined things further and found other results and/or what potentially needs to be done for doing so.

Tina

Update to DNAME Aliasing in the DNS

This draft on DNAME is dated May 2nd, 2008 and latest information I could find. Did not conclude from this that DNAME is not a possible solution.

http://www.ietf.org/internet-drafts/draft-ietf-dnsext-rfc2672bis-dname-1...

I have read other suggestions for aliasing of IDNs either by putting the punycode directly into the root, or via database aliasing/mirroring at the various TLD registries.

Still curious about my original question....
Can Verisign (.com, .net etc.) and JPRS (.jp) move ahead to create idn.idn with names in their registries at this time if they so choose?

Thanks again Tina and Kieren for fielding our questions.
Bill