6,681
edits
Changes
no edit summary
Watch the .CLUB Domains LLC team as they realize they won the .club TLD via private auction:
Watch the .CLUB Domains LLC team as they realize they won the .club TLD via private auction:
<videoflash>Wu38PkeyF0M</videoflash>
<videoflash>Wu38PkeyF0M</videoflash>
==Developments==
===Name Collision===
Many applications for new gTLDs have raised security concerns because the applied-for strings are already in wide use on internal networks in certain areas of the world.<ref>[http://domainincite.com/13994-new-gtlds-are-the-new-y2k-corp-and-home-are-doomed-and-everything-else-is-delayed New gTLDs are the New Y2K, Domain Incite] Retrieved 12 Sept 2013</ref> This would create a name collision if the new gTLD were to be delegated and could cause serious security concerns for some strings. The remaining application for .club has been deemed an "uncalculated risk" by [[ICANN]] because of name collision with existing internal networks, which means the application will face delays until the issues are resolved. However, in a letter that .CLUB Domains LLC CTO [[Dirk Bhagat]] sent to [[ICANN]] on September 16, 2013, .CLUB Domains has proposed a solution to the name collision issue. The company hired the same firm that ICANN hired ([Interisle Consulting]) to report on the proposed .club gTLD, and are proposing to reserve the top 50 name collisions of .club, which is available knowledge now due to Interisle's report. The top 50 name collisions would be blocked from registration, and according to .CLUB Domains LLC would create a number of queries to the gTLD that it would be deemed by [[ICANN]] as "low risk."<ref>[http://domainincite.com/14501-club-offers-solution-to-name-collision-risks .club Offers Solution to Name Collision Risks] Retrieved 16 Sept 2013</ref>
==References==
==References==