- Impact
- 1
At T.R.A.F.F.I.C. Tina Dam, Senior Director of IDNs at ICANN spoke on gTLDs in general and on IDN gTLDs. She noted yesterday’s success with 4 .IDN ccTLDs moving forward in the Fast Track process.
When asked about whether there will be a Fast Track gTLD process, Tina said that it has been discussed at length but she doesn’t see it happening.
So what does this mean for non-latin gTLDs? She did not say if she does not see it happening in the near future or at all. In any case, ccTLDs in Russian, Arabic, Chinese markets will have a big head start, this is more or less clear by now. Besides, I personally don't even see the need for aliasing of existing com/net idn.ascii to idn.idn. Russian, Chinese and arabs will do perfectly well with their ccTLD or may be another Idn.idn gTLD besides com/net. I understand the desire of people who hold large portfolios of those to have it their way but this is probably the last reason ICANN will take into consideration.
On the other hand, latin gTLD (Spanish, French etc) has proven to be a safe bet since they do not require any fast track or alising (if this ever going to happen to non-latins at all). They are already functional, do not need aliasing since com/net/org etc in latins is com/net/org and inclusion of Spanish gTLD domain TarjetasDeCrédito.com (Credit Cards) into Traffic auction proves that domaining community sees these as already having investment value. As far as non-latins, time will show. So far, the situation with them is still unclear at best - and market does not like uncertainty.
So far the approach of Icann seems logical. It is need based. With Latin idn gTLD it is making already existing domains work 100% with correct orthography. With ccTLD is to allow countries to have their respective extensions in their languages.
The motive for com/net idn.ascii>idn.idn is very weak, not need based and purely speculative. This is why I don't see it as ICANN priority even if it's possible technically.
When asked about whether there will be a Fast Track gTLD process, Tina said that it has been discussed at length but she doesn’t see it happening.
So what does this mean for non-latin gTLDs? She did not say if she does not see it happening in the near future or at all. In any case, ccTLDs in Russian, Arabic, Chinese markets will have a big head start, this is more or less clear by now. Besides, I personally don't even see the need for aliasing of existing com/net idn.ascii to idn.idn. Russian, Chinese and arabs will do perfectly well with their ccTLD or may be another Idn.idn gTLD besides com/net. I understand the desire of people who hold large portfolios of those to have it their way but this is probably the last reason ICANN will take into consideration.
On the other hand, latin gTLD (Spanish, French etc) has proven to be a safe bet since they do not require any fast track or alising (if this ever going to happen to non-latins at all). They are already functional, do not need aliasing since com/net/org etc in latins is com/net/org and inclusion of Spanish gTLD domain TarjetasDeCrédito.com (Credit Cards) into Traffic auction proves that domaining community sees these as already having investment value. As far as non-latins, time will show. So far, the situation with them is still unclear at best - and market does not like uncertainty.
So far the approach of Icann seems logical. It is need based. With Latin idn gTLD it is making already existing domains work 100% with correct orthography. With ccTLD is to allow countries to have their respective extensions in their languages.
The motive for com/net idn.ascii>idn.idn is very weak, not need based and purely speculative. This is why I don't see it as ICANN priority even if it's possible technically.
Last edited:
) because you have registered few idn.ascii in those languages. This is the only reason you think .com is an asset.
