<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Just to comment on Griffin's characterization of "proposed revisions" versus "prior version"--the "context" language Paul is commenting on was, as far as I can tell, added by Staff and not previously agreed to by the WG, so it shouldn't be characterized as
somehow the default. I think the best course of action might be simply to remove that additional language, which as Paul notes is basically a third restatement of text we agreed to but with small differences that can only risk confusion.</div>
<div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature">
<div>
<div style="font-family:Tahoma; font-size:13px">
<div style="font-family:Tahoma; font-size:13px">
<div><br>
</div>
Rebecca Tushnet</div>
<div style="font-family:Tahoma; font-size:13px">Frank Stanton Professor of First Amendment Law, Harvard Law School<br>
703 593 6759 </div>
</div>
</div>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> GNSO-RPM-WG <gnso-rpm-wg-bounces@icann.org> on behalf of Griffin Barnett <Griffin@Winterfeldt.law><br>
<b>Sent:</b> Monday, October 26, 2020 11:47 AM<br>
<b>To:</b> Paul Tattersfield <gpmgroup@gmail.com>; Kathy Kleiman <kathy@kathykleiman.com><br>
<b>Cc:</b> gnso-rpm-wg <gnso-rpm-wg@icann.org><br>
<b>Subject:</b> Re: [GNSO-RPM-WG] Edits and updates</font>
<div> </div>
</div>
<style>
<!--
@font-face
{font-family:Helvetica}
@font-face
{font-family:"Cambria Math"}
@font-face
{font-family:Calibri}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif}
a:link, span.x_MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.x_MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
span.x_EmailStyle17
{font-family:"Calibri",sans-serif;
color:#1F497D}
.x_MsoChpDefault
{}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.x_WordSection1
{}
-->
</style>
<div lang="EN-US" link="blue" vlink="purple">
<div class="x_WordSection1">
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">Paul,</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">I don’t agree with your proposed revisions to this text. I think the previous language more accurately reflected the WG discussions. First, “TMCH Validation
Provider” is not a new concept – we have used this term before to specify Deloitte as compared to IBM who is a “TMCH Provider” but is specifically the database provider and does not perform the validation role. I think it is a useful distinction that should
be preserved for the sake of clarity. Further, your proposed revised text starting with “(1) mandatory RPMs should only be for word marks….” does not fully capture the appropriate scope of what we agreed to in our recommendations, and also moves away from
the crux of the distinction being drawn in that section which relates to appropriate treatment of “trademarks” versus GIs and other types of source indicators that are not “trademarks” specifically.
</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">Accordingly, I would oppose the adoption of these proposed revisions and support the prior version of the text here.</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">Thank you,</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D">Griffin</span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></p>
<div class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:black">
<hr size="2" width="264" noshade="" align="left" style="width:2.75in; color:#4EAAE8">
</span></div>
<table class="x_MsoNormalTable" border="0" cellspacing="0" cellpadding="0" style="margin-left:5.8pt; border-collapse:collapse">
<tbody>
<tr>
<td width="112" style="width:84.2pt; padding:0in 5.4pt 0in 5.4pt">
<p class="x_MsoNormal" align="center" style="text-align:center"><a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.winterfeldt.law_&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=E-M4OQvQBo8UWqE1LwEiDR3PcWlfM0I-0jiI1c4ous0&m=ZHRQkYYyLz4uFHkt_VQWEZULSpI3PkaAjyjWZkOXjOk&s=9Us2eE6sb1SD8PacT308SUf6kzvxR73vvgOi02IVpD4&e="><img border="0" width="72" height="54" align="left" hspace="12" alt="https://daks2k3a4ib2z.cloudfront.net/59358b8cf7332631232417e8/595fb59d73c5b113a1d2a61b_WIPG_LogoMark.png" title="" data-outlook-trace="F:1|T:1" src="cid:image002.png@01D6AB8D.CFD59DB0"></a><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:black"></span></p>
</td>
<td width="181" valign="top" style="width:135.9pt; padding:0in 5.4pt 0in 5.4pt">
<p class="x_MsoNormal"><b><span style="font-size:10.0pt; font-family:"Calibri",sans-serif; color:black">Griffin M. Barnett</span></b><span style="font-size:10.0pt; font-family:"Calibri",sans-serif; color:black"></span></p>
<p class="x_MsoNormal"><span style="font-size:10.0pt; font-family:"Calibri",sans-serif; color:black">Associate</span></p>
<p class="x_MsoNormal"><span style="font-size:10.0pt; font-family:"Calibri",sans-serif; color:black">Winterfeldt IP Group</span></p>
<p class="x_MsoNormal"><span style="font-size:10.0pt; font-family:"Calibri",sans-serif; color:black">1601 K Street NW, Ste 1050</span></p>
<p class="x_MsoNormal"><span style="font-size:10.0pt; font-family:"Calibri",sans-serif; color:black"><a href=""><span style="color:black; text-decoration:none">Washington, DC 20006</span></a></span></p>
<p class="x_MsoNormal"><span style="font-size:10.0pt; font-family:"Calibri",sans-serif; color:black"><a href="mailto:griffin@winterfeldt.law"><span style="color:#0563C1">griffin@winterfeldt.law</span></a></span></p>
<p class="x_MsoNormal"><span style="font-size:10.0pt; font-family:"Calibri",sans-serif; color:black">+1 202 759 5836</span><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:black"></span></p>
</td>
</tr>
</tbody>
</table>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></p>
<p class="x_MsoNormal"><span style="font-size:11.0pt; font-family:"Calibri",sans-serif; color:#1F497D"> </span></p>
<p class="x_MsoNormal"><b><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt; font-family:"Calibri",sans-serif"> GNSO-RPM-WG [mailto:gnso-rpm-wg-bounces@icann.org]
<b>On Behalf Of </b>Paul Tattersfield<br>
<b>Sent:</b> Friday, October 23, 2020 7:14 PM<br>
<b>To:</b> Kathy Kleiman <kathy@kathykleiman.com><br>
<b>Cc:</b> gnso-rpm-wg <gnso-rpm-wg@icann.org><br>
<b>Subject:</b> Re: [GNSO-RPM-WG] Edits and updates</span></p>
<p class="x_MsoNormal"> </p>
<div>
<div>
<p class="x_MsoNormal" style=""><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">Dear All,
<br>
<br>
Recommendation TMCH #1 </span><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">Edits and Updates<br>
</span><span style="font-size:11.0pt; font-family:"Calibri",sans-serif"><br>
I am concerned that the new language and the titles, separates and diminishes well-developed recommendation and guidance from each other.
</span><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">The precisely drafted clauses seem to be more separated from the policy principles than in the
</span><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">final language
</span><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">draft which
</span><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">published to the WG list for review September, 14<sup>th</sup>.</span><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif"> The whole point of drafting precise
language was to make sure unintended consequences were minimised in a way that is very hard to do with policy principles. It’s really a question of
</span><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">emphasis and weight. It feels the new language is
</span><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">introducing more and more potential for problems down the line.
<br>
<br>
Someone has introduced the new concept of “TMCH Validation Provider” and I wasn’t aware of this change being flagged to the working group. (Highlighted in the attached document)<br>
<br>
This seems to me to be a new concept and potentially infers changes to the role of the TMCH provider whose job is primarily to authenticate rather than validate. Validation currently is for Sunrise and the newly introduced language may lead to the impression
that the working group wished a significant role change. Rebecca & I were very careful to ensure we did not take the ‘validation’ role for entry into the clearinghouse away from the trademark offices alone.<br>
<br>
I am not aware of any of the above being highlighted on the call</span><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">. Ideally I think we should return to the recommendation language of September 14<sup>th
</sup>if there is to be no further discussion.<br>
<br>
Context language<br>
<br>
</span><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">I believe the context language was very new and for me password protected until just before the RPM WG call at ICANN 69. So the review time for this language was very short
and outside the normal working group weekly meetings times.<br>
<br>
Again the Context language seems to me to want to put more distance between the precisely drafted clauses and the policy language. The policy recommendation came from the implementation guidance so this doesn’t seem quite right to say – “<i>The Working Group
ultimately agreed on the policy principles reflecting those ideas, which guides the suggested amendment to the Applicant Guidebook (AGB) text in the Implementation Guidance.<br>
<br>
</i>The second paragraph of the new context language needs a lot of work. It </span>
<span style="font-size:11.0pt; font-family:"Calibri",sans-serif">also </span><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">just seems to
</span><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">triplicate (and triplicate incorrectly)
</span><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">what is already there twice.</span><span style="font-size:11.0pt; font-family:"Calibri",sans-serif"> If it is necessary i</span><span lang="EN-GB" style="font-size:11.0pt; font-family:"Calibri",sans-serif">t</span><span style="font-size:11.0pt; font-family:"Calibri",sans-serif">
would be an improvement to say:<br>
<br>
</span><i><span lang="EN-GB" style="font-family:"Calibri",sans-serif; color:blue">(1) mandatory RPMs should only be for word marks, not other types of intellectual property or geographical indications; (2) while other types of marks can be entered into an additional/ancillary
database maintained by the TMCH Provider, they are not eligible for Sunrise and Claims; and (3) the ability for the TMCH Provider and Registry Operators to offer additional/voluntary ancillary services should be preserved (e.g., via ancillary database).</span></i><i><span style="font-family:"Calibri",sans-serif; color:blue"><br>
<br>
</span></i><span style="font-family:"Calibri",sans-serif">Best regards, Paul</span></p>
</div>
</div>
<p class="x_MsoNormal"> </p>
<div>
<div>
<p class="x_MsoNormal">On Fri, Oct 23, 2020 at 11:20 PM Kathy Kleiman <<a href="mailto:kathy@kathykleiman.com">kathy@kathykleiman.com</a>> wrote:</p>
</div>
<blockquote style="border:none; border-left:solid #CCCCCC 1.0pt; padding:0in 0in 0in 6.0pt; margin-left:4.8pt; margin-right:0in">
<div>
<p class="x_MsoNormal"><span style="font-size:9.0pt; font-family:"Helvetica",sans-serif">Hi All, </span></p>
<div>
<p class="x_MsoNormal"><span style="font-size:9.0pt; font-family:"Helvetica",sans-serif">Attached please find my proposed edits to the Background section of our report. We had a little more interaction with the EPDP report than noted -- and went past the summary
wave table to the actual EPDP recommendations to determine that there was no conflict between them and our WG recommendations. I've proposed revisions to the background text to show this process with the steps involved. As a WG, we certainly did our due diligence
on this important task!</span></p>
</div>
<div>
<p class="x_MsoNormal"><span style="font-size:9.0pt; font-family:"Helvetica",sans-serif"> </span></p>
</div>
<div>
<p class="x_MsoNormal"><span style="font-size:9.0pt; font-family:"Helvetica",sans-serif">Best and have a good weekend,</span></p>
</div>
<div>
<p class="x_MsoNormal" style="margin-bottom:12.0pt"><span style="font-size:9.0pt; font-family:"Helvetica",sans-serif">Kathy<br>
<br>
</span></p>
</div>
</div>
<p class="x_MsoNormal">_______________________________________________<br>
GNSO-RPM-WG mailing list<br>
<a href="mailto:GNSO-RPM-WG@icann.org" target="_blank">GNSO-RPM-WG@icann.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Drpm-2Dwg&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=E-M4OQvQBo8UWqE1LwEiDR3PcWlfM0I-0jiI1c4ous0&m=ZHRQkYYyLz4uFHkt_VQWEZULSpI3PkaAjyjWZkOXjOk&s=4x--g5QB9XOkGmmoAj-aRpkFX4mIE7QrdUYCl_p2tWE&e=" target="_blank">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a><br>
_______________________________________________<br>
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=E-M4OQvQBo8UWqE1LwEiDR3PcWlfM0I-0jiI1c4ous0&m=ZHRQkYYyLz4uFHkt_VQWEZULSpI3PkaAjyjWZkOXjOk&s=nQsX7iIoZOxM0HeQzgaaceA_S5ZfEeuEYBVlxcEN0lc&e=" target="_blank">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_tos&d=DwMGaQ&c=WO-RGvefibhHBZq3fL85hQ&r=E-M4OQvQBo8UWqE1LwEiDR3PcWlfM0I-0jiI1c4ous0&m=ZHRQkYYyLz4uFHkt_VQWEZULSpI3PkaAjyjWZkOXjOk&s=eMnG-D3BJ1wHQSUfBLmDFYxW7WOHmeroKKOqlnIc21Q&e=" target="_blank">https://www.icann.org/privacy/tos</a>).
You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</p>
</blockquote>
</div>
</div>
</div>
</body>
</html>