<!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.19170">
<STYLE><!--
/* Font Definitions */
@font-face
{font-family:Arrow;
panose-1:0 0 7 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","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:"Arial","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Arial","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:#1F497D;}
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:#1F497D;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:#1F497D;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:#1F497D;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:#1F497D;}
span.EmailStyle26
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:#1F497D;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:#1F497D;}
span.EmailStyle29
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:windowtext;}
.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>
<P
style="MARGIN: 0in 0in 0pt; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN style="FONT-FAMILY: Arial; FONT-SIZE: 10pt"></SPAN></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><SPAN
class=247494120-17022012>Dear IAG,<BR></SPAN></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal>I agree with Brian that EPP
should be the protocol of choice concerning queries or transactions with the
TMCH.<SPAN style="mso-spacerun: yes"> </SPAN>This is much preferred over
some non-EPP version of XML.<SPAN style="mso-spacerun: yes"> </SPAN>In
terms of performance, EPP has proven itself for the past 10 years in various
registry operations.</P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p> </o:p></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal>ICANN may want to announce a TMCH
vendor before consensus is reached on many of the TMCH protocols and
processes.<SPAN style="mso-spacerun: yes"> </SPAN>However, this may not be
that critical, as long as the selected vendor is not pre-disposed to any one
particular solution and can implement the eventual consensus approach.</P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p> </o:p></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal>In an ideal world, registries and
registrars want to be able to operate in complete independence.<SPAN
style="mso-spacerun: yes"> </SPAN>Where they need to rely on others, such
as the TMCH, then system redundancies and service-level agreements are called
for.<SPAN style="mso-spacerun: yes"> </SPAN>Performance concerns are
predominantly an issue during the processing of trademark claims.</P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p></o:p> </P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p><SPAN
class=247494120-17022012><FONT color=#0000ff><FONT color=#000000>Previous
discussions have raised whether data should be distributed to registries to
eliminate any dependence on the TMCH.</FONT> </FONT>But
p</SPAN></o:p>roviding copies of the TMCH data to each registry (or their
back-end operators) without the ability to control and monitor access is not
desirable for data security reasons. <SPAN
style="mso-spacerun: yes"> </SPAN>Distributing encrypted data in
packaged database applications is possible but not very practical.<SPAN
style="mso-spacerun: yes"> </SPAN></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p> </o:p></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal>However, the TMCH vendor should
be capable of distributing TMCH data globally while maintaining full control of
the data.<SPAN style="mso-spacerun: yes"> </SPAN>This would require the
TMCH vendor to locate multiple servers around the world. <SPAN
style="mso-spacerun: yes"> This may be the one exception to mandating
universal use of EPP. <o:p> </o:p></SPAN></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><SPAN
style="mso-spacerun: yes"></SPAN><o:p> </o:p></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal>For example, the TMCH could
mirror servers containing the list of claims notices<SPAN
class=247494120-17022012> and associated data</SPAN> within a global
network of <SPAN class=247494120-17022012>DNS </SPAN>servers around the
world.<SPAN style="mso-spacerun: yes"> </SPAN>Multiple redundancies are
provided through the use of Anycast DNS.<SPAN
style="mso-spacerun: yes"> <SPAN class=247494120-17022012>The TMCH
data becomes distributed but only to TMCH-controlled servers.
</SPAN></SPAN>Such a global network would ensure <SPAN
class=247494120-17022012>optimum </SPAN>response <SPAN
class=247494120-17022012>time </SPAN>and <SPAN
class=247494120-17022012>near 100% </SPAN>up-time availability for registries
while maintaining the security of the data.<SPAN class=247494120-17022012>
Note that there any many registries and DNS service providers that already do
this.</SPAN><SPAN style="mso-spacerun: yes"> <SPAN
class=247494120-17022012>In addition, </SPAN><SPAN
class=247494120-17022012>the TMCH can log every claims request for analysis of
possible data mining. </SPAN></SPAN></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><SPAN
style="mso-spacerun: yes"><SPAN
class=247494120-17022012></SPAN></SPAN><o:p></o:p> </P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><B
style="mso-bidi-font-weight: normal">Detailed Comments to T2 and
T3:<o:p></o:p></B></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p> </o:p></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><B
style="mso-bidi-font-weight: normal">T2:<SPAN style="mso-spacerun: yes">
</SPAN>Data Access<o:p></o:p></B></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal>A comment on the “Public” option,
which is defined as “Information may be published or distributed without
restriction”</P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p> </o:p></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal>I don’t think there is any TMCH
data that should be published or distributed without restrictions.<SPAN
style="mso-spacerun: yes"> </SPAN>All data would then be categorized as
“internal”, “partner” or “restricted”.</P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p> </o:p></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p> </o:p></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><B
style="mso-bidi-font-weight: normal">T3: Communication
Protocols<o:p></o:p></B></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal>Here are some specific responses
to the blanks in the T3 Protocol Table:</P>
<UL style="MARGIN-TOP: 0in" type=disc>
<LI
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in"
class=MsoNormal><?xml:namespace prefix = st1 ns =
"urn:schemas-microsoft-com:office:smarttags" /><st1:City w:st="on"><st1:place
w:st="on">Sunrise</st1:place></st1:City> 6: EPP</LI>
<LI
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in"
class=MsoNormal><st1:City w:st="on"><st1:place
w:st="on">Sunrise</st1:place></st1:City> 7-8a: EPP</LI>
<LI
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in"
class=MsoNormal>Claims 4-5. EPP or DNS.<SPAN style="mso-spacerun: yes">
</SPAN>This is where the TMCH can log every claims request for analysis of
possible data mining</LI>
<LI
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in"
class=MsoNormal>Claims 10-11a: EPP</LI>
<LI
style="MARGIN: 0in 0in 0pt; mso-list: l0 level1 lfo1; tab-stops: list .5in"
class=MsoNormal>Claims 13-14a: EPP.<SPAN
style="mso-spacerun: yes"> <SPAN
class=247494120-17022012>***</SPAN></SPAN>I am actually proposing the flow be
reversed here: <SPAN class=247494120-17022012>for </SPAN><SPAN
class=247494120-17022012>the transaction to be </SPAN>initiated by the
TMCH<SPAN class=247494120-17022012> with a query t</SPAN>o <SPAN
class=247494120-17022012>the </SPAN>Registry, whereby the TMCH discovers which
of the requested claims resulted in a registration<SPAN
class=247494120-17022012>. I think this is more
efficient</SPAN> since the Registry has no visibility of which
registrations displayed a claims notice<SPAN class=247494120-17022012> and
would need to perform extra work to determine which registrations matched a
claim.</SPAN></LI></UL>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p><SPAN
class=247494120-17022012>Thank you.</SPAN></o:p></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p> </o:p></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal>Tom Barrett</P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal>EnCirca, Inc</P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal>400 West Cummings park,
<st1:address w:st="on"><st1:Street w:st="on">Suite</st1:Street>
1725</st1:address></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><st1:place w:st="on"><st1:City
w:st="on">Woburn</st1:City>, <st1:State w:st="on">MA</st1:State> <st1:PostalCode
w:st="on">01801</st1:PostalCode></st1:place></P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal>+1.781.942.9975 ext. 11</P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal>+1.781.492.1315 (cell)</P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal>+1.781.823.8911 (fax)</P>
<P style="MARGIN: 0in 0in 0pt" class=MsoNormal><o:p> </o:p></P></DIV><BR>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> tmch-iag-bounces@icann.org
[mailto:tmch-iag-bounces@icann.org] <B>On Behalf Of </B>Winterfeldt,
Brian<BR><B>Sent:</B> Friday, February 17, 2012 2:41 PM<BR><B>To:</B>
tmch-iag@icann.org<BR><B>Subject:</B> [Tmch-iag] Trademark Clearinghouse IAG -
Issue T3 and Issue N2<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Dear Trademark
Clearinghouse IAG,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Please see my below
comments on the following issues:<o:p></o:p></SPAN></P>
<DIV
style="BORDER-BOTTOM: windowtext 1.5pt solid; BORDER-LEFT: medium none; PADDING-BOTTOM: 1pt; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0in">
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: #1f497d; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></P></DIV>
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: #1f497d">Issue
T3<o:p></o:p></SPAN></B></P>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Dear Trademark
Clearinghouse IAG,</SPAN><o:p></o:p></P>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">The issue has been
raised whether to use EPP as the communication protocol of choice for
communications between the Trademark Clearinghouse and the registries and
registrars. While I understand that use of DNS or https in conjunction
with xml are viable alternatives, I still believe that EPP should be the
protocol of choice. First, most registrars and registries already possess
a working familiarity with EPP as they use it in their day-to-day operations,
and it will be a required protocol between all registries and registrars in all
new gTLDs. Second, EPP was originally designed with the flexibility and
adaptability in mind to extend its use in situations such as this.
Finally, the implementation costs for EPP are already well-known by all
the involved parties, including ICANN itself. To deviate from EPP would
add more unknown costs and implementation variables when a workable, easily
implemented solution of EPP is readily available.</SPAN><o:p></o:p></P>
<DIV
style="BORDER-BOTTOM: windowtext 1.5pt solid; BORDER-LEFT: medium none; PADDING-BOTTOM: 1pt; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0in">
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P></DIV>
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: #1f497d">Issue
N2<o:p></o:p></SPAN></B></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Dear Trademark
Clearinghouse IAG,</SPAN><o:p></o:p></P>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">With respect to Issue
N2, I agree that there should be penalties for any individuals making fraudulent
submissions to the Clearinghouse. If an individual does indeed make a
fraudulent submission, then I believe that the appropriate penalty should be to
forfeit that listing. Should this individual make repeated fraudulent
submissions, however, then I believe a lifetime ban from the Clearinghouse is an
appropriate penalty.<o:p></o:p></SPAN></P>
<DIV
style="BORDER-BOTTOM: windowtext 1.5pt solid; BORDER-LEFT: medium none; PADDING-BOTTOM: 1pt; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: medium none; BORDER-RIGHT: medium none; PADDING-TOP: 0in">
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Regarding the time
period for revalidation in the Clearinghouse, I believe that annual or biannual
revalidation periods create unduly burdensome reporting requirements for
trademark owners, especially if a markholder chooses to register a significant
number of marks. Accordingly, I think that the revalidation period in the
Clearinghouse should match the timeframe for renewal required in the applicant’s
trademark jurisdiction (<I>e.g.</I> a markholder in U.S. would submit his
revalidation to the Clearinghouse when he also submits the corresponding renewal
to the USPTO).<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></P></DIV>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Thank
you,<o:p></o:p></SPAN></P>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Brian<o:p></o:p></SPAN></P>
<P class=MsoNormal><B><U><SPAN style="FONT-FAMILY: Arrow; COLOR: black">Brian J.
Winterfeldt, Esq.</SPAN></U></B><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 11pt"><BR></SPAN><SPAN
style="FONT-FAMILY: Arrow; COLOR: #00b0f0; FONT-SIZE: 10pt">Steptoe &
Johnson LLP</SPAN><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: blue; FONT-SIZE: 10pt"><BR></SPAN><SPAN
style="FONT-FAMILY: Arrow; COLOR: black; FONT-SIZE: 10pt">1330 Connecticut
Avenue, NW</SPAN><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><BR></SPAN><SPAN
style="FONT-FAMILY: Arrow; COLOR: black; FONT-SIZE: 10pt">Washington, DC
20036</SPAN><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; COLOR: black; FONT-SIZE: 10pt"><BR></SPAN><SPAN
style="FONT-FAMILY: Arrow; COLOR: black; FONT-SIZE: 10pt">TEL 202.429.6260 | FAX
202.261.7547</SPAN><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 11pt">
<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 11pt"><BR></SPAN><SPAN
style="FONT-FAMILY: Arrow; FONT-SIZE: 10pt">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 style="COLOR: #00b0f0"><A
href="mailto:bwinterfeldt@steptoe.com"><SPAN
style="COLOR: #00b0f0">bwinterfeldt@steptoe.com</SPAN></A></SPAN>.” Thank
you.</SPAN><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 11pt"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></P>
<P style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto"
class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P></DIV>
<HR SIZE=1 noShade>
<A></A>
<P align=left color="#000000" avgcert??>No virus found in this
message.<BR>Checked by AVG - <A
href="http://www.avg.com">www.avg.com</A><BR>Version: 2012.0.1913 / Virus
Database: 2112/4815 - Release Date: 02/17/12</P></BODY></HTML>