<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><title>ICANN News Alert</title><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
h2
{mso-style-priority:9;
mso-style-link:"Heading 2 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:18.0pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
h3
{mso-style-priority:9;
mso-style-link:"Heading 3 Char";
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:13.5pt;
font-family:"Times New Roman","serif";
font-weight:bold;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.Heading2Char
{mso-style-name:"Heading 2 Char";
mso-style-priority:9;
mso-style-link:"Heading 2";
font-family:"Cambria","serif";
color:#4F81BD;
font-weight:bold;}
span.Heading3Char
{mso-style-name:"Heading 3 Char";
mso-style-priority:9;
mso-style-link:"Heading 3";
font-family:"Cambria","serif";
color:#4F81BD;
font-weight:bold;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:603339849;
mso-list-template-ids:202139058;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:1882085647;
mso-list-template-ids:-857418094;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal style='text-align:justify'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>For those interested in the topic on Name Collision of New gTLDs, please read on.<o:p></o:p></span></p><p class=MsoNormal style='text-align:justify'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='text-align:justify'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Fahd Batayneh<o:p></o:p></span></p><p class=MsoNormal style='text-align:justify'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>ICANN<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Sent:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Monday, August 04, 2014 11:23 PM<br><b>Subject:</b> ICANN News Alert -- ICANN Approves Name Collision Occurrence Management Framework | Special IP Address (127.0.53.53) Alerts System Administrators of Potential Issue<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div style='border:solid #CCCCCC 1.0pt;padding:8.0pt 8.0pt 8.0pt 8.0pt'><div><p class=MsoNormal><span style='font-family:"Arial","sans-serif"'><a href="http://www.icann.org/"><span style='text-decoration:none'><img border=0 id="_x0000_i1025" src="http://www.icann.org/images/gradlogo_bow.jpg" alt=ICANN></span></a><o:p></o:p></span></p><h2 style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>News Alert<o:p></o:p></span></h2><p style='mso-margin-top-alt:0in;margin-right:0in;margin-bottom:7.5pt;margin-left:0in;text-align:justify'><span style='font-family:"Arial","sans-serif"'><a href="https://www.icann.org/news/announcement-2-2014-08-01-en">https://www.icann.org/news/announcement-2-2014-08-01-en</a><o:p></o:p></span></p><div class=MsoNormal align=center style='margin-top:15.0pt;text-align:center'><span style='font-family:"Arial","sans-serif"'><hr size=2 width="100%" align=center></span></div><h2 style='margin-bottom:0in;margin-bottom:.0001pt;text-align:justify'><span style='font-family:"Arial","sans-serif"'>ICANN Approves Name Collision Occurrence Management Framework | Special IP Address (127.0.53.53) Alerts System Administrators of Potential Issue<o:p></o:p></span></h2><p style='mso-margin-top-alt:11.25pt;margin-right:0in;margin-bottom:0in;margin-left:0in;margin-bottom:.0001pt;text-align:justify'><span style='font-family:"Arial","sans-serif"'>1 August 2014<o:p></o:p></span></p><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>ICANN today announced the approval of the <a href="https://www.icann.org/en/system/files/files/name-collision-framework-30jul14-en.pdf">Name Collision Occurrence Management Framework</a> [PDF, 634 KB] by the ICANN Board New gTLD Program Committee (NGPC). The framework implementation requirements were developed with input from many sources including the ICANN community, a report published by JAS Global Advisors LLC, and advice from the Security and Stability Advisory Committee (SSAC).<o:p></o:p></span></p><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>The framework is designed to mitigate the impact of name collisions in the domain name system (DNS), which typically occur when fully qualified domain names conflict with similar domain names used in private networks. When this occurs, users can be taken to an unintended Web page or encounter an error message.<o:p></o:p></span></p><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>To address this issue, the framework calls for registry operators to use a technique called "controlled interruption" to alert system administrators that there may be an issue in their network. Specifically, an IPv4 address – <strong><span style='font-family:"Arial","sans-serif"'>127.0.53.53</span></strong> – will appear in system logs, enabling a quick diagnosis and remediation.<o:p></o:p></span></p><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>"We now have a well-defined methodology for mitigating name collisions for delegated top-level domain names and a path forward for registries to unblock certain second-level domains in their list," said Akram Atallah, president of ICANN's Global Domains Division. "These operational processes, which were developed in conjunction with the multistakeholder community, will help to ensure the security of the domain name system."<o:p></o:p></span></p><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>Atallah went on to note that ICANN will provide information to and work with the Generic Names Supporting Organization (GNSO) to consider whether policy work on developing a long-term plan to manage gTLD name collisions issues should be undertaken.<o:p></o:p></span></p><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>ICANN will be holding <a href="https://www.icann.org/news/announcement-3-2014-08-01-en">webinars</a> to discuss details of the Name Collision Occurrence Management Framework and answer questions on 12 August 2014 – Session 1 will take place at 01:00-02:30 UTC and Session 2 will be from 15:00-16:30 UTC.<o:p></o:p></span></p><h3 style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>Overview: Name Collision Occurrence Management Framework Implementation<o:p></o:p></span></h3><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>ICANN registry operators are obligated to comply with requirements in the Name Collision Occurrence Management Framework, which include:<o:p></o:p></span></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:justify;mso-list:l1 level1 lfo1'><span style='font-family:"Arial","sans-serif"'>Acting on name collision reports from ICANN within two hours of receipt of the report during the first two years of the life of the top-level domain (TLD), measured from the time of delegation of the TLD;<o:p></o:p></span></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:justify;mso-list:l1 level1 lfo1'><span style='font-family:"Arial","sans-serif"'>Implementing continuous controlled interruption for a 90-day period.<o:p></o:p></span></li></ul><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>ICANN obligations include:<o:p></o:p></span></p><ul type=disc><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:justify;mso-list:l0 level1 lfo2'><span style='font-family:"Arial","sans-serif"'>Monitoring the registry's implementation of the controlled interruption to ensure compliance with contractual requirements;<o:p></o:p></span></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:justify;mso-list:l0 level1 lfo2'><span style='font-family:"Arial","sans-serif"'>Coordinating an emergency response for name collision reports only where there is a reasonable belief that the name collision presents a clear and present danger to human life; and<o:p></o:p></span></li><li class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:justify;mso-list:l0 level1 lfo2'><span style='font-family:"Arial","sans-serif"'>Working within the Internet Engineering Task Force (IETF) and with other relevant technical communities to identify a mechanism for IPv6 IP addresses that provides similar functionality to that being used in IPv4 (the loopback IP address 127.0.53.53).<o:p></o:p></span></li></ul><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>The Name Collision Occurrence Management Framework also calls for the delegation of .CORP, .HOME, and .MAIL to be deferred indefinitely. ICANN will collaborate with the technical and security communities to determine the best way to handle these strings in the long term.<o:p></o:p></span></p><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>For more information on name collisions please visit <a href="https://www.icann.org/resources/pages/name-collision-2013-12-06-en">https://www.icann.org/namecollision</a>.<o:p></o:p></span></p><h3 style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>About ICANN<o:p></o:p></span></h3><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>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: <a href="https://www.icann.org/">www.icann.org</a>.<o:p></o:p></span></p><p style='margin-right:8.25pt;text-align:justify'><span style='font-family:"Arial","sans-serif"'>[UPDATE: The date of the Session 1 webinar on the Name Collision Occurrence Management Framework has changed. It will now take place from 01:00-02:30 UTC on <em><span style='font-family:"Arial","sans-serif"'>12 August 2014</span></em>.]<span style='color:#1F497D'><o:p></o:p></span></span></p></div></div><p class=MsoNormal><span style='font-family:"Arial","sans-serif"'><img border=0 width=1 height=1 id="_x0000_i1028" src="http://click.icptrack.com/icp/track.php?msgid=943218&act=MI8Z&r=25971199&c=165637"><o:p></o:p></span></p></div></body></html>