Governments and Country-Code Managers' Interest in the Fast Track Process - IDN Forums

alpha · #1 (**permalink**) 10th February 2009, 10:41 PM

Posted today on ICANN website

http://www.icann.org/en/announcement...10feb09-en.htm

Drewbert · #2 (**permalink**) 11th February 2009, 03:21 AM

Very interesting.

Although someone will have to explain to me why Sweden wants Yiddish.

Fka200 · #3 (**permalink**) 11th February 2009, 03:57 AM

Quote:

Originally Posted by Drewbert

Very interesting.

Although someone will have to explain to me why Sweden wants Yiddish.

I was thinking the same thing...

phio · #4 (**permalink**) 11th February 2009, 04:56 AM

yep, wiki has some info on the yiddish in Sweden.

Rubber Duck · #5 (**permalink**) 11th February 2009, 08:52 AM

If ICANN cannot see the frustration in some of those responses, they must have a hide like a Rhino!

Rubber Duck · #6 (**permalink**) 11th February 2009, 08:54 AM

Quote:

Originally Posted by phio

yep, wiki has some info on the yiddish in Sweden.

A more important question might be why US didn't!

phio · #7 (**permalink**) 11th February 2009, 09:53 AM

Korean and Chinese would be great idncctlds for the US. Sure would separate a lot of pages that user here would be searching for. Arabic and Japanese would also work here, not sure about thai and vietnamese.

Drewbert · #8 (**permalink**) 12th February 2009, 07:00 AM

Interesting to see Turkey wanting in on the fasttrack process.

Maybe they're going to gun for .tü ?

Also Iran's comments:

xn--mgba3a4f16a (visually identical with Arabic xn--mgba3a4fra)

and:

"We are ready:have been registering IDN's under the above TLD since Sept 2005".

Hey, at least someone's brave enough to admit it.

Note also that Israel is going for the full ".israel" xn--4dbrk0ce for their IDN ccTLD rather than a 2 letter code.

Rubber Duck · #9 (**permalink**) 12th February 2009, 07:06 AM

Quote:

Originally Posted by Drewbert

Interesting to see Turkey wanting in on the fasttrack process.

Maybe they're going to gun for .tü ?

Also Iran's comments:

xn--mgba3a4f16a (visually identical with Arabic xn--mgba3a4fra)

and:

"We are ready:have been registering IDN's under the above TLD since Sept 2005".

Hey, at least someone's brave enough to admit it.

Note also that Israel is going for the full ".israel" xn--4dbrk0ce for their IDN ccTLD rather than a 2 letter code.

Iran was never going to capitulate on Bush's demands for full disclosure over IDN!

dave_5 · #10 (**permalink**) 13th February 2009, 04:46 PM

Any thought on Hebrew .com’s?

Since there are no news regarding aliasing, how do you think ccTLD in Hebrew would affect the value of Hebrew.com’s?

Thanks!

Drewbert · #11 (**permalink**) 13th February 2009, 05:57 PM

IDN ccTLD's will help IDN.com due to user awareness. THe market will expand.

bwhhisc · #12 (**permalink**) 14th February 2009, 04:22 AM

Quote:

Originally Posted by dave_5

Any thought on Hebrew .com’s? Since there are no news regarding aliasing, how do you think ccTLD in Hebrew would affect the value of Hebrew.com’s? Thanks!

There is some language in the GNSO documents to the effect that their is an informal agreement with Verisign not to upstage idn.idn prior to its release by moving ahead and aliasing .com (prior to idn.idn release). Verisign has been mum on the overall subject of aliasing but seems logical that would be an eventual step for .com and .net. They had outlined a proposed system in a Dec. 05 report on "DNAME equivalent for mapping idns".