[[.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> | [[.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> |