TAS to reopen May 22. Big Reveal on for Prague?

Kevin Murphy, May 9, 2012, 10:39:53 (UTC), Domain Policy

ICANN’s bug-plagued TLD Application System will reopen on May 22 and close on May 30, according to a statement just issued by chief operating officer Akram Atallah.

The dates, which are only “targets”, strongly suggest that that the Big Reveal of all new gTLD applications is going to happen during the public meeting in Prague in late June.

If ICANN still needs two weeks to collate its application data before the reveal, we’re looking at June 14, or thereabouts, as the earliest possible reveal date.

But that’s just ten days before ICANN 44 officially kicks off, and I think it’s pretty unlikely ICANN will want to be distracted by a special one-off event while it’s busy preparing for Prague.

For the Big Reveal, my money is on June 25.

Atallah also said this morning that all new gTLD applicants have now been notified whether they were affected by the TAS bug, meaning ICANN has “met our commitment to provide notice to all users on or before 8 May”.

That said, some applicants I spoke to this morning, hours after it was already May 9 in California, said they had not received the promised notifications. But who’s counting?

The results of ICANN’s analysis of the bug appear to show that no nefarious activity was going on.

“We have seen no evidence that any TAS user intentionally did anything wrong in order to be able to see other users’ information,” Atallah said.

ICANN has also discovered another affected TAS user, in addition to the 50 already disclosed, according to Atallah’s statement.

Tagged: , , , , , , ,

Comments (2)

  1. Ash says:

    I’m astonished that ICANN can claim they have met their obligations when I know for a fact that they did not notify some applicants until the 9th of May. Also, the notifications are really only an update, rather than a final confirmation that you have/have not been affected.

  2. John Smith says:

    Reminder to ICANN: Instead of building a complex system prone to bugs, next time use a tried and true entry system:

    eMAIL!

Add Your Comment