<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:Cambria;
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;}
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";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-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.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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:1248880537;
mso-list-template-ids:1127367736;}
@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;}
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'>(sorry for cross posting)<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'>For those interested in the Domain Name Collisions of New gTLDs.<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<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"'> Wednesday, February 26, 2014 7:55 PM<br><b>Subject:</b> ICANN News Alert -- Independent Report Maps Possible Way Forward in Mitigating Domain Name Collisions<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><a href="http://www.icann.org/"><span style='font-family:"Arial","sans-serif";text-decoration:none'><img border=0 width=94 height=94 id="_x0000_i1026" src="cid:image001.jpg@01CF3650.7D8F2350" alt=ICANN></span></a><span style='font-family:"Arial","sans-serif"'><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="http://www.icann.org/en/news/announcements/announcement-26feb14-en.htm">http://www.icann.org/en/news/announcements/announcement-26feb14-en.htm</a><o:p></o:p></span></p><div style='margin-top:15.0pt'><div class=MsoNormal align=center style='text-align:center'><span style='font-family:"Arial","sans-serif"'><hr size=2 width="100%" align=center></span></div></div><h2 style='margin-bottom:0in;margin-bottom:.0001pt;text-align:justify'><span style='font-family:"Arial","sans-serif"'>Independent Report Maps Possible Way Forward in Mitigating Domain Name Collisions<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"'>26 February 2014<o:p></o:p></span></p><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>An independent report commissioned by ICANN, <em><b><span style='font-family:"Arial","sans-serif"'>Mitigating the Risk of DNS Namespace Collisions,</span></b></em> has offered a set of concrete recommendations on how to mitigate potential risks of domain name collisions.<o:p></o:p></span></p><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'><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]<o:p></o:p></span></p><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'><a href="http://www.icann.org/en/news/public-comment/name-collision-26feb14-en.htm">Click here to submit comments on the report »</a><o:p></o:p></span></p><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>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 (DNS).<o:p></o:p></span></p><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>"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 ICANN's Global Domains Division. "The next step is to seek input from our community on the report's findings."<o:p></o:p></span></p><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>The report stressed that name collisions are nothing new and that any issues that arise from expansion of the Top-Level Domains (TLDs) under ICANN's New gTLD program would resemble those that occur in other parts of the DNS. But the report noted that expanding the number of TLDs will not fundamentally or significantly increase the risks of name collisions.<o:p></o:p></span></p><p style='text-align:justify'><span style='font-family:"Arial","sans-serif"'>Specifically, the study outlines a set of recommendations on how ICANN and the TLD operators should handle the issue of name collisions in the expanding TLD space:<o:p></o:p></span></p><p style='mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in;text-align:justify;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='font-size:10.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span dir=LTR></span><span style='font-family:"Arial","sans-serif"'>ICANN should require new TLD registries to implement and publish a 120-day <em><span style='font-family:"Arial","sans-serif"'>controlled interruption zone</span></em> monitored by ICANN immediately upon delegation in the root zone.<o:p></o:p></span></p><p style='mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:12.0pt;margin-left:1.0in;text-align:justify;text-indent:-.25in;mso-list:l0 level2 lfo2'><![if !supportLists]><span style='font-size:10.0pt;font-family:"Courier New"'><span style='mso-list:Ignore'>o<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span dir=LTR></span><span style='font-family:"Arial","sans-serif"'>After the 120-day period, there shall be no further collision-related restrictions on the TLD.<o:p></o:p></span></p><p style='mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in;text-align:justify;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='font-size:10.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span dir=LTR></span><span style='font-family:"Arial","sans-serif"'>ICANN should have emergency response processes to analyze and act upon reported problems that present "clear and present danger to human life".<o:p></o:p></span></p><p style='mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in;text-align:justify;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='font-size:10.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span dir=LTR></span><span style='font-family:"Arial","sans-serif"'>ICANN and others in the community should continue to collect and analyze data relating to the root servers and to the controlled interruption.<o:p></o:p></span></p><p style='mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in;text-align:justify;text-indent:-.25in;mso-list:l0 level1 lfo2'><![if !supportLists]><span style='font-size:10.0pt;font-family:Symbol'><span style='mso-list:Ignore'>·<span style='font:7.0pt "Times New Roman"'> </span></span></span><![endif]><span dir=LTR></span><span style='font-family:"Arial","sans-serif"'>The Top-Level Domains .corp, .home and .mail should be permanently reserved.<o:p></o:p></span></p><p style='margin-right:8.25pt;text-align:justify'><span style='font-family:"Arial","sans-serif"'>The report is posted for public comment until April 21, 2014.<span style='color:#1F497D'><o:p></o:p></span></span></p></div></div><p class=MsoNormal style='text-align:justify'><span style='font-family:"Arial","sans-serif"'><o:p> </o:p></span></p></div></body></html>