IDN extensions - what effects on existing

[netfleet]

Now that ICANN has stated that from next year they'll be allowing IDN extensions (as part of their general relaxation on extensions) isn't this going to render all idn.com, idn.tv etc obsolete?

Obviously this announcement, if it comes to fruition will have far reaching consequences for all domainers but isn't it going to blow a hole in all existing IDN domain values?

I don't know much about them but I would have through that an IDN domain with a Latin/Western extension sort of defeats the purpose....

 

[jnorthct]

Well one would think that native users would prefer extensions in their own language. But there is also an argument that the introduction of a myriad of new language-specific extensions will actually strengthen IDN.com, as it will become the only universal standard for IDNs. Further, the new extensions will draw greater publicity to IDN generally, which may benefit IDN.com. So we really have to wait and see what happens.

Of course, none of these developments will affect those with Latin IDNs (French, Spanish, Portuguese, Turkish, Vietnamese, etc.).

 

[Billidn]

Now that ICANN has stated that from next year they'll be allowing IDN extensions (as part of their general relaxation on extensions) isn't this going to render all idn.com, idn.tv etc obsolete?

Obviously this announcement, if it comes to fruition will have far reaching consequences for all domainers but isn't it going to blow a hole in all existing IDN domain values?

I don't know much about them but I would have through that an IDN domain with a Latin/Western extension sort of defeats the purpose....

Not at all. First point most international domainers would tell you is that .com is the most "famous" tld brand in the world and recognizable to all internet users in all languages. Surprisingly, many would like to see their idns stay as .com (English), but the overwhelming majority on the various forums seem to want IDNs to get aliased to the "equivalent" .com or .net in the various languages via Verisigns DNAME proposal.

Right now it is "wait and see" if idn.com is indeed "aliased" to its equivalent languages later this year or early next year and also if owners of idn.com will get BOTH idn.com and its equivalent idn.idn in the various languages. You have to remember that idn.com has been registered and held by many domainers since 2000'. It is very clear in the various ICANN decisions and working paper documents that registrars are fully protected for their equivalent extensions in various languages so Verisign's .com, JPRS .jp, Germany's .de, CCNIC .cn etc. are pretty much protected territory for them.

IDN.com have never been a better investment now that things are getting cleared up, and ICANN has budgeted tens of millions for the rollout of new idn.idn extensions etc. (google "ICANN 2009 budget" for the report).

Existing idn.com, idn.net, idn.jp, idn.cn are all clearly going to be top of class, joined with new idn.idn extensions that can be applied for by registrars. Since most .cc are in existance, most of those will alias to their native languages, or offer "both". Here is the latest proposal from the Japanese Registry for aliasing .jp. This is from May 2008:

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

And here is Verisigns proposal for handling idn.com, idn.net etc via aliasing:

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

 

[rhys]

As Bill correctly points out, JPRS discussion to alias .JP with the kanji equivalent extension means that values of .JP IDN's have suddenly increased in value. This is good news for those of us who own substantial portfolio of Japanese