6,681
edits
Changes
no edit summary
==History==
==History==
Although the Name Collision issue is not new, the topic was reintroduced and debated in the [[ICANN]] community in 2013 during the [[New gTLD Program]].
==New gTLD Program==
==New gTLD Program==
The New gTLD Applicant's Group within ICANN sent a letter responding to the Interisle's report and ICANN recommendations. The NTAG felt that the report overstated the risks of Name Collision, and called for all of the strings that were designated by ICANN as "uncalculated risk" to be moved into the "low risk" category. The NTAG stated that they agreed however, that the .home and .corp strings should remain as "high risk" and further research is required to move forward with those strings.<ref name="NTAG"></ref>
The New gTLD Applicant's Group within ICANN sent a letter responding to the Interisle's report and ICANN recommendations. The NTAG felt that the report overstated the risks of Name Collision, and called for all of the strings that were designated by ICANN as "uncalculated risk" to be moved into the "low risk" category. The NTAG stated that they agreed however, that the .home and .corp strings should remain as "high risk" and further research is required to move forward with those strings.<ref name="NTAG"></ref>
==Alternative Path to Delegation==
===Community Discussions===
The discussions surrounding the Interisle Report and ICANN's response occurred online, in the public comments on the ICANN site, as well as several in-person conferences organized by several community members.
[[Artemis Internet]], the applicant for [[.secure]], held a day-long conference in San Francisco in August 2013 to discuss the Names Collision issue. Delegates from [[Google]] and [[Paypal]] were listed as panelists.
==Proposed Solutions==
==Research==
==Research==