<html 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">
<head>
<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:"MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
@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:"\@MS Gothic";
panose-1:2 11 6 9 7 2 5 8 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.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.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:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
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.xmsolistparagraph, li.xmsolistparagraph, div.xmsolistparagraph
{mso-style-name:xmsolistparagraph;
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.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
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.EmailStyle26
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle27
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle28
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
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:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle32
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle33
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle34
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle35
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle36
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle37
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
.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;}
--></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" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:black">Dear All,</span><o:p></o:p></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black"> </span><o:p></o:p></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
<span style="color:black">Please see below the action items captured by staff from the<span class="apple-converted-space"> </span></span>RPM PDP Working Group<span style="color:black"> call held on</span> 11 September 2019 at 17:00 UTC<span style="color:black">.
Staff have posted these to the wiki space. <b><i>Please note that these </i></b></span><b><i>are<span style="color:black"> high-level notes and are not meant as a substitute for the recording</span>, chat room, or transcript</i></b><i><span style="color:black">.</span></i><span style="color:black"> The
recording, Zoom chat,</span> transcript<span style="color:black"> and attendance records are posted on the wiki<span class="apple-converted-space"> </span>at</span>:
<a href="https://community.icann.org/display/RARPMRIAGPWG/2019-09-11+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG">
https://community.icann.org/display/RARPMRIAGPWG/2019-09-11+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG</a>.
</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="color:black">Best Regards,</span><o:p></o:p></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
Julie<o:p></o:p></p>
<p class="MsoNormal" style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: auto;text-align:start;widows: auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px">
Julie Hedlund, Policy Director</p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">==</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"> </span></p>
<p class="MsoNormal"><b>NOTES & ACTION ITEMS</b></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><b>Actions:</b> WG members should continue consideration and discussion of Open Charter Questions 7 and 8 (see attached document and proposals 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 link above).</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>Notes:<o:p></o:p></b></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><u>Open Charter Question 8</u>:<o:p></o:p></p>
<p class="MsoNormal">-- Clarify what is meant by TMs protected by statutes or treaties – not meant to include non-TMs.
<o:p></o:p></p>
<p class="MsoNormal">-- 3.2.3: Any word mark [specified as protected]...<o:p></o:p></p>
<p class="MsoNormal">-- 3.2.4: Other marks that constituted intellectual property.<o:p></o:p></p>
<p class="MsoNormal">-- See proposal from Rebecca Tushnet: The Trademark Clearinghouse is for trademarks. The current categories in the AGB of "Marks protected by statute or treaty" and "other IP" (3.2.3 and 3.2.4) should both be replaced by the single concept
of "word marks protected as trademarks by statute or treaty specifying the marks at issue." The three categories of eligible trademarks for the TMCH would then be marks protected by a national registration, marks confirmed by a court decision, and marks recognized
as trademarks by statute or treaty (e.g., the Olympic marks, 36 U.S.C. §380, Use of Olympic symbols, emblems, trademarks and names).<o:p></o:p></p>
<p class="MsoNormal">-- If a Registry Operator wants to protect intellectual property it can do so under 3.2.4, but if not how else?<o:p></o:p></p>
<p class="MsoNormal">-- Amend to “Any word mark set forth in a statute or treaty and protected as a mark, trademark, service mark...by a statute or treaty...” and delete 3.2.4.<o:p></o:p></p>
<p class="MsoNormal">-- QUESTION from staff: it likely makes a difference in scope whether the WG agrees to use “mark” or “trademark” for what is within scope of 3.2.3., i.e. all “trademarks” are likely “marks”, but not all marks are trademarks.<o:p></o:p></p>
<p class="MsoNormal">-- If the statute treats you as a trademark you should be in the TMCH, if not then not.<o:p></o:p></p>
<p class="MsoNormal">-- Could change 3.2.4 to reference “trademark” instead of “marks”.
<o:p></o:p></p>
<p class="MsoNormal">-- On 3.2.4 - it is supposed to cover other intellectual property protected by arrangement with a registry, under that registry’s rules and requirements.<o:p></o:p></p>
<p class="MsoNormal">-- “mark” was used in 3.2.4 was used to avoid confusion. The intention in the practice in AGB and implemented by Deloitte, are marks protected by a Registry for its rules, but only pertain to that Registry. It is not meant to be a broad
category of anything that could be a mark.<o:p></o:p></p>
<p class="MsoNormal">-- It seems to staff that basically the WG is converging on the concept that “word marks protected by statute or treaty” should be limited to those marks that are protected as the functional & substantive equivalent of trademarks.<o:p></o:p></p>
<p class="MsoNormal">-- But staff are concerned about specifying that the actual statute/treaty must either name the mark(s) and/or contain an actual list of the marks, as that may exclude a lot of “marks” that have that function and protection.<o:p></o:p></p>
<p class="MsoNormal">-- Concern that the staff comment above would put statute or treaty marks on parallel with trademarks.<o:p></o:p></p>
<p class="MsoNormal">-- Could say “trademark” “service marks” “certification marks” and “collective marks”.<o:p></o:p></p>
<p class="MsoNormal">-- Listing or specifying marks will likely exclude Paul Tattersfield’s suggestion of Article 6ter, some Red Cross names, etc.<o:p></o:p></p>
<p class="MsoNormal">-- As follow up, the staff comments above really went to our earlier point about “mark” vs “trademark”. The examples we gave could arguably be “marks” but perhaps not “trademarks”.<o:p></o:p></p>
<p class="MsoNormal">-- Registry uses of ancillary databases – such as book titles – what a Registry is allowed to do under its contract. Allow them to protect different forms of source identifiers. Don’t agree on how that should happen. The ancillary database
would be a way to do it, with the limited registration period after the Sunrise period.<o:p></o:p></p>
<p class="MsoNormal">-- Ancillary databases are not in the TMCH, but are services provided by the TMCH.<o:p></o:p></p>
<p class="MsoNormal">-- Everything in the TMCH gets Sunrise and notices, so we should separate out those that shouldn’t – such as 3.2.4.<o:p></o:p></p>
<p class="MsoNormal">-- Look at AGB in 7.0, 7.1, and 7.2 – everyone is maybe talking about best practices. Maybe a good idea that ancillary marks should be in a separate database.<span style="font-family:"MS Gothic""><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><u>Open Charter Question 7</u>:<o:p></o:p></p>
<p class="MsoNormal">We have had some side line conversations regarding the proposal below. I informed Zak separately and wish to convey that this is where the IPC currently stands:<o:p></o:p></p>
<p class="MsoNormal">1. <span lang="EN-CA">As per Greg’s proposal, where a design mark with words disclaims >>all<< words, it <i>does not</i> enter TMCH. – IPC agrees.</span><o:p></o:p></p>
<p class="MsoNormal">2. <span lang="EN-CA">As per Greg’s proposal, where a design mark with words disclaims >>some but not all words<< it <i>does </i>enters the TMCH. – IPC agrees. </span><o:p></o:p></p>
<p class="MsoNormal">3. <span lang="EN-CA">Where a design mark with words is permitted into the TMCH, it entitles the mark holder to a Claims Notice, but not a Sunrise priority. – The IPC disagrees as this would undermine the purpose of registering with
the TMCH to begin with.</span><o:p></o:p></p>
<p class="MsoNormal">4. <span lang="EN-CA">The Claims Notice would have to specify inter alia, that it is notifying prospective registrants of someone claiming to have rights corresponding to the domain name, but that not in all cases does having a design
mark confer rights over the words inside, or something to that effect. – The IPC is willing to discuss this proposal. We agree in principle that language that is not well understood or could frighten an unsophisticated applicant should be revised. However,
the notice should not be providing legal advice or any advice about effects of certain types of trademark registrations.</span><o:p></o:p></p>
<p class="MsoNormal">5. <span lang="EN-CA">Design marks consisting of a single letter, e.g. a stylized or graphical “i”, whether disclaimed or not, do not go into the TMCH. – The IPC does not agree as this outcome is contrary to trademark law.</span><o:p></o:p></p>
<p class="MsoNormal">In general, it appears that Greg’s proposal addresses 3 and 5. To what degree to people object? We see the proposal as creating a solution for a small problem with significant, unintended consequences.<o:p></o:p></p>
<p class="MsoNormal">There are objections procedures for domains registered during Sunrise period and we believe that these procedures should be highlighted as remedy for the concerns that registrant’s have regarding this issue.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Discussion:<o:p></o:p></p>
<p class="MsoNormal">-- Could include Greg’s proposal of eliminating design marks that have disclaimers and include those that have partial disclaimers.<o:p></o:p></p>
<p class="MsoNormal">-- With respect to #3 – it is interesting if there was some clearer names that could give a right to claims but not to Sunrise, but IPC membership is concerned about how you draw that line. Comes back to what is or isn’t a design mark.<o:p></o:p></p>
<p class="MsoNormal">-- In terms of #4 we were thinking that there could be compromise language, but not provide legal advice in a notice.<o:p></o:p></p>
<p class="MsoNormal">-- In terms of #5, many IPC members agreed that these are TM registrations and should be in the TMCH.<o:p></o:p></p>
<p class="MsoNormal">-- Design Mark/Word Mark is a false binary. <o:p></o:p></p>
<p class="MsoNormal">-- Could have a compromise if we can figure out how to split Sunrise and Claims. Sunrise can do some additional examination, we should leverage that.<o:p></o:p></p>
<p class="MsoNormal">-- If it is a clear situation – talking about predominantly the mark is a word, then we are closer to compromise. The concern is not to expand rights beyond what they are given under the law.
<o:p></o:p></p>
<p class="MsoNormal">-- Be aware of the practical impact of a registrant getting a notice and the possible chilling effect.<o:p></o:p></p>
<p class="MsoNormal">-- On Sunrise, getting that pre-emptive right that is expansive if you don’t have that clear right – such as in a heavy design mark, although unclear who would make that determination.
<o:p></o:p></p>
</div>
</body>
</html>