So...you see some value in idn.idn, but idn.com is "even more worthless with this announcement". I guess you did not read the fine print.
You can read the ICANN transcript below, and the words of ICANN CEO Rod Beckstrom's about idn.com moving to become idn.idn.
This is not something new, the agreements to alias idn.com, etc to idn.idn between ICANN, GNSO, ccNSO, GAC etc were agreed long ago.
So for all thee doubters and naysayers about existing gTLD's move forward to IDN.IDN status...ICANN's Board transcript of Oct 30 is posted below.
http://sel.icann.org/meetings/seoul2...30oct09-en.txt
CEO Rod Beckstrom's Remarks:
ROD BECKSTROM: Thank you, Peter. I'd just like to express my appreciation to all those across the open Internet ecosystem who have
worked for many, many years to make this possible. And especially not only to the members of the ICANN community, but to the members of the Internet Engineering Task Force, the IETF, some of whom have worked for over a decade on this issue.
And this represents today one small step for ICANN, and the IETF, but it represents a very important and significant step for half the
world of Internet users. Those who use non-Latin scripts and their own language. This helps us live up to our shared goals of: One world, one Internet, everyone connected. Now, in people's own script.
And this first step allows them to use their own domain names in their own languages, but only for the country code domains, so
instead of dot Korea, they can have dot -- the set of Hangul symbols or, rather, symbols that represent Korea for them -- and this is an
important step. And yet there's many people around the world that would like to have the equivalents of the Latin TLDs such as dot com, dot net, dot org, and others in their own native scripts as well. This is an important next step that we need to continue working on. We, as a community, have not yet reached consensus on the final resolution of those other issues, but we have a moral responsibility in what we do for the public interest to push that forward. Otherwise, we are prejudicing the global domain name system against half of the world whose native languages are in those other scripts.
So I hope that to fulfill our obligation to act in the public interest, which we recently reaffirmed by signing the Affirmation of Commitments, that we will move forward swiftly and professionally and with due consideration to bring those issues to a closure, so that people in Thailand, in Korea, in India, and all over the world can truly use the Internet in their own script for their domain name needs. Thank you.
Last edited by bwhhisc; 11-07-2009 at 05:35 AM.
ICANN has been answering some questions regarding aliasing existing idns by saying that many decisions are being made directly between the various "registrars".
Negotiated over the last 2 years was agreements that neither the gtlds or the cctlds would "disadvantage" one another. So it seems that the "fair' solution would be that they are aliased to .idn (com/jp, com/cn, etc) all within a short window.
At least the hard work is over after nearly a decades and .idn is finally going to become reality over the next year. Cheers to those domainers who have been sticking to and renewing since 2000'.
For idn.idn, I heard the extension will spell out ".com" or ".net" in the foreign script, so if for example, the actual domain name means "apple" in the foreign language with a ".com" extension, will the page redirect to the English apple.com? Or will there now be plenty of apple.com's in many languages? What if they spell out the word "apple" (which probably means nothing in the native language), will that redirect them to apple.com?
the company does not own the fruitThe apple is the pomaceous fruit of the apple tree, species Malus domestica in the rose family Rosaceae. It is one of the most widely cultivated tree fruits.
(check apple.org)
the translations and transcriptions will not be automatically redirected
they must be registered
There are plenty of threads regarding this subject. It is a worthy investment if you can get your hands on them... The good ones were taken years ago and with idn.idn aliasing the future looks promising to idn holders.
If I'm not mistaken, this is the first time they're releasing idn.idn domains so the good ones can't possibly be taken yet. As for idn.coms, I'm not sure they will be worth too much b/c if people can just type in the full domain in their native language, why would they take the time to write the domain name in their language, then switch to English for the extension (.com)? Perhaps I'm missing something?
The domains will be aliased to .idn. You can see the aliased domains already for CNNIC by doing a whois there. CNNIC has just been waiting years on Icann to implement this. .cn already resolves to it's .idn counterpart within China.
For example lets say I own newspaper.cn in IDN. Here are the variants that I already own and are reserved for me at the registry.
报纸.cn
报纸.中国
报纸.中國
報紙.中国
報紙.中國
報紙.cn
The same thing will be done with .com .net and the rest. Verisign has been working closely with China who has perfected this method of aliasing.
So they are available to the public. They just aren't live yet. Well outside of China anyways. Nov. 16th is coming fast!
All prices are valid for 72 hours.
The first part is incorrect in a number of cases particularly in China where idn.cn owners already own the variants as mentioned by Sarcie and most of the decent names have long gone.
IDN.com has two different camps where one thinks .com is and always will be king and others who think like you and see natives typing wholly in their own language- time will tell.
where can you register these idn.idn and more importantly..how do you with an english keyboard?
Bookmarks