Originally Posted by sarcle
They'll listen when Verisign speaks. Verisign needs to play offense now. They can't afford to sit and let country codes make it first in the IDN.IDN namespace.
Dnaming will solve having to have an extension go through a verification process that has to be approved by Icann. It's the only way Verisign can hold a firm grip on the .com namespace and not lose out on native people registering only their country IDN.IDN when the flood-doors open Nov 16.
I myself am still shocked that Verisign hasn't sent a press release discussing in detail how they plan to acheive this. Or maybe they are silently waiting for Dec. 21, 2012.
Wrong. Verisign has been keeping quite because they know the only thing that can sink them is opening their big mouth. There has always been a risk that the natives wouldn't want them walking all over their turf, but they understood the IP position from the start and decided that they would deny the opposition a focus by staying quiet.
This really is quite sad, because not only can IDN not be considered separately but try to reorganize constituencies at this time will only kick IDN gTLDs further into the long grass, and for that reason alone it cannot happen. More importantly, however, is that introduction of IDN gTLDs cannot be considered separately. Taking an IDN in Arabic will effectively reserve the English equivalent an vis-versa. No Arabic TLD is going to get through the process without an English equivalent because those trying to discuss it just would not be able to function without such an equivalent. We do it all the time. We use the English translation to tell people what it means, ICANN is going to do exactly the same, because even if they were all foreigners they are going to be different foreigners.
This is, however, quite positive because it will make the case for a Fast Track for gTLD even stronger, even if the outcome is not what Khalid envisages.