<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div>Karen,</div>
<div><br>
</div>
<div>Thanks for the update on the timing of the comments and the call. Is there any update to the timing of the reveal of the TMCH provider? Do you believe we will have the provider on the call that is scheduled for the week of May 14-18 to discuss implementation? </div>
<div><br>
</div>
<div>Jeff</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>Karen Lentz <<a href="mailto:karen.lentz@icann.org">karen.lentz@icann.org</a>><br>
<span style="font-weight:bold">To: </span>"<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>
<span style="font-weight:bold">Subject: </span>Re: [Tmch-iag] comments on draft Trademark Clearinghouse implementation model<br>
</div>
<div><br>
</div>
<div 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">
<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;}
/* 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
{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.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.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]-->
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; ">All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; ">Thank you for the comments and the interest in having a call. I am working on scheduling a call during the week of May 14-18. In light of this,
comments can continue to be submitted through <b>Friday, 18 May</b>. I will provide more call details as soon as I can confirm the date/time.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; ">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; ">Karen Lentz<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; ">ICANN<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125); font-family: Calibri, sans-serif; "><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; "> Hong Xue [<a href="mailto:hongxueipr@gmail.com">mailto:hongxueipr@gmail.com</a>]
<br>
<b>Sent:</b> Tuesday, May 01, 2012 2:54 AM<br>
<b>To:</b> Karen Lentz<br>
<b>Cc:</b> <a href="mailto:tmch-iag@icann.org">tmch-iag@icann.org</a><br>
<b>Subject:</b> Re: [Tmch-iag] Keith Barritt comments on draft Trademark Clearinghouse implementation model<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
Dear All,<br>
<br>
I agree with the proposal that a call be scheduled to discuss the details of the implementation model. Q&A would be useful. If taken the call into account, the commentary period should be reasonably extended.
<br>
<br>
With respect to the substance of the draft, I welcome its reference to the IDN readiness. "The Clearinghouse will accept trademark<br>
information in its native form (i.e., using the Unicode character set); specific variant character mappings must be handled by the<br>
registry." It seems each Registry are obliged to handle IDN variants issues but are not provided any guidance for handling. It would inevitably result in discrepancies. Also, should a Registry notify the TMCH of its variants management policy so as to ensure
TMCH to implement that policy in authentication and validation? I feel many details are missing and gaps are wide open.
<br>
<br>
<br>
P.33 refers to "Local Caching at Registry", does it refer to new gTLD registries, not local CH providers? If data could be locally cached, why then service provider must be centralized as one?<br>
<br>
Hong<br>
<br>
-- <br>
Dr. Hong Xue<br>
Professor of Law<br>
Director of Institute for the Internet Policy & Law (IIPL)<br>
Beijing Normal University<br>
<a href="http://iipl.org.cn/" target="_blank">http://www.iipl.org.cn/</a><br>
19 Xin Jie Kou Wai Street<br>
Beijing 100875 China<br>
<br>
<o:p></o:p></p>
<div>
<p class="MsoNormal">On Tue, May 1, 2012 at 3:10 AM, Karen Lentz <<a href="mailto:karen.lentz@icann.org" target="_blank">karen.lentz@icann.org</a>> wrote:<o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Keith, thank you for these comments which we are reviewing.
</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">As a reminder to all, the draft implementation model and summary of IAG input are available on the wiki and comments are requested by Friday, 4 May.
I will send out a reminder notice shortly.</span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Best regards,</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">Karen Lentz</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D">ICANN</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="color:#1F497D"> </span><o:p></o:p></p>
</div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; "> Keith Barritt [mailto:<a href="mailto:barritt@fr.com" target="_blank">barritt@fr.com</a>]
<br>
<b>Sent:</b> Wednesday, April 25, 2012 4:07 PM<br>
<b>To:</b> Karen Lentz; <a href="mailto:tmch-iag@icann.org" target="_blank">tmch-iag@icann.org</a><br>
<b>Subject:</b> Keith Barritt comments on draft Trademark Clearinghouse implementation model</span><o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Dear All:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I appreciate and commend all the hard work that ICANN has put into summarizing input from the IAG and in preparing the draft implementation model. However, I do have a few comments
below on the draft implementation model.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">My primary concern is that there are many instances where the recommendations are somewhat vague and the relative roles of ICANN and the TMC are unclear. In the absence of specific
requirements from ICANN upon which to comment, I am concerned that at some point in the future we will be presented with a “final” document that was not fully vetted by the community For example:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Page 4: “Standards ensuring that the Clearinghouse is in the role of ‘fact verifier’ will be in place, limiting the discretaion that can occur in any result, and creating consistency across the process.” While the goal is beyond question, the question remains
as to precisely what those standards will be.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Page 10: It is unclear to me if ICANN is proposing to allow entities other than the rights holder to obtain Sunrise registrations. Page 10 refers to the submission of “assignment documentation” if the names do not match, but does not clarify if licensees
can qualify. Section 6.2.3 of the “Trademark Clearinghouse” Section of the final Applicant Guidebook states that the “proposed” Sunrise eligibility requirements include ownership of a mark, so a licensee would not qualify under the earlier “proposed” requirements,
but what is the final rule going to be? As I have commented during the IAG process, I believe only the rights holder as reflected in the TMC’s records should be eligible, for ease of administration and to allow third parties to challenge undeserved Sunrise
registrations. <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Page 11: “Penalties should be in place to help deter fraudulent submissions.” While we all want to deter fraud, it would be helpful to have an opportunity to comment on specific proposed penalties and their triggers. See also page 17 that states “Penalties
for failing to keep the information current can include removal of a record.” The “can include” leaves the full scope of potential penalties unknown. Will ICANN be specifying the penalties, or will the TMC have discretion that is not subject to community
input?<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Page 12: It is not clear what “equitable treatment” with respect to verifying registration numbers really means. Does it mean that all rights holders should pay the same to have their rights recorded in the TMC, or that rights holders from jurisdictions where
information is not on-line should pay more, since the verification process will be more complex?<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Page 13: “[I]t is recommended that the TMC verify that the court existed as of the date of the order . . .” Is this really an ICANN “recommendation” or mandate? Will the TMC have discretion on how to verify certain factual information?
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Page 15: Is the “recommended” declaration a suggestion or mandate to the TMC? Will the TMC have discretion on what the declaration will say?<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Page 16: Is the “recommendation” that the sample of use be of a particular type a mere suggestion or mandate to the TMC? I also believe that the “without the possibility of confusion” standard is asking the TMC to make a legal judgment beyond its scope.
I understand and agree that the TMC needs some discretion in the particulars of what to accept. However, I note that under U.S. trademark law at least, an application for a business license would not be considered use of the mark, as it is not use before
the public in a trademark sense. Likewise, the appearance of the mark in a license is not public use. Thus, these two examples should be stricken from the list.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Page 18: “An authenticated Clearinghouse record should be renewed once per year. . . . The renewal process should not require resubmission or re-authentication of information that was previously provided. . . . [i]t is recommended that the annual renewal
for the record not require submission of a new sample [of proof of use]. However, submission of a curent sample should be required at a longer interval (e.g. every five years). . .” Are these suggestions or mandates to the TMC? Will the TMC have discretion
in how often certain information needs to be renewed?<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Page 19: “The Clearinghouse provider should publish and supply notice of any grace period procedures that are instituted.” Will ICANN be mandating a grace period, or will the TMC have discretion?<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:.5in">
Page 20: “A Sunrise code should be unique per mark.” If a “Sunrise code” approach is adopted so that a TMC record can be relied upon only once per Sunrise per new gTLD, I believe this sentence should be “A Sunrise code must be unique per mark.”<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Other issues include:<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>1)<span style="font-size:7.0pt"> </span>I continue to believe “verifies” as a single verb suffices in place of “authenticates” and “validates.” With each use of “authenticate” or “validate” we will likely see terms like “authenticate the contact information”
and “validate the proof of use.” Why not just “verify” for both? It has been suggested these are two different activities, but so is checking an elecronic database to verify the trademark registration number and reviewing a paper record to verify a registration’s
expiration date, but we don’t feel compelled to have two verbs for these different activities. I suspect this is a lost cause, but I continue to resist the unnecessary introduction of terms that have specialized meaning when in practice we will likely need
to specify what we mean anyway. I can see the conversations with clients now: <o:p>
</o:p></p>
<p> <o:p></o:p></p>
<p style="margin-left:1.0in">Lawyer: “Your filing has been authenticated by the TMC, but not yet validated.”
<o:p></o:p></p>
<p style="margin-left:1.0in"> <o:p></o:p></p>
<p style="margin-left:1.0in">Client: “Huh?”<o:p></o:p></p>
<p style="margin-left:1.0in"> <o:p></o:p></p>
<p style="margin-left:1.0in">Lawyer: “The TMC has verified that your trademark registration data is correct, but hasn’t yet verified your proof of use.”<o:p></o:p></p>
<p style="margin-left:1.0in"> <o:p></o:p></p>
<p style="margin-left:1.0in">Client: “Oh, why didn’t you say so in the first place?!”<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>2)<span style="font-size:7.0pt"> </span>I commend ICANN for abandoning the use of “registrant” to refer to a trademark rights holder who has recorded its rights with the TMC. However, I note that on page 37 the term “registrant” is evidently inadvertently
used to refer to a rights holder that is applying for a Sunrise registration.<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>3)<span style="font-size:7.0pt"> </span>The declaration for submission of information to the TMC referred to in Section 2.1.5 on page 12 should be “to the best of the submitter’s knowledge,” similar to the declaration to accompany proof of use (see
page 15). <o:p></o:p></p>
<p> <o:p></o:p></p>
<p>4)<span style="font-size:7.0pt"> </span>I believe more detail should be provided regarding Sunrise eligibility disputes, and particularly regarding proof of use issues. ICANN should specify that a third party can challenge a Sunrise registration based
on lack of use. The role of the TMC and registry in such disputes should be clarified (see pages 42-43). Under Section 6.2.4 of the “Trademark Clearinghouse” section of the AGB, the TMC is to hear challenges regarding Sunrise eligibility requirements, which
would include proof of use.<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>5)<span style="font-size:7.0pt"> </span>Will rights holders be able to submit information to the TMC only for Sunrise, and opt out of the Claims service?
<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>6)<span style="font-size:7.0pt"> </span>Should the TMC validate proof of use only when a Sunrise application is filed to reduce the burden of validation of records for which proof of use may never be an issue, or is it unrealistic to expect the TMC
to be able to validate fewer records at Sunrise but on short notice?<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>7)<span style="font-size:7.0pt"> </span>Can a rights holder submit proof of use after a trademark is recorded in the TMC, in anticipation of a particular Sunrise filing?<o:p></o:p></p>
<p> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Keith Barritt<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><img border="0" width="30" height="28" id="_x0000_i1025" src="cid:image001.jpg@01CD2785.2E58AF30" alt="Description: Description: Description: Description: http://fishnet.fr.com/C15/Marketing%20Department%20Policies/Fish%20Logos/frlogo.bmp">Fish
& Richardson P.C.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">1425 K Street N.W.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Suite 1100<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Washington, DC 20005<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Phone:
<a href="tel:%28202%29%20626-6433" target="_blank">(202) 626-6433</a><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Fax:
<a href="tel:%28202%29%20783-2331" target="_blank">(202) 783-2331</a><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><a href="http://www.fr.com" target="_blank">www.fr.com</a><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; ">From:</span></b><span style="font-size: 10pt; font-family: Tahoma, sans-serif; "><a href="mailto:tmch-iag-bounces@icann.org" target="_blank">tmch-iag-bounces@icann.org</a><a href="mailto:[mailto:tmch-iag-bounces@icann.org]" target="_blank">[mailto:tmch-iag-bounces@icann.org]</a><b>On
Behalf Of </b>Karen Lentz<br>
<b>Sent:</b> Friday, April 13, 2012 8:34 PM<br>
<b>To:</b> <a href="mailto:tmch-iag@icann.org" target="_blank">tmch-iag@icann.org</a><br>
<b>Subject:</b> [Tmch-iag] IAG summary and draft Clearinghouse implementation model</span><o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Dear colleagues,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Please see attached 2 documents: (1) a draft implementation model for the Trademark Clearinghouse (reflecting many of the inputs from the IAG), and (2) a summary report compiling
the feedback received from the IAG process. <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">These documents are for your review and comment – please submit any comments to the list by
<b>Friday, 4 May</b> so that we can also compile these and take them into account.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">We do not have any additional IAG calls scheduled currently, although we can schedule a call, or an open webinar to walk through the model, if there is interest in doing so.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">These materials have also been posted on the wiki at
<a href="https://community.icann.org/display/cctrdmrkclrnghsiag/Documents" target="_blank">
https://community.icann.org/display/cctrdmrkclrnghsiag/Documents</a>. We look forward to your comments.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b> </b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Best regards,<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Karen Lentz<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">ICANN<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><br>
<br>
<span style="font-size: 9pt; font-family: 'Courier New'; ">****************************************************************************************************************************<br>
This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized use or disclosure is prohibited. If you are not the intended recipient, please contact the sender by reply email and
destroy all copies of the original message. <br>
<br>
IRS CIRCULAR 230 DISCLOSURE: Any U.S. tax advice contained in this communication (including any attachments) is not intended or written to be used, and cannot be used, for the purpose of (i) avoiding penalties under the Internal Revenue Code or (ii) promoting,
marketing or recommending to another party any transaction or matter addressed herein.(FR08-i203d)<br>
****************************************************************************************************************************
</span><o:p></o:p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
tmch-iag mailing list<br>
<a href="mailto:tmch-iag@icann.org">tmch-iag@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/tmch-iag" target="_blank">https://mm.icann.org/mailman/listinfo/tmch-iag</a><o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<br clear="all">
<o:p></o:p></p>
</div>
</div>
</div>
</span><br>
<hr>
<font face="Arial" color="Gray" size="1">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.<br>
</font>
</body>
</html>