ICANN ICANN Email List Archives


<<< Chronological Index >>>    <<< Thread Index >>>

[bc-gnso] ICANN Issues Advice to IT Professionals on Name Collision Identification and Mitigation

  • To: <bc-gnso@xxxxxxxxx>
  • Subject: [bc-gnso] ICANN Issues Advice to IT Professionals on Name Collision Identification and Mitigation
  • From: "Benedetta Rossi" <bc-secretariat@xxxxxxxxx>
  • Date: Fri, 6 Dec 2013 20:54:36 +0100

Dear BC Members,

Please find below an ICANN Announcement regarding ICANN's issuing advice to
IT Professionals on name collision identification & mitigation, an
announcement of particular interest to business.



Kind Regards,


Benedetta Rossi

BC Secretariat







6 December 2013


ICANN Issues Advice to IT Professionals on Name Collision Identification and


Los Angeles, California.ICANN today issued comprehensive advice to IT
professionals worldwide on how to proactively identify and manage private
name space leakage into the public Domain Name System (DNS) and thus,
eliminate the causes of name collisions as new Top Level Domains (TLDs) are
added to the DNS. In a report titled Name Collision Identification and
Mitigation for IT Professionals, ICANN explains the nature and causes of
name collision and proposes a range of possible solutions.

Domain name collisions are not new. However the report addresses some
concerns that a number of applied-for new TLDs may be identical to names
used in private name spaces."

The report explains how DNS queries leak into the global DNS from private
name spaces and how these leaks can have unintended consequences. The report
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.

"While it appears that name collisions won't affect significant numbers of
corporate network operators or Internet users, ICANN considers it essential
that it does everything possible to minimize potential impact and to offer
clear advice on dealing with the issue," said Paul Mockapetris, Global
Domains Division Security Advisor.

The report recommends that every organization that is not already using
FQDNs from the public DNS should consider the following strategy:

*       Monitor name services, compile a list of private TLDs or short
unqualified names you use internally, and compare the list you create
against the list of new TLD strings.
*       Formulate a plan to mitigate causes of leakage.
*       Prepare users for the impending change in name usage by notifying
them in advance or providing training
*       Implement your plan to mitigate the potential collision

The release of today's advice to IT professionals is the result of several
months of diligent work by ICANN's staff, subject matter experts, the ICANN
Executive Team and the Board of Directors.

"The report we've issued today offers IT professionals, whether they work in
large organizations or small companies, comprehensive advice and suggested
remedies that can be simple to implement," said Dave Piscitello, Vice
President of Security and ICT Coordination. "While other interim or
makeshift solutions may exist, migration using FQDNs has lasting value -
once you've done this, you are good to go for now and future new TLD

The report, along with additional useful information and resources, can be
found at: http://www.icann.org/en/help/name-collision.





Brad White
Director Global Media Affairs
Washington, D.C.
Tel: +1.202.570.7118
E: brad.white@xxxxxxxxx

James Cole
ICANN Global Media Coordinator
Washington, D.C.
Tel.  +1 202.570.7240
E: james.cole@xxxxxxxxx

Andrew Robertson
Edelman Public Relations
London, U.K.
Tel.  + 44 (7811) 341 945
E: andrew.robertson@xxxxxxxxxxx


About ICANN: ICANN's mission is to ensure a stable, secure and unified
global Internet. To reach another person on the Internet you have to type an
address into your computer - a name or a number. That address has to be
unique so computers know where to find each other. ICANN coordinates these
unique identifiers across the world. Without that coordination we wouldn't
have one global Internet. ICANN was formed in 1998. It is a not-for-profit
public-benefit corporation with participants from all over the world
dedicated to keeping the Internet secure, stable and interoperable. It
promotes competition and develops policy on the Internet's unique
identifiers. ICANN doesn't control content on the Internet. It cannot stop
spam and it doesn't deal with access to the Internet. But through its
coordination role of the Internet's naming system, it does have an important
impact on the expansion and evolution of the Internet. For more information
please visit:  <http://www.icann.org> www.icann.org.


If you would rather not receive future communications from ICANN, let us
know by clicking here.
ICANN, 12025 Waterfront Drive Suite 300, Los Angeles, CA 90094-2536 United

<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy