6,681
edits
Changes
Jump to navigation
Jump to search
Line 47:
Line 47: − + − ==Research==+ + +
no edit summary
===NGPC Resolution===
===NGPC Resolution===
On 8 October 2013, The [[New gTLD Program Committee]] (NGPC) announced their final solution to the Name Collision issue. The committee met to discuss the public comments received on the initial proposal, and then updated and released a final document titled the "[http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-annex-1-07oct13-en.pdf New gTLD Collision Occurrence Management Plan]"
On 8 October 2013, The [[New gTLD Program Committee]] (NGPC) announced their final solution to the Name Collision issue. The committee met to discuss the public comments received on the initial proposal, and then updated and released a final document titled the "[http://www.icann.org/en/groups/board/documents/resolutions-new-gtld-annex-1-07oct13-en.pdf New gTLD Collision Occurrence Management Plan]".
The final plan left the [[.home]] and [[.corp]] strings in permanent limbo as "high risk" strings, just as the original plan stated. These string will be not be delegated until ICANN and the community conduct more research and come up with a solution. ICANN believes these strings will cause significant problems if delegated to the [[Root Zone]].
The final plan left the [[.home]] and [[.corp]] strings in permanent limbo as "high risk" strings, just as the original plan stated. These string will be not be delegated until ICANN and the community conduct more research and come up with a solution. ICANN believes these strings will cause significant problems if delegated to the [[Root Zone]].
The plan states that ICANN will contract a Collision Occurrence Management Framework that will stipulate assessments and mitigation measures that may need to be taken for certain TLDs. This process is similar to that outlined in the original plan, with applicants waiting to delegate until they receive their assessment report and perform the necessary mitigation measures. However, the new report focused on an "Alternative Path to Delegation" in which New gTLD applicants who are not applying for .home or .corp could proceed to delegation without their assessment report, provided they block all [[Second Level Domain]]s (SLDs) that were found in the "Day in The Life" Internet data for their TLD. The majority of New gTLD applicants ended up choosing this alternative path.<ref>[http://domainincite.com/14659-new-gtld-applicants-get-a-way-to-avoid-name-collision-delay New gTLD Applicants Get a Way to Avoid Name Collision Delay, DomainIncite] Retrieved 19 Feb 2014</ref>
Finally, the plan outlined an outreach campaign to educate systems administrators, software developers, and other engineers about the Name Collision issue and the mitigation measures they could take to reduce risk.<ref>[http://www.icann.org/en/news/announcements/announcement-08oct13-en.htm Announcement 08 OCt 2013, ICANN.org] Retrieved 19 Feb 2014</ref><ref>[http://domainnamewire.com/2013/10/09/icann-gives-new-tld-applicants-a-faster-path-to-market/ ICANN Gives New gTLD Applicants a Faster Path to Market, DomainNameWire.com] Retrieved 19 Feb 2014</ref>
*[http://domainincite.com/14592-angry-gtld-applicants-lay-into-ana-and-verisign-bullshit ANA and verisign]
*[http://domainincite.com/14592-angry-gtld-applicants-lay-into-ana-and-verisign-bullshit ANA and verisign]