<!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 http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.17080" name=GENERATOR>
<STYLE>@font-face {
font-family: Calibri;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
P.MsoListParagraph {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; mso-style-priority: 34
}
LI.MsoListParagraph {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; mso-style-priority: 34
}
DIV.MsoListParagraph {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt 0.5in; FONT-FAMILY: "Calibri","sans-serif"; mso-style-priority: 34
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-compose
}
.MsoChpDefault {
FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: export-only
}
DIV.WordSection1 {
page: WordSection1
}
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 lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=402521303-14122011>All, </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=402521303-14122011></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=402521303-14122011>With apologies for the delay, here are my
comments.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=402521303-14122011></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=402521303-14122011><U>General</U>: <FONT face=Arial color=#0000ff
size=2><SPAN class=402521303-14122011>Please stop using "collides" and
"collision" when referring to the match. Doing so introduces new
terminology (the last thing we need in ICANNland) that is unnecessary.
It's a match, not a collision. </SPAN></FONT>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=402521303-14122011></SPAN></FONT> </DIV></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=402521303-14122011><U>P3</U>: </SPAN></FONT><FONT face=Arial
color=#0000ff size=2><SPAN class=402521303-14122011>I recommend against Approach
1 for the reasons noted by Brian and Stacey. Because of my concerns about
the security of the data in the Clearinghouse and to minimize the potential for
abuse, I have a slight preference for Approach 3 over Approach 2.
</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=402521303-14122011></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=402521303-14122011><U>P5</U>: I support Approach 2 for the reasons
set out by Brian and Stacey. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=402521303-14122011></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=402521303-14122011><U>T1</U>: I support Approach 1 because of
concerns about the potential abuse and misuse of TMCH data. Even
if ICANN is willing to amend the new gTLD Registry Agreement and both ICANN
and RrSG are willing to amend the RAA to explicitly prohibit abuse and misuse of
TMCH data and to impose penalties for such misuse and abuse, there
serious concerns in the trademark community about ICANN Compliance's capacity to
handle the other compliance issues that will likely arise in connection with the
addition of potentially hundreds of new registries - let alone this issue.
The security of the data in the TMCH and its vulnerability to abuse and misuse
is a very significant concern to the trademark owners with whom I've raised the
issue. An implementation decision that does not fully address
these concerns has the potential to impact drastically (and negatively) the
willingness of trademark owners to deposit their data. After trumpeting
the TMCH so vigorously (and citing to brand owner participation in this group in
Senate and House testimony), it would be ironic if ICANN itself undermined the
utility of the TMCH and trademark owner willingness to use
it. </SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=402521303-14122011></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=402521303-14122011>I plan to be on the process call, but currently have a
conflict that will prevent my attendance on the technical
call.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=402521303-14122011></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=402521303-14122011><!-- Converted from text/rtf format -->
<P><SPAN lang=en-us><FONT face=Arial size=2>Sincerely yours,</FONT></SPAN>
<BR><SPAN lang=en-us><FONT face=Arial size=2>Kristina </FONT></SPAN></P>
<P><SPAN lang=en-us><FONT face=Arial size=2>Kristina Rosette</FONT></SPAN>
<BR><SPAN lang=en-us><FONT face=Arial size=2>Covington & Burling
LLP</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial size=2>1201 Pennsylvania
Avenue, N.W.</FONT></SPAN> <BR><SPAN lang=en-us><FONT face=Arial
size=2>Washington, DC 20004</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial size=2>voice: 202.662.5173</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial size=2>fax: 202.778.5173</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial size=2>krosette@cov.com</FONT></SPAN> <BR><SPAN lang=en-us><FONT
face=Arial size=2>www.cov.com/krosette</FONT></SPAN> </P>
<P><SPAN lang=en-us><I><FONT face=Arial size=2>This message is from a law firm
and may contain information that is confidential or legally privileged. If
you are not the intended recipient, please immediately advise the sender by
reply e-mail that this message has been inadvertently transmitted to you and
delete this e-mail from your system. Thank you.
</FONT></I></SPAN></P></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=402521303-14122011></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2></FONT><BR> </DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> tmch-iag-bounces@icann.org
[mailto:tmch-iag-bounces@icann.org] <B>On Behalf Of </B>Karen
Lentz<BR><B>Sent:</B> Wednesday, December 07, 2011 2:44 PM<BR><B>To:</B>
tmch-iag@icann.org<BR><B>Subject:</B> [Tmch-iag] Materials for 16 Dec 11 IAG
calls<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=WordSection1>
<P class=MsoNormal>Dear Colleagues,<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Thanks again for the useful submissions and participation on
the last IAG call on 30 November. <BR><BR>For those who were not able to
attend, materials from the call are posted<BR>at <A
href="https://community.icann.org/display/cctrdmrkclrnghsiag/Home">https://community.icann.org/display/cctrdmrkclrnghsiag/Home</A>,
including<BR>slides, documents, chat transcript and audio
recording.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Note that any follow up submissions on the issues P1 and P2
are due by <B>Monday,</B> <B>12 December</B>. We’ll provide a brief update
to those 2 issues after review of all the materials.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><B>Schedule<o:p></o:p></B></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>For the call schedule going forward, note that there are 2
tracks that will proceed in parallel: the process track (focusing on
business process development, as now underway) and the technical track (focusing
on technical implementation issues).<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Therefore, on 16 December, there will be 2 calls taking
place:<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoListParagraph
style="TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"><![if !supportLists]><SPAN
style="mso-list: Ignore">1.<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN><![endif]>Process call (issues P3 and P5) at <B>13:00
UTC</B>.<o:p></o:p></P>
<P class=MsoListParagraph
style="TEXT-INDENT: -0.25in; mso-list: l0 level1 lfo2"><![if !supportLists]><SPAN
style="mso-list: Ignore">2.<SPAN
style="FONT: 7pt 'Times New Roman'">
</SPAN></SPAN><![endif]>Technical call (issues T1 and T3) at <B>16:00
UTC</B>.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Both calls are scheduled for 90 minutes and will use the
existing dial-in number and Adobe Connect room.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>You may choose to attend both calls, if you wish, or focus
only on one you are interested in. The relevant documents for both are
attached.<BR><BR><o:p></o:p></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><B>Process
Track<o:p></o:p></B></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt">Issue# P3 (Responsibility for
Trademark Holder Registration Notice) <o:p></o:p></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt">Issue# P5 (Responsibility to
Perform Trademark Claims Checks) <o:p></o:p></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt">We will discuss these topics,
informed by your written comments, on the <B>16 Dec call</B>. Please
submit your written comments to these issues by <B>13 Dec 2011</B> (23:59 UTC)
to the mailing list.<BR><BR>As discussed previously, we are ultimately seeking
your recommendations<BR>for either (1) one of the proposed options in the
document or (2) your<BR>suggestions for alternatives that you believe to be more
attractive and<BR>that should be considered.<BR><BR>In your written comments,
please make sure to indicate: (a) the issue<BR>number (P3 or P5), (b) the
recommended option or alternative for the issue,<BR>(c) rationale (consideration
of advantages and how any disadvantages could<BR>be minimized) and (d) any other
comments.<BR><BR><B>Technical Track</B><o:p></o:p></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt">Issue# T1 (Data Locations)
<o:p></o:p></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt">Issue# T3 (Communication
Protocols) <o:p></o:p></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt">We will discuss these topics,
informed by your written comments, on the <B>16 Dec call</B>. Please
submit your written comments to these issues by <B>13 Dec 2011</B> (23:59) UTC
to the mailing list.<BR><BR>We are ultimately seeking your recommendations for
either (1) one of the<BR>proposed options in the document or (2) your
suggestions for alternatives<BR>that you believe to be more attractive and that
should be considered.<BR><BR>In your written comments, please make sure to
indicate: (a) the issue<BR>number (T1 or T3), (b) the recommended option
or alternative for the issue,<BR>(c) rationale (consideration of advantages and
how any disadvantages could<BR>be minimized) and (d) any other
comments.<BR><BR>We look forward to hearing from you.<BR><BR>Karen
Lentz<BR>ICANN<BR><BR><o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><BR><BR><o:p></o:p></P></DIV></BODY></HTML>