Changes

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 not be delegated until ICANN and the community conduct more research and propose a mitigation plan. 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 not be delegated until ICANN and the community conduct more research and propose a mitigation plan. 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 the one 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 and were eligible, 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 that were eligible 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>

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 the one 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 and were eligible, 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 that were eligible 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>

====Alternative Path to Delegation====

====Alternative Path to Delegation====

On 17-18 November 2013, ICANN released the reports for the alternative path to delegation. Apart from .home and .corp, all but 25 strings were eligible for this path, and could choose to elect the alternative path. The 25 strings not eligible for the alternative path must wait to receive their assessment and mitigation plans from ICANN.<ref>[https://newgtlds.icann.org/en/announcements-and-media/announcement-2-17nov13-en Announcement 17 Nov 2013, ICANN.org] Retrieved 19 Feb 2014</ref>

On 17-18 November 2013, ICANN released the reports for the alternative path to delegation. Apart from .home and .corp, all but 25 strings were eligible for this path, and could choose to elect the alternative path. The 25 strings not eligible for the alternative path must wait to receive their assessment and mitigation plans from ICANN.<ref>[https://newgtlds.icann.org/en/announcements-and-media/announcement-2-17nov13-en Announcement 17 Nov 2013, ICANN.org] Retrieved 19 Feb 2014</ref>