<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" 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"><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19222"><!--[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]-->
<STYLE><!--
/* Font Definitions */
@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;}
@font-face
{font-family:Verdana;
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: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;}
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.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle25
{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;}
--></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 dir=ltr align=left><SPAN class=447430219-23052012><FONT color=#0000ff>Dear
IAG,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=447430219-23052012><FONT
color=#0000ff></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=447430219-23052012><FONT color=#0000ff>While
the draft TMCH model appears to be comprehensive, it is lacking many details and
nuances that have been discussed within the IAG</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=447430219-23052012><FONT color=#0000ff>It is
not clear how further refinement of the TMCH policies and rules will take place
in a transparent manner.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=447430219-23052012><FONT
color=#0000ff></FONT></SPAN> </DIV>
<DIV><FONT color=#0000ff>There are three <SPAN
class=447430219-23052012>specific issues that I would like to comment
on.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff>1. Potential Abuse from Data
Mining<BR>I find the proposed model of distributing encrypted data an elegant
approach that, if feasible, could possibly meet the needs of both trademark
owners and registry operators.</FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV><SPAN class=447430219-23052012><FONT color=#0000ff>Since this first
appeared only in the draft model, there hasn't been much discussion on the
feasibility of this approach.</FONT></SPAN></DIV>
<DIV><FONT color=#0000ff><SPAN class=447430219-23052012>If adopted, I still
see </SPAN>the risk of <SPAN class=447430219-23052012> potential
</SPAN>data mining by registries, registrars and end-users.</FONT></DIV>
<DIV> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff>I believe the best way to detect
such data mining is to ensure that all <SPAN
class=447430219-23052012> queries </SPAN>and/or displays of claims
data is logged and made available to the TMCH for possible reporting purposes,
even if no end-user <SPAN class=447430219-23052012>domain name
</SPAN>registration is consummated<SPAN class=447430219-23052012> .
The trademark owner is in the best position of determining if data mining has
occured for their portfolio. </SPAN><SPAN class=447430219-23052012> A
Trademark owner should be able to receive a periodic report showing how often a
claims notice was triggered for their trademarks, regardless if there were
no resulting registration. </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff>2. Creating New Rights<BR>I believe
there is consensus that offical <SPAN
class=447430219-23052012> trademark </SPAN>data sources should be used to
verify submissions to the TMCH. However, the issue of what to do if the
submission does not match the official record remains problematic.<SPAN
class=447430219-23052012> <FONT color=#0000ff><SPAN
class=447430219-23052012>In order to rely on official data sources, trademark
owners should be encouraged to maintain accurate records at the official data
sources.</SPAN></FONT></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff><SPAN
class=447430219-23052012> </SPAN><BR>A <SPAN
class=447430219-23052012> blanket </SPAN>policy of allowing
applicants, including assignees and licensees, to simply provide a letter
declaring their rights to a string should not be deemed sufficient to allow
over-riding the offical owner of record. If such Declarations are
allowed, then the TMCH would result in a repository of rights that <SPAN
class=447430219-23052012> are </SPAN> not reflected in the official
data sources.<SPAN class=447430219-23052012> The community would be
unable to verify the Rights of records in the TMCH if such rights are not
reflected in official data sources. Such a practice would be counter to
the transparency objective of ICANN. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff><SPAN
class=447430219-23052012></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff>3. Treatment of Special
Characters<BR>Limiting the transliteration of only two special characters "@"
and "&" appears arbitrary and a <SPAN
class=447430219-23052012> possible </SPAN>misreading of the IRT
Report.<BR>All special characters should be allowed so as to avoid eliminating
bona fide trademarks<SPAN class=447430219-23052012> from protection in the
TMCH </SPAN>. The trademark owner should specify at the time of
submission to the TMCH, the transliteration of any special characters in their
trademarks<SPAN class=447430219-23052012> , so that the registrable
domain name strings can be generated</SPAN>. <SPAN
class=447430219-23052012> </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff><SPAN
class=447430219-23052012></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff><SPAN class=447430219-23052012>The
TMCH should make available to the public reports showing the transliteration of
special characters provided by trademark owners. This published report
does not need to include the trademark containing these special
characters. Transparency of this information is important to help explain
to the community how certain domain name strings are protected by the TMCH
absent the existence of the exact domain name string in the official trademark
data sources.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff><SPAN
class=447430219-23052012> </SPAN><SPAN
class=447430219-23052012></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff><SPAN
class=447430219-23052012>Sincerely,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff><SPAN
class=447430219-23052012></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff><SPAN
class=447430219-23052012>Thomas Barrett</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff><SPAN
class=447430219-23052012>EnCirca, Inc</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff><SPAN
class=447430219-23052012> </SPAN><BR></DIV></FONT></BODY></HTML>