<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<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]--><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:Arrow;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Arial","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.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.apple-style-span
{mso-style-name:apple-style-span;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:black;
font-weight:normal;
font-style:normal;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
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 class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Jeff,<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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">If one had access to the TMCH data it is possible that one could see the entire trademark portfolio for a particular rights holder across all marks and jurisdictions.
This consolidated information is not available anywhere, for free or for a fee, except in the rights holder’s files and docketing system. While some jurisdictions allow public searching of their trademark database, most do not. As for 3<sup>rd</sup> party
search companies, a worldwide search is extremely expensive, and does not cover every country. Even if every jurisdiction had free search and/or paid search covered every country and wasn’t obscenely expensive, you would have to know all the marks and registrants
that you were searching for as it is likely that all registrations would not be in the name of the same company (i.e. subsidiaries, affiliates, etc). Furthermore, for paid search, e</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">ven
assuming you could effectively do such a search and cover all marks, countries, subsidiaries/affiliates, it would likely cost tens or hundreds of thousands for EACH COMPETITOR. The threat of decentralizing data storage in the TMCH via local cache or otherwise
is that companies could somehow access this information for free or negligible cost. This information could be misused in a variety of ways that could negatively impact the rights holder, including identifying gaps in trademark registration coverage in first
to file jurisdictions that would enable a competitor or other third party to register first in those countries and block the rights holder from entering the market or forcing the rights holder to pay a ransom to enter (and yes I realize that the company technically
might not be a rights holder in those jurisdictions with no registration or use yet but am just using “rights holder” nomenclature for convenience). In other words, this represents a very real identifiable issue that could result in very real harm to rights
holders. </span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Best regards,<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>
<table class="MsoNormalTable" border="0" cellpadding="0" width="100%" style="width:100.0%">
<tbody>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><b><span style="font-size:11.0pt;color:black">Marc H. Trachtenberg
<o:p></o:p></span></b></p>
</td>
</tr>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><span style="font-size:9.0pt;color:#333333">Winston & Strawn LLP<br>
35 W. Wacker Drive<br>
Chicago, IL 60601-9703<o:p></o:p></span></p>
</td>
</tr>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><span style="font-size:9.0pt;color:#333333">D: +1 (312) 558-7964<o:p></o:p></span></p>
</td>
</tr>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><span style="font-size:9.0pt;color:#333333">M: +1 (773) 677-3305
<o:p></o:p></span></p>
</td>
</tr>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><span style="font-size:9.0pt;color:#333333">F: +1 (312) 558-5700<o:p></o:p></span></p>
</td>
</tr>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><span style="font-size:9.0pt;color:maroon"><a href="http://www.winston.com/index.cfm?contentID=24&itemID=15281"><span style="color:maroon;text-decoration:none">Bio</span></a> | <a href="http://www.winston.com/sitefiles/wsvcard/15281.vcf"><span style="color:maroon;text-decoration:none">VCard</span></a> | <a href="mailto:mtrachtenberg@winston.com"><span style="color:maroon;text-decoration:none">Email</span></a> | <a href="http://www.winston.com"><span style="color:maroon;text-decoration:none">www.winston.com</span></a><o:p></o:p></span></p>
</td>
</tr>
<tr>
<td style="padding:.75pt .75pt .75pt .75pt">
<p class="MsoNormal"><b><span style="font-size:11.0pt;color:black"><a href="http://twitter.com/winstonadvlaw"><span style="font-size:9.0pt;color:maroon;text-decoration:none">Follow us on Twitter
</span><span style="font-size:9.0pt;color:maroon">twitter.com/winstonadvlaw</span></a><o:p></o:p></span></b></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:#1F497D"><img border="0" width="96" height="53" id="_x0000_i1026" src="cid:image001.jpg@01CD374E.E71DA970" alt="Description: Winston & Strawn LLP"></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><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>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><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-family:"Tahoma","sans-serif"">From:</span></b><span style="font-family:"Tahoma","sans-serif""> tmch-iag-bounces@icann.org [mailto:tmch-iag-bounces@icann.org]
<b>On Behalf Of </b>Jeff Eckhaus<br>
<b>Sent:</b> Monday, May 21, 2012 11:41 AM<br>
<b>To:</b> Rosette, Kristina; tmch-iag@icann.org<br>
<b>Subject:</b> Re: [Tmch-iag] Trademark Clearinghouse IAG - Comments on Draft Implementation Model<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">Hi Kristina and the IP team,<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">I hope I am not stirring up a hornets nest here, but I have a question regarding the data access and the protections being recommended by the IP lawyers in the
IAG. <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black">There is a statement in the comments that "</span><span class="apple-style-span"><span style="color:black">Local caching at the Registry, which the Model envisions,
creates an environment in which a Registry can misuse and/or abuse trademark data". While I do not doubt that their could be misuse in any environment or any setting with any data, I am unsure what the misuse of data here could be? Isn't all of the data that
will be in the TMCH available for free or for a nominal fee from existing sources? </span></span><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><span style="color:black">Is the concern that a Registry , will use their access to the TMCH during the sunrise period and then sell that data to some other person? Will they use the Sunrise data in some other
nefarious way? What could they do with it? </span></span><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><span style="color:black">I have discussed this issue with trademark people outside of the ICANN world with existing Registries and Registrars and still cannot figure out what the misuse of data can be. If
the data is currently available either for free or from other sources for a fee, what is the abuse that can occur? Is this just a case of we need to protect against every possible issue that can come up, even if we cannot identify it? </span></span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><span style="color:black">Now I am not asking this because I want to start an argument, but really work towards a solution. The cryptographic approach has issues and implementation can be difficult and do
not believe it is the best solution. I also believe rate limiting is not a proper solution as it could lead to unintended consequences and negatively affect a sunrise period as orders are not able to be fulfilled and requests denied or lost as artificial limits
are reached in a busy sunrise period. </span></span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><span style="color:black">I hope we can discuss this issue on this list and in Prague and more important at a possible TMCH summit in July that could include more of the technical folks and IP contingent and
of course the actual provider</span></span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><span style="color:black">Thanks</span></span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span class="apple-style-span"><span style="color:black">Jeff</span></span><span style="color:black"><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><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:11.0pt;font-family:"Calibri","sans-serif";color:black">From:
</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:black"><Rosette>, Kristina <<a href="mailto:krosette@cov.com">krosette@cov.com</a>><br>
<b>To: </b>"<a href="mailto:tmch-iag@icann.org">tmch-iag@icann.org</a>" <<a href="mailto:tmch-iag@icann.org">tmch-iag@icann.org</a>><br>
<b>Subject: </b>Re: [Tmch-iag] Trademark Clearinghouse IAG - Comments on Draft Implementation Model<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri","sans-serif";color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="color:black">In fairness to Brian, any arrows regarding the Data Location and Data Access comments should be aimed at me as I was the person in our drafting group who drafted that section.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black">And, of course, I support the comments in their entirety.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:black"> <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" style="margin-left:.5in"><b><span style="font-family:"Tahoma","sans-serif";color:black">From:</span></b><span style="font-family:"Tahoma","sans-serif";color:black">
<a href="mailto:tmch-iag-bounces@icann.org">tmch-iag-bounces@icann.org</a> [<a href="mailto:tmch-iag-bounces@icann.org">mailto:tmch-iag-bounces@icann.org</a>]
<b>On Behalf Of </b>Winterfeldt, Brian<br>
<b>Sent:</b> Friday, May 18, 2012 7:18 PM<br>
<b>To:</b> <a href="mailto:tmch-iag@icann.org">tmch-iag@icann.org</a><br>
<b>Subject:</b> [Tmch-iag] Trademark Clearinghouse IAG - Comments on Draft Implementation Model</span><span style="color:black"><o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">Dear Trademark Clearinghouse IAG,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">Please find below comments on various issues regarding the draft Trademark Clearinghouse Implementation Model (“Model”). I would like to reserve my right to comment after the service provider
is selected and announced and after any additional draft Trademark Clearinghouse Implementation Models.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><u><span style="color:black">Data Location and Data Access</span></u><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">The Model does not adequately address the concerns expressed by trademark owners about the potential for misuse and abuse of trademark data deposited with and contained in the Trademark
Clearinghouse.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">Local caching at the Registry, which the Model envisions, creates an environment in which a Registry can misuse and/or abuse trademark data. Indeed, there had been previous recommendations
by members of the IAG against permitting local caching at the Registry for this very reason. ICANN’s own consultant
<u>repeatedly</u> acknowledged in the 14 May IAG call that, under the Model, preventing misuse and/or abuse by a Registry is “not a technically solvable problem,” but is instead “a contractually solvable problem.” If ICANN adopts (or requires the Clearinghouse
Provider to adopt) the proposal to locate data through local caches at the Registry, then ICANN must impose contractual limitations to prevent and to address Registry misuse and/or abuse of trademark data. Those contractual limitations must be contained in
both the contract between the Clearinghouse Provider and the Registry <b><u>and</u></b> in the New gTLD Registry Agreement between ICANN and the Registry Operator. Violations of those contractual limitations should affect a Registry’s ability to use the Trademark
Clearinghouse and trigger ICANN Compliance action, respectively. Trademark owners have repeatedly been told in the context of the Registrar Accreditation Agreement that ICANN Compliance can only enforce against the contract. We have no reason to believe
that this is not true for Registries. <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">To be clear, the cryptographic approach should be implemented, but it requires supplementation with contractual limitations.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">Similarly, the proposal to impose rate limiting at the Registry-registrar level that was articulated by JAS Global Advisors in the 14 May IAG Call is recommended. To facilitate enforcement
of a rate limiting mechanism, it is also recommended that uniform language be developed for inclusion in Registry-Registrar agreements.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><u><span style="color:black">Penalties for Fraudulent TMCH Submission</span></u><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="color:black"> </span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">As an initial matter, the protections afforded by the TMCH benefit all stakeholders, whether they be registrars, registries or brand owners. As a result, an intentional fraudulent or bad-faith
submission is detrimental to all stakeholders and appropriate penalties should be levied against persons found to have acted fraudulently or in bad faith. For the sake of clarity, this comment is meant to address submissions of fraudulent or bad faith records
to the TMCH and not errors in the submission of legitimate records. <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">The current Draft Implementation Model dated April 13, 2012 (the “Model”), allows for the removal of any record that the TMCH accepted in error. While it is not yet clear how dispute mechanism
will actually work, 4.1.1 of the Model does allow for third-party challenges against accepted TMCH records. In such instances where a challenging party can show by a preponderance of the evidence that a challenged record was fraudulently submitted or submitted
in bad faith, the party responsible for submission of the original record should face penalties for abuse of the TMCH. While a wide range of penalties can be considered, parties found to have fraudulently submitted records, at a minimum, should have the offending
record removed in the first instance and be barred from taking advantage of the TMCH in the future for multiple instances.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><u><span style="color:black">Proof of Use</span></u><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">2.2 Validation for Proof of Use<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">A clear set of standards is necessary for evaluating proof of use submissions. ICANN has stated that a "single standard is desired to create an efficient and predictable process." However
it is not clear from the Model what that standard will be and what process will be put in place for evaluating proof of use submissions that are not standard. It is recommended that there be a higher level of review within the TMCH to evaluate proof of use
submissions that are questionable, and that there should be a process in place for objecting to false or misleading poof of use claims. These recommendations should be included in the TMCH Model document.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">2.2.2 Declaration<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">The language for the Declaration states "[Trademark Holder/Representative/Licensee/Agent] hereby certifies", and there was much discussion about who can submit information to the TMCH.
One of the IAG recommendations was that only the trademark holder or its agent or representative could make submissions, and that licensees should not be permitted to submit information on behalf of rights holders because they may not have rights that cover
making domain name registrations.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">The Declaration goes on to state ""that the trademarks set forth in this submission are currently in use in the manner set forth in the accompanying specimen; ... and that if, at any time,
the information contained in this submission is no longer accurate, the [Trademark Holder/Representative/Licensee/Agent] will notify the Clearinghouse within a reasonable time of that information which is no longer accurate, ...." If what is meant here relates
only to changes in the actual registration or validity of a mark, rather than updating the TMCH on changes in the specimen of use, the language should be revised. For example, do changes in the specimen of use, i.e. from using a mark in italics to using plain
block letters, require a new specimen of use to be submitted to the TMCH? The current language suggests that a new specimen would need to be submitted.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">2.2.3 Sample of Use<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">The standard that the sample "be an item that evidences an effort on behalf of the holder to communicate to a consumer so that the consumer can distinguish, without the possibility of confusion,
the products or services of one from those of another" is requiring the TMCH to make a legal judgment on what constitutes confusion that is beyond its purpose and scope. The phrase "without the possibility of confusion" should be stricken.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">The TMCH will require some guidance on what types of samples of use are acceptable. However, some items on the list, applications for business licenses, licenses to use the mark in question,
would not be considered bona fide trademark use, at least in the US. Additionally, other items such as letterhead/business cards/press releases may be problematic as they can be easily produced to fabricate use. Again, in the US, items such as business
names on letterhead/business cards/press releases do not necessarily constitute trademark use but merely business name use. Accordingly, it may be useful to request recommendations for a specific and exhaustive list of samples that can be submitted so as
to reduce the role and discretion of the TMCH in the evaluation process.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><u><span style="color:black">Matching Rules</span></u><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">During the IAG conference call, there was discussion concerning how the matching rules would be implemented, and in particular, how certain elements of a mark would be translated. The
Model states: <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:black">For processing Clearinghouse records for the purpose of Sunrise and Trademark Claims processes, matching rules specified in the Special Trademark Issues Review Team recommendations are
used. An “identical match” is defined as follows:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:black">Domain name consists of the complete and identical textual elements of the mark.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:black">a. spaces can be replaced by hyphens (and vice versa) or omitted;<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:black">b. only certain special characters in a trademark are spelled out with appropriate words describing it (@ and &);<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:black">c. punctuation or special characters in a mark that are unable to be used in a domain name may be (i) omitted or (ii) replaced by spaces, hyphens or underscores and still be considered
identical matches; and<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:1.0in"><span style="color:black">d. no plurals and no “marks contained” qualify.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">The Model acknowledges that "more work is needed" on this issue, but appears to limit that to determining which languages are relevant. As an initial matter regarding matching rules, all
matching rules should be determined before implementation of the Clearinghouse and administered solely by the Clearinghouse so as to reduce uncertainty among trademark owners and to reduce burdens on registries.
<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">It is agreed that words ought to be translated. However, attempting to define which languages are deserving, or relevant enough, to allow translation, seems to be an arbitrary and fruitless
undertaking. In other words, translation of words in an inherently imperfect and personal/cultural analysis that would be best left to the trademark owner.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">This theory was suggested by some members of the IAG that put forth the idea that a trademark registration owner should be able to provide a translation of its mark's content. This functionality
is important because in many languages symbols might have multiple meanings. For instance the + symbol can be translated in English as "and", "plus" or "positive". For example, Google + is branded as "Google Plus" not "Google And" or "Google Positive".
Moreover, as stated in the Draft Implementation Model, the genesis for the matching rules was the Special Trademark Issues Review Team Report, which clearly stated that the ""symbols", were, in fact, any "special characters", including but not limited to,
" ~ @ # ! § % ^ © and &". See the IRT Report at p. 19, footnote 15. This list is not exhaustive and may include hundreds, if not thousands, of special characters many of which have multiple and different meanings in different languages. Allowing the trademark
owner to designate the translation of its symbols relieves this burden from the TMCH and helps to keep costs down. A challenge process could be put into place for a translation that was false or fraudulent.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">Lastly, with respect to subsection (d) concerning plural and marks contained, we suggest that if TMCH policies were developed to allow an applicant to self-identify translations of element
of its mark, then the policy should be expanded to allow a trademark owner to designate other generic terms related to the trademark registration being entered in the TMCH. It is our understanding that a similar process had been implemented in the past by
.ASIA allowing registrants to submit a list of marks including other words contained in the Nice classification(s) of the trademark's registration.
<a href="http://www.wipo.int/classifications/nice/en/classifications.html">http://www.wipo.int/classifications/nice/en/classifications.html</a>. The text of Trademark Claims Notice in its current form with just minor revisions could provide such notice without
any chilling concerns toward domain name registrants.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><u><span style="color:black">Additional Verification Services</span></u><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">Regarding additional verification beyond identical matching, the Clearinghouse should not be tasked with additional verification duties. Adding these duties would only cause further delays
and costs, and is arguably beyond the Clearinghouse’s mandate. Moreover, given the wide range of possible registration policies, it may make sense for many registries to directly manage their own specific eligibility requirements.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><u><span style="color:black">Dispute Resolution Procedures</span></u><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">In line with the Trademark Clearinghouse’s mandate to hear Sunrise challenges, but not to decide legal claims, the Sunrise Dispute Resolution Procedure (SDRP) should be limited to the following
grounds: (1) where a Sunrise Applicant submitted a Sunrise Application that is not an exact match to a listed Clearinghouse registration, (2) where a Sunrise Application is based on one or more clear-cut unqualified listed registrations under the current SERs
that can be determined by objective data such as cancelled trademark registrations or registration dates, or (3) where a Sunrise Applicant has submitted fraudulent documents, including specimens, in support of a TMCH listing. This would decrease the likelihood
that the TMCH or third parties could unnecessarily delay sunrise registrations in order to litigate gray legal issues such as bona fide use and/or abandonment, and keep the TMCH within its mandate not to decide legal claims. This would also likely reduce
Sunrise Application deterrents to participation by trademark owners and any subsequent adverse impact on the financial success of open registries that sell domain name registrations and will rely on Sunrise Registrations to increase profit.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">Additionally, the two flow charts in the Executive Summary could do a better job of identifying which party is carrying out which action. In some portions of the charts, the acting party
is clearly identified (“Registry notifies”, “Clearinghouse notifies”, “Applicant reviews”, “Registrar captures”, etc.), but in others no party is identified, merely an action (“Seek”, “Provide”, “Confirm”, “Check”, “Display”, etc.).<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">_______________________________________________<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">Thank you,<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black">Brian<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><b><u><span style="font-size:12.0pt;font-family:Arrow;color:black">Brian J. Winterfeldt, Esq.</span></u></b><span style="font-size:11.0pt;color:black"><br>
</span><span style="font-family:Arrow;color:#00B0F0">Steptoe & Johnson LLP</span><span style="color:blue"><br>
</span><span style="font-family:Arrow;color:black">1330 Connecticut Avenue, NW</span><span style="color:black"><br>
</span><span style="font-family:Arrow;color:black">Washington, DC 20036</span><span style="color:black"><br>
</span><span style="font-family:Arrow;color:black">TEL 202.429.6260 | FAX 202.261.7547</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="font-size:11.0pt;color:black"><br>
</span><span style="font-family:Arrow;color:black">The information contained in this e-mail may be privileged, confidential, and protected from disclosure. If you are not the intended recipient, any dissemination, distribution or copying is strictly prohibited.
If you think that you have received this e-mail message in error, please e-mail the sender at “</span><span style="font-family:Arrow;color:#00B0F0"><a href="mailto:bwinterfeldt@steptoe.com"><span style="color:#00B0F0">bwinterfeldt@steptoe.com</span></a></span><span style="font-family:Arrow;color:black">.”
Thank you.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in"><span style="color:black"> <o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black"><o:p> </o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal"><span style="font-size:7.5pt;color:gray">Please NOTE: This electronic message, including any attachments, may include privileged, confidential and/or inside information owned by Demand Media, Inc. Any distribution or use of this communication
by anyone other than the intended recipient(s) is strictly prohibited and may be unlawful. If you are not the intended recipient, please notify the sender by replying to this message and then delete it from your system. Thank you.</span><span style="font-size:12.0pt;font-family:"Times New Roman","serif";color:black"><o:p></o:p></span></p>
</div>
<br>The contents of this message may be privileged and confidential. Therefore, if this message has been received in error, please delete it without reading it. Your receipt of this message is not intended to waive any applicable privilege. Please do not disseminate this message without the permission of the author. ****************************************************************************** Any tax advice contained in this email was not intended to be used, and cannot be used, by you (or any other taxpayer) to avoid penalties under the Internal Revenue Code of 1986, as amended.</body>
</html>