TLD Application System

The TLD Application System (TAS) is the official online application system implemented by the Internet Corporation for Assigned Names and Numbers for the new gTLD program. Applicants are required to complete the registration on the system to be able to submit and manage their applications. The TAS registration is the first step in the application process and it is open from January 12 to March 29, 2012. Applicants need to follow three steps which include: filling out an applicant profile, legal review and payment of a non-refundable deposit of $US 5000. Access to TAS will not be granted until the deposit is confirmed by ICANN. The TAS will send e-mail updates and notifications to the applicants and they can also track the progress of every

application they submitted.[1]

According to ICANN senior vice president Kurt Pritz, every TAS account can store as much as 50 applications. As of February 13, 2012, he reported that there were already 100 applicants for new gTLD. [2] On March 2012, ICANN reported that there are 556 registered users in the system and it is expected to receive more than 1 thousand new gTLD applications. [3]

New gTLD consultant FairWinds Partners reported that it is processing an average of 2.7 applications per client. [4]

Reports on Technical Failures

FairWinds Partners reported that some applicants encountered technical failures using the TLD Application System and were not able to complete the profile registration. TAS was un-functional for two days. To resolve the issue, ICANN announced that there will be a schedule TAS systems maintenance during Sunday mornings from 12:00 midnight to 2:00 in the morning UTC. [5] The complete schedule for TAS maintenance is available here

On February 2, Jeff Neuman and Ken Hanson executives from Neustar tweeted that their applications were missing on TAS. Neumann's tweeted, “Check your applications in TAS. Reports of missing applications- Our application 4 .Neustar is 1 of them. TAS also lost our “unique” ID which we got upon paying initial 5k. We need ID to pay remainder, fill out app & see all apps.”[6] ICANN explained that the system encountered a display issue, which was resolved after two hours. All data were visible and no missing information. [7]

On April 12, 2002, ICANN's Chief Operating Officer Akram Atallah issued a statement acknowledging that a a possible glitch in the TLD application system software caused a limited number of users saw the file names and user names of other users in some instances. He said that ICANN decided to shut down the system until April 17 to protect the data of applicants. Atallah also said that ICANN is investigating how the problem happened and necessary measures will be done to resolve the situation. [8]

Following Atallah's statement, Kevin Murphy of DomainIncite reported that an applicant claimed that he noticed that a file from another applicant was attached to his application on April 6 and immediately reported the problem to ICANN. The applicant said, "I could infer the applicant/string… based on the name of the file." However the actual contents of the file was not visible. The TAS problem ignited different speculations and questions within the internet community particularly the how long will the TAS suffer from vulnerability, who among the applicants saw others applications and if some applicants took advantage of the situation and filed competing bids.[9] [10]

ICANN also announced that TAS will be offline temporarily and the extension of the application window until April 20. [11] [12]

Apart from the extension of the application window, ICANN also informed journalists that the problem was not caused by a cyber attack, no application data were lost and the TAS system is expected to open on April 18. According to .nxt speculated that the situation maybe considered as a "non-denial-denial category and ICANN was following the second path dealing with a suspected hack." [13] [14]

On April 14, 2012, ICANN issued another statement related to the TAS problem. The internet governing body identified that a report on March 19 was the only incident related to the technical glitch. [15]

On April 23, 2012, ICANN announced that it was able to identify all applicants affected by the TAS failure and the testing to fix the system is running smoothly. In addition, it also announced the postponement of the scheduled publication of all the applied new gTLD strings on April 30. [16] Two days after, ICANN released an update informing applicants that the TAS will re-open on April 27. [17] ICANN continuously provides update to the internet community regarding the progress of the testing to resolve the system. On April 27, the internet governing body reported that based on its analysis there are still limited number of affected applicants and tests to improve the system is being conducted continuously. ICANN promised to continue to provide updates. [18]

On May 2, 2012, ICANN reported that there were 1268 registered users and around 95,000 file attachments were available when the system went offline. It estimated 455 incidents wherein a file name and user name was possibly seen by another applicant. It also identified that most probably the file names and user names of 105 applicants were viewed by another applicant and 50 applicants possibly viewed the file names and user names of one or more applicants. ICANN assured the internet community that it is continuously working on improving the system to fix the technical problem. [19] On May 4, ICANN informed that it received approximately $350 million dollars application fees and the payments from 214 potential applicants that were registered before the March 29 cut off were not yet received. In addition, the internet governing body also reported that notifications were being sent to applicant informing them if they were affected by the software. The notification process is expected to be completed by May 8 and the schedule to re-open the TAS will be announced. [20]

Statement from Rod Beckstrom

On April 30, 2012, ICANN CEO Rod Beckstrom stated that he is hoping that the technical failure will be fixed before his term as ICANN CEO expires and pass the responsibility to hi successor during the ICANN 44 meeting in Prague on June 29, 2012. He said, "I’d like to see us obviously get the technical issues resolved, notify applicants, reopen the window and publish the strings before I pass the baton in Prague. That’s not a commitment at this point in time, it’s an indication as CEO that it’s absolutely my intention to push for a timely resolution of this issue… If we can get things done sooner, then the sooner the better." [21]

ANA's Reaction to the TAS Technical Problem

Dan Jaffe, executive vice president of ANA reacted that the TAS technical problem demonstrated that the new gTLD expansion program is moving too quickly. He said, "It's another warning signal to go slower, and make sure you have worked out all the glitches before you roll out a new system." Furthermore, he emphasized that the technical glitch on the system showed that it is impossible for ICANN to adequately police the new domain names and any sizable increase of TLDs will result to the proliferation of cybersquatting, phishing and impostor websites. He warned that if the internet will be undermined, it will result to a very unfavorable effect. [22]

Furthermore, ANA's president Bob Liodice issued a press release requesting the Department of Commerce (DOC) and the National Telecommunications and Information Administration (NTIA) to urge ICANN to hire an independent IT expert to investigate the TAS technical problem. [23]

Reaction from Cong. Bob Goodlatte

Cong. Bob Goodlatter, chairman of the House Judiciary subcommittee expressed his concerns regarding the TAS technical problem. He said that he is worried if ICANN won't be able to resolve the problem appropriately, many people around the world might push aside ICANN and advocate for a more direct governmental control on the internet. He also suggested that ICANN "may have undertaken more than they may be able to responsibly manage." [24]

Jeff Moss Explains TAS Technical Failure

ICANN’s Vice President and Chief Security Officer Jeff Moss described TAS technical problem in an interview with Brad White and how it is being resolved by ICANN. He explained that shutting down the system is the safest action to protect the applicants. Please watch the attached video for further details.

<videoflash>8jLhHCwzX0w</videoflash>

References