<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div><br>
</div>
<div style="">
<title>ICANN News Alert</title>
<meta content="icann, internet, internet corporation for assigned names and numbers, iana" name="keywords">
<meta content="Internet Corporation for Assigned Names and Numbers" name="description">
<div style="background-color: #ffffff; font-family: arial; font-size: small;">
<div style="width:758px; padding:10px; border: 1px solid #cccccc; margin-left: auto; margin-right: auto;">
<div style="width: 738px; margin-left: auto; margin-right: auto;"><a href="http://www.icann.org/"><img alt="ICANN" src="http://www.icann.org/images/gradlogo_bow.jpg" style="border: 0px; width: 94px; height: 94px; float: left; margin-top: 0px; margin-right: 10px;"></a>
<h2>News Alert</h2>
<p style="margin: 0px 0px 10px 0px; font-family: arial; font-size: small;"><a href="https://www.icann.org/news/announcement-2-2014-11-07-en">https://www.icann.org/news/announcement-2-2014-11-07-en</a></p>
<hr style="margin: 20px 0px 0px 0px;">
<h2 style="clear: left; margin-bottom: 0px;">Requirements for Implementing Rights Protection Mechanisms in Name Collision Mitigation Framework Now Available</h2>
<p style="margin: 15px 0px 0px 0px;">7 November 2014</p>
<p>Following a 90-day public consultation period, ICANN is implementing a solution to allow new gTLD registries to release names from their Second-level Domain (SLD) Block Lists while complying with all Rights Protection Mechanism requirements. ICANN will provide
affected registries with an <a href="http://newgtlds.icann.org/sites/default/files/agreements/name-collision-assessment-addendum-07nov14-en.pdf">
addendum</a> [PDF, 68 KB] to their Name Collision Occurrence Assessments that explains how to release blocked names, by 14 November 2014.</p>
<p>To release these names, the approach requires registry operators to implement an "exclusive registration period" that meets the criteria described in its "Assessment Addendum," limited to the following category of names:</p>
<ul>
<li>Included on the Second-level Domain Block List provided in the registry operator's
<em>Alternate Path to Delegation Report</em>. </li><li>Recorded in the Trademark Clearinghouse. </li><li>Withheld from allocation by a registry operator during its Sunrise Period or Claims Period.
</li></ul>
<p>Registry operators can choose one of two paths for conducting an exclusive registration period:</p>
<ol>
<li>
<p><strong><u>Option A – ICANN Selected Exclusive Registration Dates</u></strong></p>
<p>Registry Operator may opt into one of two exclusive registration periods published by ICANN by providing a minimum of ten (10) days notice to ICANN of its decision to do so, followed by at least thirty (30) days of an exclusive registration period. The start
dates for each exclusive registration period will be publicized to enhance awareness among eligible rights holders. ICANN strongly encourages this option to streamline communications and expedite the process for release of names from the SLD Block List.</p>
<p>For Option A, Exclusive Registration Period timeframes are as follows:</p>
<ul>
<li>Exclusive Registration Period 1: 10 December 2014 – 9 January 2015. Registries may opt in by
<strong>30 November 2014</strong>. </li><li>Exclusive Registration Period 2: 16 January 2015 – 15 February 2015. Registries may opt in by
<strong>6 January 2015</strong>. </li></ul>
</li><li>
<p><strong><u>Option B – Registry Operator Selected Exclusive Registration Dates</u></strong></p>
<p>Registries not opting for Option A may provide an exclusive registration period under the same requirements as the registry's original Sunrise Period:</p>
<ol class="lower-alpha">
<li>Providing a minimum of thirty (30) days notice of the exclusive registration period followed by a
<em>start-date</em> (at least 30 days) exclusive registration; or </li><li>Providing an <em>end-date</em> (60 days) exclusive registration period, provided that first-come-first-served is not used as the allocation mechanism.
</li></ol>
</li></ol>
<p><strong>All registry operators must submit their exclusive registration period information to ICANN via the
<a href="http://myicann.secure.force.com/">GDD Portal</a>.</strong></p>
<p>The 90-day consultation was specified in measure II, Section C of the <a href="http://newgtlds.icann.org/sites/default/files/agreements/name-collision-assessment-04aug14-en.htm">
Name Collision Occurrence Assessment</a> and a <a href="https://features.icann.org/name-collision-occurrence-management-framework">
resolution</a> of the New gTLD Program Committee of the ICANN Board.</p>
<h3>Resources:</h3>
<ul>
<li><a href="https://www.icann.org/en/system/files/files/name-collision-framework-30jul14-en.pdf">Name Collision Occurrence Framework</a> [PDF, 634 KB]<br>
Information regarding the requirements a registry must implement as part of this Name Collision Occurrence Assessment
</li><li><a href="http://la51.icann.org/en/schedule/wed-name-collision">Name Collision Session at ICANN51</a><br>
A presentation about the relationship between the Name Collision Mitigation Framework and Rights Protections Mechanisms. Includes Q&A with the ICANN community.
</li><li><a href="https://www.icann.org/resources/pages/name-collision-2013-12-06-en">Name Collision Resources & Information page</a><br>
A central hub for all things name collision. Includes information for system operators, registry operators and the general public.
</li><li><a href="https://www.icann.org/public-comments/name-collision-rpm-2014-08-25-en">Public Comment Forum</a><br>
Public comments received in response to discussion paper on implementing rights protection mechanisms (RPMs) in the Name Collision Occurrence Framework.
</li></ul>
</div>
</div>
<br>
<br>
</div>
</div>
</span>
</body>
</html>