More.. of the same (delays)

[squirrel]

From domainincite (http://domainincite.com/13994-new-gtlds-are-the-new-y2k-corp-and-home-are-doomed-and-everything-else-is-delayed)

First, .corp and .home are dead. These two strings have been categorized “high risk” by ICANN
[...]
Another 80% of the applied-for strings have been categorized “low risk”. ICANN has published a spreadsheet explaining which string falls into which category. Low risk does not mean they get off scot-free, however.

First, all registries for low-risk strings will not be allowed to activate any domain names in their gTLD for 120 days after contract signing.

Second, for 30 days after a gTLD is delegated the new registries will have to reach out to the owners of each IP address that attempts to query names in that gTLD, to try to mitigate the risk of internal name collisions.

This, as applicants will no doubt quickly argue, is going to place them under a massive cost burden.

But their outlook is considerably brighter than that of the remaining 20% of applications, which are categorized as “uncalculated risk” and face a further three to six months of delay while ICANN conducts further studies into whether they’re each “high” or “low” risk strings.

In other words, the new gTLD program is about to see its biggest shake-up since the GAC delivered its Advice in Beijing, adding potentially millions in costs and delays for applicants.


As per the spreadsheet referenced above (http://domainincite.com/docs/new-gtlds-proposed-class-05aug13-en.xlsx) all IDN TLDs have been classified as low-risk, thus an extra 120 days delay at a minimum before 2nd level domains can resolve.


PS : Verisign wins.

[Rubber Duck]

From domainincite (http://domainincite.com/13994-new-gtlds-are-the-new-y2k-corp-and-home-are-doomed-and-everything-else-is-delayed)




As per the spreadsheet referenced above (http://domainincite.com/docs/new-gtlds-proposed-class-05aug13-en.xlsx) all IDN TLDs have been classified as low-risk, thus an extra 120 days delay at a minimum before 2nd level domains can resolve.


PS : Verisign wins.

Maybe, but contract signing was never synonamous with delegation. Hasn't there always been a three to four month delay anyway?

Further, if there is no risk then there are no queries and hence no cost, unless there is natural type-in, in which case it is only Verisign that is going to get hammered. Seems fair to me.

[Rubber Duck]

http://newgtlds.icann.org/en/program-status/timelines

See link to programme dated: 18 July 2013

50 Days between contracting and delegation.

Then 30 Days Sunrise Notice.

Then 30 Days Sunrise Period.

So for typical TLD, this extra delay is 10 Days at most?

And Verisign is most definitely losing at the moment as they have not inked the contract.

[alpha]

http://newgtlds.icann.org/en/program-status/timelines

See link to programme dated: 18 July 2013

50 Days between contracting and delegation.

Then 30 Days Sunrise Notice.

Then 30 Days Sunrise Period.

So for typical TLD, this extra delay is 10 Days at most?

And Verisign is most definitely losing at the moment as they have not inked the contract.

Can't be.
The 120 day delay and above cannot run in parallel, else you risk worst case starting sunrise then finding a problem that the 120 day period has uncovered. Surely the above (delegation+) can't start until the 120 days has elapsed.

[TrafficDomainer]

It looks like it won't be until the middle of 2014 before we can actually activate and use .com idn.idn names.

Any other guess or prediction?

[Rubber Duck]

Can't be.
The 120 day delay and above cannot run in parallel, else you risk worst case starting sunrise then finding a problem that the 120 day period has uncovered. Surely the above (delegation+) can't start until the 120 days has elapsed.

What exactly is going to be uncovered by contract signing?

If anything is going to be discovered it is likely to be after activation, but in the best case scenario it would be during per delegation testing, which basically accounts for 50 days. If this is passed nothing further is going to happen of technical significance until activation.

[Drewbert]

Interesting to note that Verisign's Chinese IDN choices are absent from the base data (thus receive no traffic in the root)

大拿 xn--pssy2u
點看 xn--c1yn36f
点看 xn--3pxu8k

along with Afilias' .mobile (no surprise there)
移动 xn--6frz82g
and PIR's .org in Hindi
संगठन xn--i1b6b1a6a2e
and Chinese
机构体制 xn--tqq33ed31aqia (the short version 机构 gets traffic)

NO TRAFFIC FOR YOU! ADIOS MUCHACHOS!

[Drewbert]

Traffic rankings 2012:

.คอม xn--42c2d9a 29000
.ком xn--j1aef 14000
.орг xn--c1avg 4000
.公司 xn--55qx5d 3000 <---- CNNIC, not Verisign's
.网络 xn--io0a7i 2000 <---- CNNIC, not Verisign's
.كوم xn--fhbei 1000
.公益 xn--55qw42g 1000 (CNNIC)
.онлайн xn--80asehdb 1000 (CORE, contract signed)
.政务 xn--zfr164b 1000 (CNNIC)
.сайт xn--80aswg (CORE, contract signed)

Traffic rankings 2013:

.ком xn--j1aef 21000
.公司 xn--55qx5d 15000 <---- CNNIC, not Verisign's
.คอม xn--42c2d9a 14000
.网络 xn--io0a7i 9000 <---- CNNIC, not Verisign's
.орг xn--c1avg 4000
.政务 xn--zfr164b 4000 (CNNIC)
.公益 xn--55qw42g 3000 (CNNIC)
.сайт xn--80aswg 1000 (CORE, contract signed)
.онлайн xn--80asehdb 1000 (CORE, contract signed)
.كوم xn--fhbei 1000

So now we know which ones to expect instant traffic on, once this nightmare is finally over.

[squirrel]

Thanks for the summary Drewbert.

the figures indicate traffic to the top level domain over a 48 hour period https://www.dns-oarc.net/oarc/data/ditl

[TrafficDomainer]

Traffic rankings 2012:

.คอม xn--42c2d9a 29000
.ком xn--j1aef 14000
.орг xn--c1avg 4000
.公司 xn--55qx5d 3000 <---- CNNIC, not Verisign's
.网络 xn--io0a7i 2000 <---- CNNIC, not Verisign's
.كوم xn--fhbei 1000
.公益 xn--55qw42g 1000 (CNNIC)
.онлайн xn--80asehdb 1000 (CORE, contract signed)
.政务 xn--zfr164b 1000 (CNNIC)
.сайт xn--80aswg (CORE, contract signed)

Traffic rankings 2013:

.ком xn--j1aef 21000
.公司 xn--55qx5d 15000 <---- CNNIC, not Verisign's
.คอม xn--42c2d9a 14000
.网络 xn--io0a7i 9000 <---- CNNIC, not Verisign's
.орг xn--c1avg 4000
.政务 xn--zfr164b 4000 (CNNIC)
.公益 xn--55qw42g 3000 (CNNIC)
.сайт xn--80aswg 1000 (CORE, contract signed)
.онлайн xn--80asehdb 1000 (CORE, contract signed)
.كوم xn--fhbei 1000

So now we know which ones to expect instant traffic on, once this nightmare is finally over.

Thanks Drew. Interesting to see that Thai .คอม was number 1 in 2012 and that the traffic dropped by about half from 29,000 to 14,000. I know that idn.com is catching on in Thailand and speculate that less people are trying idn.คอม when they previously saw that such domains did not resolve and trying the hybrid idn.coms instead since they resolve with many Thai idn sites up and running now.

Russian .ком rise is interesting though so not sure how right my theory is and what else could have contributed to a deep plunge in Thai .คอม traffic.

[Drewbert]

Yes, I was wondering about that decrease in traffic.

Do any browsers self-correct/block to stop queries to non-existent TLD's?

[Drewbert]

Some interesting points made...

http://www.circleid.com/posts/20130806_the_long_gestation_and_afterlife_of_new_gtlds/

[squirrel]

The data points are 48hours so an increase/decrease is not necess. indicative of anything

[Drewbert]

Right. Good point. It may have been national "stay off the porn sites and hug your children day" or something.

[TrafficDomainer]

The data points are 48hours so an increase/decrease is not necess. indicative of anything

Thanks Squirrel for the clarification on the data point.

[squirrel]

Some interesting points made...

http://www.circleid.com/posts/20130806_the_long_gestation_and_afterlife_of_new_gtlds/

Are routers and resolvers really misconfigured at the moment ? I think not, it's just that they take advantage of inexisting TLDs. I wouldn't call this a misconfiguration that warrants fixing, update, sure, but fixing ??

...a report on the potential for confusion and misaddressing when someone's internal network names match the name for a new gTLD, and they have misconfigured their routers and/or DNS to the extent that someone typing in a new gTLD name might end up in the middle of someone else's network.
You'd think that if someone misconfigured their machinery it might be a good idea to get them to fix it, instead of reconfiguring the entire new gTLD program

That's blatant faulty thinking.

[nicenic]

Hi keyboard warriors ;)

Does anybody here on IDN Forums will attend the forthcoming ICANN Registrar Event (new gTLDs), 26-27 August 2013 in Westin Xiamen, China?

We were invited by both Registry of CNNIC and Founder of Zodiac Holdings, James Seng.