<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Brian,</p>
<p>Respectfully, when Phil surveyed our community for support, both
proposals - the Shatan <b>and </b>the Muskovitch/Kleiman
Proposal -- had considerable support. One had deeper support
(within one SG). One had broader support, across a range of SGs
and members, including commercial, noncommercial, registries and
academics. Both certainly met the standard of support that we have
used in other settings -- and we have moved proposals with far
less support out for public comment.</p>
<p>That said, if there is an interim way that we can navigate on
this call, great! If there is a way to stop the Deloitte from
extracting ordinary words and letters from composite marks and
entering them into the TMCH, that seems to a joint and shared
goal. <br>
</p>
<p>Quick recollection: we know from questionnaires of the WG that
TMCH/Deloitte's policy is to pull ordinary words from composite
marks (figurative, stylized, design, word+design marks -- various
terms used by our various members). We also know from the Analysis
Group that the TMCH database includes some of the most common
dictionary terms and generic terms such as love, hotel and one. <br>
</p>
<p>However, I hear what you are saying -- and wonder with you how
can we protect current brand owners and future brand owners
(noting that future brand owners are likely to use many ordinary
and dictionary words in their names)? Resolution of this design
mark issue -- and its questions -- is key. <br>
</p>
<p>Best, Kathy<br>
</p>
<div class="moz-cite-prefix">On 9/18/2019 9:44 AM, BECKHAM, Brian
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:a803110c3bda4f3388da06aac5cbd5dc@WICM02.WIECSP.UNICC.ORG">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@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:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
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.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.null, li.null, div.null
{mso-style-name:null;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle23
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle24
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle25
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.null1
{mso-style-name:null1;}
span.EmailStyle29
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle30
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle31
{mso-style-type:personal;
font-family:"Arial",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
span.EmailStyle32
{mso-style-type:personal;
font-family:"Arial",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
span.EmailStyle33
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle34
{mso-style-type:personal;
font-family:"Arial",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
span.EmailStyle35
{mso-style-type:personal-compose;
font-family:"Arial",sans-serif;
color:windowtext;
font-weight:normal;
font-style:normal;}
.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;}
/* List Definitions */
@list l0
{mso-list-id:177038611;
mso-list-template-ids:-1574646032;}
@list l0:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1
{mso-list-id:1876892356;
mso-list-template-ids:550510106;}
@list l1:level1
{mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
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]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">Thanks
Jason,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">In
advance of today’s call, an observation: on the one hand it
seems we are at a bit of a crossroads (both the “original
Kleiman/Muscovitch” proposal, and the “Muscovitch
revised-compromise proposal” were rejected by a substantial
number of WG members), and on the other hand, I wonder if
there may be yet some room for agreement. In that respect,
I would note the following as possible areas of convergence:
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">1)
the “core” of the (revised) Kleiman/Muscovitch and Shatan
proposals
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><u><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">From
the
<a
href="https://community.icann.org/display/RARPMRIAGPWG/2019-09-11+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG?preview=/117604906/117605391/Kleiman%20Muscovitch%20Proposal%20Compare%20Doc.pdf"
moz-do-not-send="true">
(revised) Kleiman/Muscovitch proposal</a></span></u></b><b><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">:</span></b><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"> “If
the applicant has a trademark registration in a national
system that does not differentiate between word marks and
other marks (e.g., stylized, design plus, and figurative
marks), they could submit evidence, such as information from
a national registry about its classifications, to show that
the trademark registration confers rights over the words
claimed as such, not limited to words + other elements”<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><u><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">From
the
<a
href="https://community.icann.org/display/RARPMRIAGPWG/2019-09-11+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG?preview=/117604906/117605390/Open%20TMCH%20Charter%20Questions%20-%2027%20Aug%202019.pdf"
moz-do-not-send="true">
Shatan proposal</a></span></u></b><b><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">:
</span></b><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">“The
Trademark Clearinghouse should not accept for inclusion
marks where all textual elements are disclaimed and as such
are only protectable as part of the entire composite mark
including its non-textual elements”<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">Especially
for purposes of today’s call, I wonder if you and WG members
might give some consideration to whether the Shatan proposal
shares the same foundational principle as the (revised)
Kleiman/Muscovitch proposal.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">If
so, perhaps so as to have an agreed principle for purposes
of our Initial Report, proponents of the (revised)
Kleiman/Muscovitch proposal could agree to the Shatan
proposal (even if they feel it should go further in certain
respects)?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">2)
clarity on text/non-standard character marks<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">Separately,
it seems clear that some degree of definition on
text/non-standard character marks (we have also seen the
terms:
</span><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">composite,
figurative, stylized, design, word+design, etc., used</span><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">)
would be useful – at least I do not recall anyone objecting
to this suggestion. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">I
look forward to your presentation today, and wonder if we
might still find some agreement!<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">Brian
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span
style="font-size:11.0pt"> Jason Schaeffer
<a class="moz-txt-link-rfc2396E" href="mailto:jason@esqwire.com"><jason@esqwire.com></a>
<br>
<b>Sent:</b> Wednesday, September 18, 2019 4:39 AM<br>
<b>To:</b> BECKHAM, Brian
<a class="moz-txt-link-rfc2396E" href="mailto:brian.beckham@wipo.int"><brian.beckham@wipo.int></a>; Zak Muscovitch
<a class="moz-txt-link-rfc2396E" href="mailto:zak@muscovitch.com"><zak@muscovitch.com></a>; Julie Hedlund
<a class="moz-txt-link-rfc2396E" href="mailto:julie.hedlund@icann.org"><julie.hedlund@icann.org></a>; <a class="moz-txt-link-abbreviated" href="mailto:gnso-rpm-wg@icann.org">gnso-rpm-wg@icann.org</a><br>
<b>Subject:</b> RE: [GNSO-RPM-WG] Proposed Agenda for
RPM Meeting on 18 September 17:00-18:30 UTC<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D">Hi Brian,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D">Please note that in
Zak’s absence (as he is travelling and may not be joining
the call) I have been asked to present on his behalf.
Although I personally believed that we were making progress
on some of these points on last week’s WG call, nonetheless
given the apparent lack of compromise with the IPC, you are
correct that the compromise proposal has been withdrawn and
the attached Kleiman/Muscovitch proposal remains for
consideration and comment.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D">Kindly refer to the
“original” September 4<sup>th</sup> proposal (attached) to
address the topic of the TMCH and word marks v. design
marks.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D">Jason <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma",sans-serif">
GNSO-RPM-WG [<a
href="mailto:gnso-rpm-wg-bounces@icann.org"
moz-do-not-send="true">mailto:gnso-rpm-wg-bounces@icann.org</a>]
<b>On Behalf Of </b>BECKHAM, Brian<br>
<b>Sent:</b> Tuesday, September 17, 2019 9:28 AM<br>
<b>To:</b> Zak Muscovitch; Julie Hedlund; <a
href="mailto:gnso-rpm-wg@icann.org"
moz-do-not-send="true">
gnso-rpm-wg@icann.org</a><br>
<b>Subject:</b> Re: [GNSO-RPM-WG] Proposed Agenda for
RPM Meeting on 18 September 17:00-18:30 UTC<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">Thanks
very much Zak for this heads up that you are withdrawing
your “compromise proposal” given the lack of additional
interest in it.
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">In
the interests of time, and personally (while I am certain
Phil and Kathy would agree), I want to say that it was
encouraging to hear that you and others attempted offline to
bring this together with other proposals (e.g., Greg’s).<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">Your
below withdrawal of course raises the question of where this
leaves us on the earlier “Kleiman / Muscovitch” proposal, in
particular given that the now-withdrawn proposal was already
an attempt to garner support for a compromise on the earlier
“Kleiman / Muscovitch” proposal.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">By
way of background, as was discussed during a call with Staff
and our WG liaisons (incoming and outgoing), we feel we need
to recognize when there may be diverging views and that wide
agreement on a compromise proposal may not be possible (in
which case alternate views can be recorded, and public
comments sought).
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">In
that light, have you (and Kathy) considered the possibility
– even if per your below message you still support it – of
also withdrawing the “Kleiman / Muscovitch” proposal in
advance of the call, or do you nevertheless consider brief
further discussion on that would in the circumstances still
be necessary and/or useful (if only as a last attempt at
compromise/to cover this off)?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">Brian
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt">From:</span></b><span
style="font-size:11.0pt"> GNSO-RPM-WG <<a
href="mailto:gnso-rpm-wg-bounces@icann.org"
moz-do-not-send="true">gnso-rpm-wg-bounces@icann.org</a>>
<b>On Behalf Of </b>Zak Muscovitch<br>
<b>Sent:</b> Tuesday, September 17, 2019 5:23 AM<br>
<b>To:</b> Julie Hedlund <<a
href="mailto:julie.hedlund@icann.org"
moz-do-not-send="true">julie.hedlund@icann.org</a>>;
<a href="mailto:gnso-rpm-wg@icann.org"
moz-do-not-send="true">gnso-rpm-wg@icann.org</a><br>
<b>Subject:</b> Re: [GNSO-RPM-WG] Proposed Agenda for
RPM Meeting on 18 September 17:00-18:30 UTC<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt" lang="EN-CA">Dear
WG members, staff and co-chairs,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt" lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt" lang="EN-CA">Since
I may not be able to attend the upcoming call this
Wednesday, I want to let you know that since last week’s
call, I have not become aware of any additional interest in
the ‘compromise’ proposal which I had circulated and which
we had discussed on last week’s call (i.e. the one that
allowed ‘design marks’ into TMCH but didn’t afford Sunrise
priority). Accordingly, I am withdrawing it and continue to
support the first proposal, namely the ‘Kleiman / Muscovitch
proposal as revised (see; </span><span lang="EN-CA"><a
href="https://community.icann.org/display/RARPMRIAGPWG/2019-09-11+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG?preview=/117604906/117605391/Kleiman%20Muscovitch%20Proposal%20Compare%20Doc.pdf"
moz-do-not-send="true">https://community.icann.org/display/RARPMRIAGPWG/2019-09-11+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG?preview=/117604906/117605391/Kleiman%20Muscovitch%20Proposal%20Compare%20Doc.pdf</a>).<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt" lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt" lang="EN-CA">Yours
truly,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt" lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt" lang="EN-CA">Zak
Muscovitch<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt" lang="EN-CA">ICA
General Counsel<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt" lang="EN-CA"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt" lang="EN-CA"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black" lang="EN-CA">From:
</span></b><span style="color:black" lang="EN-CA">GNSO-RPM-WG
<<a href="mailto:gnso-rpm-wg-bounces@icann.org"
moz-do-not-send="true">gnso-rpm-wg-bounces@icann.org</a>>
on behalf of Julie Hedlund <<a
href="mailto:julie.hedlund@icann.org"
moz-do-not-send="true">julie.hedlund@icann.org</a>><br>
<b>Date: </b>Saturday, September 14, 2019 at 1:04 AM<br>
<b>To: </b>"<a href="mailto:gnso-rpm-wg@icann.org"
moz-do-not-send="true">gnso-rpm-wg@icann.org</a>" <<a
href="mailto:gnso-rpm-wg@icann.org"
moz-do-not-send="true">gnso-rpm-wg@icann.org</a>><br>
<b>Subject: </b>[GNSO-RPM-WG] Proposed Agenda for RPM
Meeting on 18 September 17:00-18:30 UTC<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"
lang="EN-CA"><o:p> </o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"
lang="EN-CA">Dear RPM WG members, </span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"
lang="EN-CA"> </span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"
lang="EN-CA">Please find the proposed agenda and materials
for the WG meeting on Wednesday, 1</span><span
style="font-size:11.0pt" lang="EN-CA">8<span
style="color:black"> September at 17:00-18:30 UTC.</span></span><span
lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"
lang="EN-CA"> </span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"
lang="EN-CA">For ease of reference, here are the actions
from the meeting on
</span><span style="font-size:11.0pt" lang="EN-CA">11<span
style="color:black"> September:</span></span><span
lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;color:black" lang="EN-CA"> </span></b><span
lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:11.0pt;color:black" lang="EN-CA">Actions:</span></b><span
style="font-size:11.0pt;color:black" lang="EN-CA"> WG
members should continue consideration and discussion of Open
Charter Questions 7 and 8 (see attached documents and
discussions on the list) and review the discussion from the
calls on 04 and 11 September via the Zoom chat, recording,
and transcript (see the posting on the wiki at:
<a
href="https://community.icann.org/display/RARPMRIAGPWG/2019-09-11+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG"
title="https://community.icann.org/display/RARPMRIAGPWG/2019-09-11+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG"
moz-do-not-send="true">
https://community.icann.org/display/RARPMRIAGPWG/2019-09-11+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG</a>.</span><span
lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"
lang="EN-CA"> </span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"
lang="EN-CA">Proposed Agenda:</span><span lang="EN-CA"><o:p></o:p></span></p>
<ol style="margin-top:0in" start="1" type="1">
<li class="MsoNormal" style="color:black;mso-list:l0 level1
lfo3"><span style="font-size:11.0pt" lang="EN-CA">Review
Agenda and Updates to Statements of Interest</span><span
lang="EN-CA"><o:p></o:p></span></li>
<li class="MsoNormal" style="color:black;mso-list:l0 level1
lfo3"><span style="font-size:11.0pt" lang="EN-CA">Determine
Support for</span><span
style="font-size:11.0pt;color:windowtext" lang="EN-CA">
and finalize discussion on</span><span
style="font-size:11.0pt" lang="EN-CA"> proposals relating
to Open TMCH Charter Questions (see attached Summary
document. It is the same as the May 2017 version but with
formatting for readability and text from relevant TMCH and
AGB references):</span><span lang="EN-CA">
<o:p></o:p></span>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l0
level2 lfo3"><b><span style="font-size:11.0pt"
lang="EN-CA">Question 7 – Finalize Discussion on</span></b><span
style="font-size:11.0pt" lang="EN-CA"> </span><b><span
style="font-size:11.0pt;color:windowtext"
lang="EN-CA">Original and </span></b><b><span
style="font-size:11.0pt" lang="EN-CA">Revised
Proposals from Kathy Kleiman/Zak Muscovitch and Greg
Shatan</span></b><span lang="EN-CA"><o:p></o:p></span></li>
<li class="MsoNormal" style="color:black;mso-list:l0
level2 lfo3"><b><span style="font-size:11.0pt"
lang="EN-CA">Question 8 –</span></b><span
style="font-size:11.0pt" lang="EN-CA"> <b>Finalize
Discussion on</b> <b>Proposals from Paul McGrady,
Kathy Kleiman, Jonathan Agmon, and Claudio di Gangi</b></span><span
lang="EN-CA"><o:p></o:p></span></li>
</ul>
</li>
<li class="MsoNormal" style="color:black;mso-list:l0 level1
lfo3"><span style="font-size:11.0pt" lang="EN-CA">AOB</span><span
lang="EN-CA"><o:p></o:p></span></li>
</ol>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"
lang="EN-CA"> </span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"
lang="EN-CA">Best Regards,</span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"
lang="EN-CA">Mary, Julie, Ariel</span><span lang="EN-CA"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-CA"> <o:p></o:p></span></p>
<p> <o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif">World
Intellectual Property Organization Disclaimer: This
electronic message may contain privileged, confidential and
copyright protected information. If you have received this
e-mail by mistake, please immediately notify the sender and
delete this e-mail and all its attachments. Please ensure
all e-mail attachments are scanned for viruses prior to
opening or using.
<o:p></o:p></span></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
GNSO-RPM-WG mailing list
<a class="moz-txt-link-abbreviated" href="mailto:GNSO-RPM-WG@icann.org">GNSO-RPM-WG@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-rpm-wg">https://mm.icann.org/mailman/listinfo/gnso-rpm-wg</a>
_______________________________________________
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 class="moz-txt-link-freetext" href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/tos">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.</pre>
</blockquote>
</body>
</html>