Changes

no edit summary
Line 39: Line 39:  
Many solutions to the Name Collision issue were proposed by ICANN, TLD applicants, and the community at large. The initial proposal by ICANN that immediately followed the release of Interisle's report, was to delay the delegation of a portion of the strings that were of uncalculated risk, as explained above.
 
Many solutions to the Name Collision issue were proposed by ICANN, TLD applicants, and the community at large. The initial proposal by ICANN that immediately followed the release of Interisle's report, was to delay the delegation of a portion of the strings that were of uncalculated risk, as explained above.
   −
A number of New gTLD applicants proposed alternative approaches to "mitigation" of the name collision issue. [[Neustar]] conducted its own analysis of the data in the Interisle report, and suggested evaluating domains of "
+
A number of New gTLD applicants proposed alternative approaches to "mitigation" of the name collision issue. [[Neustar]] conducted its own analysis of the data in the Interisle report, and suggested a few alternative solutions that included moving all strings except .home, .corp, and .mail into the low risk category and then evaluating the risk immediately instead of mandating a 120-day period after the RA signing.<ref>[http://www.circleid.com/posts/20130717_neustar_analysis_icann_overstates_risk_of_harmful_domain_collision/%20Neustar%20analysis Neustar Analysis] Retrieved 18 Feb 2014</ref>
 +
 
 +
[[.CLUB Domain LLC]], the company applying for [[.club]], also proposed a solution of their own. The company contracted Interisle Consulting to do an evaluation of the .club string, to determine the possible name collisions that might occur if the string was delegated. They then proposed, in a letter to ICANN, that the solution for the strings in the "uncalculated risk" category would reserve the top 50 names in each string that see DNS root traffic. The list of these string would come from an individual report much like the one .CLUB Domains commissioned for themselves. Then when .club goes live, the impact of collisions would be greatly reduced. This solution makes it possible to have more time to find a solution to the Name Collision issue while still allowing delegations of new TLDs to continue provided they reserve a certain number of Second Level Domains ([[SLD]]s).<ref>[http://domainincite.com/14501-club-offers-solution-to-name-collision-risks .Club Offers Solution to Name Collision Risk, DomainIncite] Retrieved 18 Feb 2014</ref>
 +
 
 
==Research==
 
==Research==