TLD Application System: Difference between revisions

Line 15:

[http://domainincite.com/new-gtld-applications-briefly-vanish-after-glitch/ New gTLD applications briefly vanish after glitch]</ref>

On April 12, 2002, ICANN's Chief Operating Officer, [[Akram Atallah]] issued a statement, just hours before TAS was scheduled to close as per the set application window, acknowledging that a a possible glitch in the TLD application system software caused a limited number of users to see the file names and user names of other users. He said that ICANN decided to shut down the system until April 17 to protect applicants' information. Mr. Atallah also said that ICANN is investigating how the problem happened and that necessary measures would be undertaken to resolve the situation. <ref>

On April 12, 2002, ICANN's Chief Operating Officer, [[Akram Atallah]] issued a statement, just hours before TAS was scheduled to close as per the set application window, acknowledging that a possible glitch in the TLD application system software caused a limited number of users to see the file names and user names of other users. He said that ICANN decided to shut down the system until April 17 to protect applicants' information. Mr. Atallah also said that ICANN is investigating how the problem happened and that necessary measures would be undertaken to resolve the situation. <ref>

[http://www.icann.org/en/news/announcements/announcement-3-12apr12-en.htm Statement on TLD Application System]</ref>

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 were not visible. The TAS problem ignited different speculations and questions within the Internet community, particularly the how long will TAS suffer from vulnerability, who among the applicants saw others applications and if some applicants took advantage of the situation and filed competing bids.<ref>

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 were not visible. The TAS problem ignited different speculations and questions within the Internet community, particularly the how long will TAS suffer from vulnerability, who among the applicants saw others applications and if some applicants took advantage of the situation and filed competing bids.<ref>

[http://domain.incite.com/icann-knew-about-tas-security-bug-last-week/ ICANN knew about TAS security bug last week]</ref><ref> [http://domainincite.com/its-worse-than-you-thought-tas-security-bug-leaked-new-gtld-applicant-data/ It’s worse than you thought: TAS security bug leaked new gTLD applicant data]</ref>

Line 31:

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 until April 30. <ref>[http://www.icann.org/en/news/announcements/announcement-2-23apr12-en.htm TAS Interruption Update, April 23]</ref> Two days after, ICANN released an update informing applicants that the TAS will re-open on April 27. <ref>[http://newgtlds.icann.org/en/announcements-and-media/announcement-25apr12-en TAS Interruption - Update (25 April 2012)]</ref> ICANN continuously provided 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 are being conducted continuously. ICANN again delayed the opening of the TAS system but promised to continue to provide updates.<ref>[http://newgtlds.icann.org/en/announcements-and-media/announcement-27apr12-en TAS Interruption - Update (27 April 2012)]</ref>

On April 30, 2012, [[ICANN CEO]] [[Rod Beckstrom]] stated that he is hoping that the technical failure will be fixed before his term expired and he passes the job to his successor during the [[ICANN 44]] meeting, which was to be held 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."'' <ref>

On April 30, 2012, [[ICANN CEO]] [[Rod Beckstrom]] stated that he is hoping that the technical failure will be fixed before his term expired and he passes the job to his successor during the [[ICANN 44]] meeting, which was to be held 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."'' <ref>

[http://domainincite.com/beckstrom-breaks-tas-bug-silence-says-big-reveal-could-be-as-late-as-prague/ Beckstrom breaks TAS bug silence, says Big Reveal could be as late as Prague]</ref>

@@ Line 15: / Line 15: @@
 [http://domainincite.com/new-gtld-applications-briefly-vanish-after-glitch/ New gTLD applications briefly vanish after glitch]</ref>
-On April 12, 2002, ICANN's Chief Operating Officer, [[Akram Atallah]] issued a statement, just hours before TAS was scheduled to close as per the set application window, acknowledging that a a possible glitch in the TLD application system software caused a limited number of users to see the file names and user names of other users. He said that ICANN decided to shut down the system until April 17 to protect applicants' information. Mr. Atallah also said that ICANN is investigating how the problem happened and that necessary measures would be undertaken to resolve the situation. <ref>
+On April 12, 2002, ICANN's Chief Operating Officer, [[Akram Atallah]] issued a statement, just hours before TAS was scheduled to close as per the set application window, acknowledging that a possible glitch in the TLD application system software caused a limited number of users to see the file names and user names of other users. He said that ICANN decided to shut down the system until April 17 to protect applicants' information. Mr. Atallah also said that ICANN is investigating how the problem happened and that necessary measures would be undertaken to resolve the situation. <ref>
 [http://www.icann.org/en/news/announcements/announcement-3-12apr12-en.htm Statement on TLD Application System]</ref>
-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 were not visible. The TAS problem ignited different speculations and questions within the Internet community, particularly the how long will TAS suffer from vulnerability, who among the applicants saw others applications and if some applicants took advantage of the situation and filed competing bids.<ref>
+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 were not visible. The TAS problem ignited different speculations and questions within the Internet community, particularly the how long will TAS suffer from vulnerability, who among the applicants saw others applications and if some applicants took advantage of the situation and filed competing bids.<ref>
 [http://domain.incite.com/icann-knew-about-tas-security-bug-last-week/ ICANN knew about TAS security bug last week]</ref><ref> [http://domainincite.com/its-worse-than-you-thought-tas-security-bug-leaked-new-gtld-applicant-data/ It’s worse than you thought: TAS security bug leaked new gTLD applicant data]</ref>
@@ Line 31: / Line 31: @@
 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 until April 30. <ref>[http://www.icann.org/en/news/announcements/announcement-2-23apr12-en.htm TAS Interruption Update, April 23]</ref> Two days after, ICANN released an update informing applicants that the TAS will re-open on April 27. <ref>[http://newgtlds.icann.org/en/announcements-and-media/announcement-25apr12-en TAS Interruption - Update (25 April 2012)]</ref> ICANN continuously provided 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 are being conducted continuously. ICANN again delayed the opening of the TAS system but promised to continue to provide updates.<ref>[http://newgtlds.icann.org/en/announcements-and-media/announcement-27apr12-en TAS Interruption - Update (27 April 2012)]</ref>
-On April 30, 2012, [[ICANN CEO]] [[Rod Beckstrom]] stated that he is hoping that the technical failure will be fixed before his term expired and he passes the job to his successor during the [[ICANN 44]] meeting, which was to be held 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."'' <ref>
+On April 30, 2012, [[ICANN CEO]] [[Rod Beckstrom]] stated that he is hoping that the technical failure will be fixed before his term expired and he passes the job to his successor during the [[ICANN 44]] meeting, which was to be held 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."'' <ref>
 [http://domainincite.com/beckstrom-breaks-tas-bug-silence-says-big-reveal-could-be-as-late-as-prague/ Beckstrom breaks TAS bug silence, says Big Reveal could be as late as Prague]</ref>