<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">hi all,<div><br></div><div>i could have sworn i sent this out, but i find no record that i did.</div><div><br></div><div>the JAS Advisors report on the Name Collisions issue has been released for comment. here’s a link to the announcement</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><a href="http://www.icann.org/en/news/announcements/announcement-26feb14-en.htm">http://www.icann.org/en/news/announcements/announcement-26feb14-en.htm</a></div><div><br></div><div>and here’s the text — we have until April 21 to make a public comment.</div><div><br></div><div>mikey</div><div><br></div><div><br></div><div><h1 class="title" id="page-title">Independent Report Maps Possible Way Forward in Mitigating Domain Name Collisions</h1> <div id="addthis"><div class="addthis_toolbox addthis_default_style "><a class="addthis_counter addthis_pill_style"></a></div></div> <div class="tabs"></div> <div class="article"><article id="node-1173950" class="node node-announcement clearfix" about="/en/news/announcements/announcement-26feb14-en.htm" typeof="sioc:Item foaf:Document">
<div class="field field-name-field-ann-pubdate field-type-datetime field-label-hidden clearfix">
<div class="field-items">
<div class="field-item even"><span class="date-display-single" property="dc:date" datatype="xsd:dateTime" content="2014-02-26T04:45:00-08:00">26 February 2014</span></div>
</div>
</div>
<div class="field field-name-body field-type-text-with-summary field-label-hidden clearfix">
<div class="field-items">
<div class="field-item even" property="content:encoded"><p>An independent report commissioned by <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>, <strong><em>Mitigating the Risk of <abbr title="Domain Name System">DNS</abbr> Namespace Collisions,</em></strong> has offered a set of concrete recommendations on how to mitigate potential risks of domain name collisions.</p><p><a href="http://www.icann.org/en/about/staff/security/ssr/name-collision-mitigation-26feb14-en.pdf">Click here to download the full report »</a> [PDF, 322 KB]</p><p><a href="http://www.icann.org/en/news/public-comment/name-collision-26feb14-en.htm">Click here to submit comments on the report »</a></p><p>A name collision occurs when an attempt to resolve a name used in a
private name space results in a query to the public Domain Name System (<abbr title="Domain Name System">DNS</abbr>).</p><p>"This report takes an in-depth look at the collision issue and the
potential risks and impacts, and gives us some very clear advice aimed
at how to help system operators detect and mitigate those risks," said
Akram Atallah, President of <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>'s Global Domains Division. "The next step is to seek input from our community on the report's findings."</p><p>The report stressed that name collisions are nothing new and that any
issues that arise from expansion of the Top-Level Domains (TLDs) under <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>'s New <abbr title="generic Top Level Domain">gTLD</abbr> program would resemble those that occur in other parts of the <abbr title="Domain Name System">DNS</abbr>.
But the report noted that expanding the number of TLDs will not
fundamentally or significantly increase the risks of name collisions.</p><p>Specifically, the study outlines a set of recommendations on how <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> and the <abbr title="Top Level Domain">TLD</abbr> operators should handle the issue of name collisions in the expanding <abbr title="Top Level Domain">TLD</abbr> space:</p>
<ul>
<li><abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> should require new <abbr title="Top Level Domain">TLD</abbr> registries to implement and publish a 120-day <em>controlled interruption zone</em> monitored by <abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr> immediately upon delegation in the root zone.
<ul>
<li>After the 120-day period, there shall be no further collision-related restrictions on the <abbr title="Top Level Domain">TLD</abbr>.</li>
</ul>
</li>
<li><abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
should have emergency response processes to analyze and act upon
reported problems that present "clear and present danger to human life".</li>
<li><abbr title="Internet Corporation for Assigned Names and Numbers">ICANN</abbr>
and others in the community should continue to collect and analyze data
relating to the root servers and to the controlled interruption.</li>
<li>The Top-Level Domains .corp, .home and .mail should be permanently reserved.</li>
</ul><p>The report is posted for public comment until April 21, 2014.</p></div>
</div>
</div>
</article></div><div apple-content-edited="true">
<br class="Apple-interchange-newline"><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; display: inline !important; float: none; ">PHONE: 651-647-6109, FAX: 866-280-2356, WEB: <a href="http://www.haven2.com">www.haven2.com</a>, HANDLE: OConnorStP (ID for Twitter, Facebook, LinkedIn, etc.)</span>
</div>
<br></div></body></html>