6,681
edits
Changes
Jump to navigation
Jump to search
Line 18:
Line 18: + +
no edit summary
Overall, the initial reaction to the publishing of the Interisle report took the form of outrage by many New gTLD applicants, especially since the delays could potentially add on millions of dollars in costs to the applicants on their way to delegating a new gTLD. In the months following the report's publishing, the ICANN community mobilized to create alternative solutions to the Name Collision issue, as well as argue whether or not the issue was serious enough to delay delegation of 100s of gTLDs.<ref>[http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-annex-1-07oct13-en.pdf ICANN.org] Retrieved 05 Feb 2014</ref>
Overall, the initial reaction to the publishing of the Interisle report took the form of outrage by many New gTLD applicants, especially since the delays could potentially add on millions of dollars in costs to the applicants on their way to delegating a new gTLD. In the months following the report's publishing, the ICANN community mobilized to create alternative solutions to the Name Collision issue, as well as argue whether or not the issue was serious enough to delay delegation of 100s of gTLDs.<ref>[http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-annex-1-07oct13-en.pdf ICANN.org] Retrieved 05 Feb 2014</ref>
The report and ICANN's proposal for how to deal with the situation were posted on ICANN's website for public comment until September 17, 2013<ref name="NTAG">[http://domainincite.com/14162-ntag-rubbishes-new-gtld-collision-risk-report NTAG Rubbishes New gTLD Collision Risk Report, Domain Incite] Retrieved 17 Feb 2014</ref>
===Reception by New gTLD Applicants===
===Reception by New gTLD Applicants===