Quote:
|
Originally Posted by Assassin
ICANN is projecting to introduce IDN.IDN in a ccTLD frame-work, meaning that there will be no forwarding of IDN.IDN back to a corresponding IDN.com, or any such scenario to save ChineseIDN.LatinCom speculators.
|
You obviously have NOT been keeping up with what is going on with aliasing.
IDN.com can apply for aliasing to the equivalent of idn.idn (.com)
The new IDN.IDN can NOT become anything strikingly confusingly or similar to anything that is already out there, so they can't squat on .com, .net equivalents.
Their is only going to be 1 idn.idn in the first round for each country/ lanaguage.
It is most likely going to be an area or country identifier. It does not effect .com.
Things are not sorted out yet, but if you had been reading up on what is going on you would know .com is in fine shape and decisions to move to idn.idn are up to Verisign when they are ready.