<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=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></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 lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">All,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In preparation for our Council call this week where the topic of String Similarity will be discussed, I wanted to provide these comments which are my own and not necessarily the views of the Registries Stakeholder Group.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="color:black">Like many in the ICANN community, I have expressed some frustration about inconsistent application of ICANN’s standard for new gTLD objections based on claims that an applied for string is “confusingly similar”
to another proposed gTLD or to an existing TLD. This led me to ask Christine Willett during the last ICANN Webinar Update how the ICANN staff intended to proceed in such cases.</span><span lang="EN-GB" style="font-family:"Times New Roman","serif";color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> </span><span lang="EN-GB" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">I want to be clear, however, that “consistent” application of the confusingly similar standard DOES NOT require the “same” outcome for all applications for the exact match for a particular string. If that were
the case, then the dispute resolution panels would be required to evaluate the likelihood of confusion <i>without regard</i> to each applicant’s unique plan for a gTLD string and their arguments articulating why such plans would not cause confusion. That
would be a huge mistake. In fact, the proposed use of a new gTLD is highly relevant to the question of whether or not there is a likelihood of confusion. Indeed, it is to be expected that expert panels might reasonably conclude, as has apparently happened,
that the string “.cam” is confusingly similar to “.com” in one case but not in another. As lawyers for United TLD argued in that case (in a publicly accessible letter), “Consolidation has the potential to prejudice the Applicants if all Applicants’ arguments
are evaluated collectively, without regard to each Applicant’s unique plan for the .cam gTLD and their arguments why such plans would not cause confusion.”
</span><span lang="EN-GB" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span><span lang="EN-GB" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">In fact, the complained-of inconsistency in other cases appears to arise from the panel’s failure to actually take account of the context in which a proposed gTLD would operate. Examples include translation cases
where the different markets were likely not considered.</span><span lang="EN-GB" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> </span><span lang="EN-GB" style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal">My point is that <span style="color:#1F497D">t</span><span style="color:black">he community and applicant pool each have legitimate interests in the consistent application of ICANN’s standard for determining whether or not two strings “confusingly
similar.” Those interests do not, however, justify further delay or re-opening cases where context supports a finding of confusing similarity in one case but not another.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB"></span><o:p></o:p></p>
<p class="MsoNormal">Best regards,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-top:6.0pt;mso-margin-bottom-alt:auto"><b><span style="font-size:9.0pt;font-family:"Arial","sans-serif"">Jeffrey J. Neuman<span style="color:#3366FF">
<br>
</span><span style="color:#068658">Neustar, Inc. / Vice President, Business Affairs</span></span></b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D"><br>
46000 Center Oak Plaza, Sterling, VA 20166</span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray"><br>
</span><b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">Office:</span></b><b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#333333">
</span></b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D">+1.571.434.5772</span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#000066">
</span><b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">Mobile:
</span></b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D">+1.202.549.5079</span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray">
</span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#000066"> </span><b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">Fax:
</span></b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#7D7D7D">+1.703.738.7965</span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray">
</span><b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">/</span></b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#3366FF">
</span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658"><a href="mailto:jeff.neuman@neustar.biz"><span style="color:#068658">jeff.neuman@neustar.biz</span></a>
</span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray"> </span><b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658">/</span></b><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#3366FF">
</span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:#068658"><a href="http://www.neustar.biz/"><span style="color:#068658">www.neustar.biz</span></a></span><span style="font-size:8.5pt;font-family:"Arial","sans-serif";color:gray">
<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>