<div dir="ltr"><div dir="ltr">
<p style="margin-bottom:12pt" class="gmail-xmsonormal"><span style="font-size:11pt;font-family:Calibri">Hi Phil, <br>
<br>
Please see below the proposed wording to bring Rebecca's and Claudio's proposals #4 & #5 together to reach consensus. We may also need some policy principles on
who has ultimate authority in the extremely unlikely event the TMCH refuses to
accept a mark that is within policy. But overarching questions on ultimate authority are
likely best served elsewhere.<br>
<br>
Best regards, Paul<br>
<br>
<br>
3.2 The standards for inclusion in the Clearinghouse are:<br>
<br>
3.2.1 Nationally or regionally registered word
marks from all jurisdictions.<br>
</span><span style="font-size:11pt;font-family:Calibri" lang="EN-GB">3.2.2 Any word mark that has been
validated through a court of law or other judicial proceeding.<br>
<br>
3.2.3 <s><span style="color:red">Any</span></s>
Word marks protected by a statute or treaty in effect at the time the mark is
submitted to the Clearinghouse for inclusion.<br>
<br>
3.2.4 Other marks <span style="color:teal">and
indications</span> that constitute intellectual property.<br>
<br>
3.2.5 Protections afforded to trademark registrations
do not extend to applications for registrations, marks within any opposition
period or registered marks that were the subject of successful invalidation,
cancellation or rectification proceedings.<br>
<br>
<span style="color:teal">3.2.6 Protections
afforded to word marks protected by statute or treaty do not extend to
geographical indications and other quality schemes unless they also satisfy
3.2.1 or 3.2.2<br>
<br>
3.2.7 Word marks here include service marks, collective
marks, certification marks </span><span style="color:blue">and word marks
protected by statute or treaty.<br>
<br>
3.2.8 Sunrise
and Claims services available through the TMCH are limited only to word marks
under sections 3.2.1, 3.2.2 and 3.2.3 (as further limited by sections 3.2.5 and
3.2.6).<br>
<br>
3.2.9 Nothing in section 3.2 shall exclude the TMCH
provider and registry operators from offering additional voluntary services to
mark holders (e.g. via ancillary databases). Any marks admitted pursuant to
section 3.2.4 which do not also qualify for submission under sections 3.2.1,
3.2.2 or 3.2.3 shall be held only in an ancillary database.</span></span><span style="font-size:11pt;font-family:Calibri"></span></p>
</div></div><br><div class="gmail_quote"><div class="gmail_attr" dir="ltr">On Thu, Jul 30, 2020 at 4:16 PM Corwin, Philip <<a href="mailto:pcorwin@verisign.com">pcorwin@verisign.com</a>> wrote:<br></div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">
<div lang="EN-US">
<div class="gmail-m_-8491594763077726555WordSection1">
<p class="MsoNormal">Can you please share the full text of the proposal from you, Rebecca and Claudio that we will be discussing today?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thanks<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">Philip S. Corwin<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">Policy Counsel<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">VeriSign, Inc.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif" lang="EN">12061 Bluemont Way<br>
Reston, VA 20190<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">703-948-4648/Direct<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif">571-342-7489/Cell<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-family:"Arial",sans-serif"><u></u> <u></u></span></p>
<p class="MsoNormal"><i><span style="font-family:"Arial",sans-serif">"Luck is the residue of design" -- Branch Rickey<u></u><u></u></span></i></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><b>From:</b> GNSO-RPM-WG <<a target="_blank" href="mailto:gnso-rpm-wg-bounces@icann.org">gnso-rpm-wg-bounces@icann.org</a>> <b>
On Behalf Of </b>Paul Tattersfield<br>
<b>Sent:</b> Thursday, July 30, 2020 7:22 AM<br>
<b>To:</b> gnso-rpm-wg <<a target="_blank" href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a>><br>
<b>Subject:</b> [EXTERNAL] Re: [GNSO-RPM-WG] Simplified language to bring together individual TMCH #4 & #5 proposals<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<p class="MsoNormal"><span lang="EN-GB">Hi All, Please see below improved wording for 3.2.7 bringing together GAC advice and Mary’s / Staff observations and new clauses 3.2.8 & 3.2.9 clarifying working group member’s policy intentions. Best regards, Paul<br>
<br>
<br>
<span style="color:teal">3.2.7 Word marks here include service marks, collective marks, certification marks
</span><span style="color:blue">and word marks protected by statute or treaty.<br>
<br>
3.2.8 Sunrise and Claims services available through the TMCH are limited only to word marks under sections 3.2.1, 3.2.2 and 3.2.3 (as further limited by sections 3.2.5 and 3.2.6).<br>
<br>
3.2.9 Nothing in section 3.2 shall exclude the TMCH provider and registry operators from offering additional voluntary services to mark holders (e.g. via ancillary databases). Marks under section 3.2.4 must be held in an ancillary database.<br>
<br>
<br>
<br>
</span><b>Implementation of Consensus Policy for the Protection of Red Cross & Red Crescent Identifiers</b><br>
<a target="_blank" href="https://secure-web.cisco.com/1ndqdFZScX6xY3wAJjo75d47lU0adf8bKhc04Yg5ShCoAe5hC9KkRYeautAJoDZiO335mYsDnPXdw4eFntKvMrbY3d4mkOQsD6VPSLwq187UucURN2kuMNgRU_UXKv9u0IN008vapXiiDdkGJTtpY_V4Gln8vzh55jDcj734cnIuAMAl1pYstjuRXaQ7LNNxzXX2XahSI2utQ2-nP7lwg9SCOZQrc2oWWat6MJpF4mzcZGUHyDMJJLYYWHMQKGlFJXmLruHHjXdQ0tQYUIwZhXQ/https%3A%2F%2Fwww.icann.org%2Fnews%2Fannouncement-2020-02-18-en">https://www.icann.org/news/announcement-2020-02-18-en</a></span><u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote></div>