Archives For Digital Archery

After nearly a full week of debates, discussions, meetings, and even a handful of thinly veiled jabs from community members, the ICANN Board officially pronounced Digital Archery dead and gone today at around 2:35 PM, Prague time, during the Public Forum here at the ICANN Public Meeting.

Yes, there was applause. Continue Reading…

In the few days since ICANN made the decision to suspend the Digital Archery system for batching applications, discussions about next step have, not altogether unsurprisingly, focused not on how to improve Digital Archery, but alternatives to replace it entirely. Perhaps most significant is the groundswell that seems to be forming around the idea of tossing out batching completely, and instead evaluating all applications at once. Continue Reading…

Yesterday, ICANN made waves by announcing that it had suspended the Digital Archery process for batching. In the public statement, ICANN stated, “The primary reason is that applicants have reported that the timestamp system returns unexpected results depending on circumstances.” The decision came when the Digital Archery process was a mere five days away from closing – and still, only 20 percent of applicants had recorded a timestamp, or fired their digital “arrows” at that point, amounting to about 386 of the 1,930 applications. Continue Reading…

Yesterday, ICANN issued another announcement about the batching process for new gTLD applications. For the most part, it’s nothing we don’t already know (and haven’t already blogged about), but peppered throughout the announcement are some interesting new things to consider.

For one, we know that applicants will log back into the TLD Application System (TAS) to select and hit their target time. We now know that applicants will also be able to use a testing feature to gauge the response time of their system and, in some cases, their trigger finger. This can be helpful for those applicants who are still trying to decide whether to use a technology solution to hit their target time, or to just hit the button manually. Continue Reading…

So now we know how ICANN’s Digital Archery process will work, and have a very rough idea of when that process will take place. On the surface, it may seem like having the process start before before Reveal Day is not a big deal – perhaps ICANN is even trying to make up for some time lost during the month-long TAS delay. But there could be some really serious ramifications to the timing of this process. And like so many other aspects of the New gTLD Program, these ramifications result from ICANN keeping applicants in the dark. Continue Reading…

It’s been more than two months since ICANN first announced its plans for how to deal with the “batching” issue – how it will order new gTLD applications for evaluation – and yet there still seems to be rampant confusion around the basics of the process and its implications.

Let’s start with the basics: what exactly does ICANN mean by “batching”? Well, according to the New gTLD Applicant Guidebook, if ICANN receives substantially more than 500 new gTLD applications, which we know with certainty that it will, it will divide those applications into groups in order to evaluate them. The first batch will consist of 500 applications, and subsequent batches will each contain 400 applications. In an announcement on May 4, ICANN stated that the TLD Application System (TAS) held 2,091 applications, plus 214 potential applications for which the payments had yet to be reconciled. Assuming that all 2,305 applications make it through, there will be a total of six batches. Continue Reading…