<html><head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"></head><body
bgcolor="#FFFFFF" text="#000000">
Hi all,<br>
<br>
Message from ICANN.<br>
In an enterprise environment, I felt the probability of this happening
is low.<br>
<br>
<br>
/chunsing<br>
<br>
<p class="MsoNormal"><b><u><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">ICANN
Advisory to IT Professionals on Name Collision Identification and
Mitigation<o:p></o:p></span></u></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span>
</p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><a
href="http://www.icann.org/">ICANN</a>, the international body
responsible for oversight of the Internet’s Domain Name System (DNS),
has issued comprehensive
advice to IT professionals worldwide on how to proactively identify and
manage an issue known as “domain name collision”.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">In
a report titled ‘<a
href="https://www.icann.org/en/about/staff/security/ssr/name-collision-mitigation-05dec13-en.pdf">Name
Collision Identification and Mitigation
for IT Professionals</a>’, ICANN explains the nature and causes of name
collision and proposes a range of possible solutions.<o:p></o:p></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span>
</p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">A
name collision occurs when an attempt to resolve a name that is used in
a private name space (e.g., under a non-delegated Top Level Domain, or a
short, unqualified
name) results in a query to the public DNS. To explain the issue using
an analogy, consider calling for “Mary” in your office where you’ve
assumed there’s only one “Mary”, and then calling out “Mary” in a
shopping mall and expecting that “office Mary” will
respond.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Domain
name collisions are not new. However, with up to 1,300 new generic Top
Level Domains (TLDs) being introduced over the next year, there is an
increased
level of concern and ICANN is ensuring that IT professionals are aware
of the issue. The ICANN report addresses some concerns that a number of
applied-for new TLDs may be identical to names used in private name
spaces.<o:p></o:p></span><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span>
</p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The
report explains how DNS queries leak into the global DNS from private
name spaces and how these leaks can have unintended consequences. It
shows that private
networks will consistently, stably, and reliably perform name
resolution when they use Fully Qualified Domain Names (FQDNs) and
resolve them from the global DNS, and proposes methods to migrate to
FQDNs.<o:p></o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">For
more information:</span></b><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">
The report, along with additional useful
information and resources, can be found at:</span> <span
style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
<a href="http://www.icann.org/en/help/name-collision">http://www.icann.org/en/help/name-collision</a>.</span></p>
<br>
</body>
</html>