ICANN has indicated that it will reveal the list of applied-for TLDs before its Prague meeting. The second of ICANN's 3 yearly international meeting officially opens on Monday 25 June.
ICANN will publish details of its new gTLD timetable, which includes the date of the "reveal day", on May 29. But new gTLD watchers should expect the big reveal to happen sometime during the week of June 18.
That same week may also be the start of the allocation process for the first batch of TLD applications that will be considered by ICANN. A 500 TLD limit exists for ICANN to evaluate applications, and as there are currently more than 2,200 applications expected, batching is a cert.
ICANN will be using a digital timestamp system to determine which applicants go in the first batch of 500. The system, dubbed "digital archery", requires applicants to select a timeslot and then log on to an ICANN website to try and hit a button as close to the selected timeslot as possible.
ICANN is targeting 22 May 2012 as the intended reopening date for the TLD Application System. It is anticipated that the system would remain open for five business days and close on 30 May. This takes account of the 28 May Memorial Day holiday in the United States.
We took TAS offline following a technical glitch that may have allowed some users to see some file names and user names of other users. We have seen no evidence that any TAS user intentionally did anything wrong in order to be able to see other users' information.
We have met our commitment to provide notice to all users on or before 8 May 2012 by sending out notifications today.
The large majority of users are unaffected by the glitch. We continue to review the extensive database of system logs and system traffic, and any new and relevant information that emerges from this analysis will be shared with applicants in a timely way.
Even as late as yesterday, 7 May 2012, our packet-level research uncovered a new set of instances (in addition to those previously announced) where another applicant might have viewed a set of system-generated file names. It is possible that further analysis will also show that some of the parties that we have notified were not affected, but notice was provided out of an abundance of caution.
We thank everyone for your patience and apologize for the inconvenience the delay has caused.