<html 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:"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;}
/* 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;}
span.EmailStyle38
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle39
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle40
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle41
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle42
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle43
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle44
{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>
</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> 20 November 2019 at 17:00 UTC<span style="color:black">.
Staff </span>will post<span style="color:black"> 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-11-20+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG">
<span style="color:blue">https://community.icann.org/display/RARPMRIAGPWG/2019-11-20+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG</span></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><span style="color:black">Actions:</span></b></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">Pages 9-10: <span style="color:black">OPERATIONAL FIX</span>
<span style="color:black">(Providers ST) – ACTION: </span>Move the second paragraph to the top and also put the questions before the specifics (as they are more general).</p>
<p class="MsoNormal">Page 11: F. REMEDIES <b>- </b>4. Other topics (Providers ST) – ACTION: Provide a description/definition of the HSTS-preloaded domain suspension remedy.<o:p></o:p></p>
<p class="MsoNormal">Page 11: <span style="color:black">G. APPEAL - 1. Appeals process POLICY RECOMMENDATION</span>
<span style="color:black">(Documents ST)</span> -- ACTION: Add text in column 2 noting the consolidation with page 7.</p>
<p style="margin:0in;margin-bottom:.0001pt">Page 12: G. APPEAL<b> - </b>2. De novo review and H. POTENTIALLY OVERLAPPING PROCESS STEPS<b> -
</b>1. Potential overlap concerning duration of respondent appeal, review and extended reply periods along the URS process timeline
<span style="color:black">POLICY RECOMMENDATION</span> <span style="color:black">
(Documents ST; see also Section H)</span> -- ACTION: Revise column 2 to indicate that the WG will review after the URS individual proposals go out for public comment. No recommendation for the WG at this time. Delete the current text in column 2.<o:p></o:p></p>
<p class="MsoNormal">Page 13: I. COST<b> - </b>1. Cost allocation model (Providers ST) -- ACTION: Add that FORUM has never collected these fees.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">J. LANGUAGE ISSUES<b> - </b>1. Language issues, including current requirements for complaint, notice of complaint, response, determination
</p>
<p style="margin:0in;margin-bottom:.0001pt">Page 14: <span style="color:black">OPERATIONAL FIX</span>
<span style="color:black">(Providers ST) -- </span>ACTION: Add the reference concerning consolidation with pages 8-10 to column 2.<o:p></o:p></p>
<p class="MsoNormal">Page 15: POLICY RECOMMENDATION (Documents ST) (middle of page) -- ACTION: Update column 2 to include the explanation that the WG agreed to withdraw this recommendation.<o:p></o:p></p>
<p class="MsoNormal">Page 15: POLICY RECOMMENDATION (Documents ST) (bottom of page) -- ACTION: Change from “guidance to assist examiners” to “guidance to assist URS providers”, but not sure we need the recommendation at all. Also, change to WG recommendation.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">Page 17: L. EDUCATION & TRAINING<b> -
</b>1. Responsibility for education and training of complainants, registrants, registry operators and registrars,
<span style="color:black">POLICY RECOMMENDATION</span> <span style="color:black">
(Documents ST; see also Section H) </span>-- ACTION: Change to “WG recommends” (as the WG has previously discussed).<o:p></o:p></p>
<p class="MsoNormal">Page 18: M. URS PROVIDERS<b> - </b>1. Evaluation of URS providers and their respective processes (including training of panelists) OPERATIONAL FIX (Providers ST) -- ACTION: Include the reference to the consolidation with pages 8-10 in column
2.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><u>Review Revisions from the WG Discussions in Montreal:<o:p></o:p></u></p>
<p class="MsoNormal">A. THE<b> </b>COMPLAINT<b> - </b>6. Amending the Complaint in light of GDPR/Temp Spec<o:p></o:p></p>
<p class="MsoNormal">Page 1: OPERATIONAL FIX<b> </b>(Providers ST) -- ACTION: Add in brackets/all caps that the language has been overcome by events and is better addressed section X/Y/Z below.<o:p></o:p></p>
<p class="MsoNormal">Page 2: OPERATIONAL FIX<b> </b>(Providers ST) -- ACTION: Insert bracketed text that this has been overcome by events and reference EPDP recommendation #23 as well as the recommendations on compliance.<o:p></o:p></p>
<p class="MsoNormal">Page 2: POLICY RECOMMENDATION (Providers ST) (bottom of page 2) -- ACTION: Start with this item on the next call on 04 December.</p>
<p class="MsoNormal"><span style="color:black"> </span></p>
<p class="MsoNormal"><b>Notes:</b></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="color:black">1. Updates to Statements of Interest:
</span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">-- Justine Chew: Now seated as a member of the ALAC. However, unless otherwise stated, my views in this WG are that of my own.<o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"> </span></p>
<p class="MsoNormal">2. Working Group to complete discussions regarding the recommendations of the URS Sub Teams’ to go into the Initial Report, see:
<a href="https://docs.google.com/document/d/1jlsM6yl3A9ssPdHymjZwoSQXsncsl8h_9oOE1vFYm9o/edit?usp=sharing%20%5bdocs.google.com%5d">
https://docs.google.com/document/d/1jlsM6yl3A9ssPdHymjZwoSQXsncsl8h_9oOE1vFYm9o/edit?usp=sharing [docs.google.com]</a> (top of page 9)</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">F. REMEDIES<b> - </b>2. Duration of suspension period; 3. Review of implementation<o:p></o:p></p>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:black">Page 8: POLICY RECOMMENDATION</span>
<span style="color:black">(Providers ST)</span></p>
<p class="MsoNormal">-- Revised language agreed to at ICANN66.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Pages 9-10: <span style="color:black">OPERATIONAL FIX</span>
<span style="color:black">(Providers ST)</span></p>
<p class="MsoNormal">-- Questions are broad.</p>
<p class="MsoNormal">-- Include the context. Staff notes that we’ll include the deliberations in any case. The intention is to include the entire text of column 2 in the Initial Report.</p>
<p class="MsoNormal">-- ACTIONS: Move the second paragraph to the top and also put the questions before the specifics (as they are more general).</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Page 11: F. REMEDIES <b>- </b>4. Other topics (Providers ST)<o:p></o:p></p>
<p class="MsoNormal">-- ACTION: Provide a description/definition of the HSTS-preloaded domain suspension remedy.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Page 11: <span style="color:black">G. APPEAL - 1. Appeals process</span>
<span style="color:black">POLICY RECOMMENDATION</span> <span style="color:black">
(Documents ST)</span></p>
<p class="MsoNormal">-- Consolidated with top of page 7, policy recommendation.</p>
<p class="MsoNormal">-- ACTION: Add text in column 2 noting the consolidation with page 7.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Page 12: G. APPEAL<b> - </b>2. De novo review and H. POTENTIALLY OVERLAPPING PROCESS STEPS<b> -
</b>1. Potential overlap concerning duration of respondent appeal, review and extended reply periods along the URS process timeline</p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black">POLICY RECOMMENDATION</span>
<span style="color:black">(Documents ST; see also Section H)</span></p>
<p class="MsoNormal">-- The WG has not made a determination on Sub Team recommendations 1 and 2 so there is nothing to include in the Initial Report.</p>
<p class="MsoNormal">-- With respect to adjusting the response times, what prompted it was that there was a redundancy in the appeals process. So for economy purposes make this into one appeal. Also, hope that proposal #36 will go out for public comment as
a proposal to address the redundancy.</p>
<p class="MsoNormal">-- ACTION: Revise column 2 to indicate that the WG will review after the URS individual proposals go out for public comment. No recommendation for the WG at this time. Delete the current text in column 2.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Page 13: I. COST<b> - </b>1. Cost allocation model (Providers ST)</p>
<p class="MsoNormal">-- Acts as a deterrent against late responses.</p>
<p class="MsoNormal">-- ACTION: Add that FORUM has never collected these fees.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">J. LANGUAGE ISSUES<b> - </b>1. Language issues, including current requirements for complaint, notice of complaint, response, determination</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p style="margin:0in;margin-bottom:.0001pt">Page 14: <span style="color:black">OPERATIONAL FIX</span>
<span style="color:black">(Providers ST)</span></p>
<p class="MsoNormal">-- Consolidated with recommendation on pages 8-10. </p>
<p class="MsoNormal">-- ACTION: Add the reference concerning consolidation with pages 8-10 to column 2.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Page 15: POLICY RECOMMENDATION (Documents ST) (middle of page):</p>
<p class="MsoNormal">-- ACTION: Update column 2 to include the explanation that the WG agreed to withdraw this recommendation.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Page 15: POLICY RECOMMENDATION (Documents ST) (bottom of page):</p>
<p class="MsoNormal">-- Revised the language to put it in the form of a recommendation and consolidated it with the action item at the top of page 16.</p>
<p class="MsoNormal">-- By the time the examiner gets the case we’ve had to make a determination on the language based on the examiner we select. So it wouldn’t be guidance to the examiner, but to the provider. Per FORUM, this has not been an issue at all.</p>
<p class="MsoNormal">-- ACTION: Change from “guidance to assist examiners” to “guidance to assist URS providers”, but not sure we need the recommendation at all. Also, change to WG recommendation.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Page 16: K. ABUSE OF PROCESS<b> - </b>1. Misuse of the process, including by trademark owners, registrants and “repeat offenders”; 2. Forum shopping; 3. Other documented abuses (Providers ST)</p>
<p class="MsoNormal">-- WG agrees that these are appropriate questions to ask.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Page 17: L. EDUCATION & TRAINING<b> - </b>1. Responsibility for education and training of complainants, registrants, registry operators and registrars</p>
<p style="margin:0in;margin-bottom:.0001pt"><span style="color:black">POLICY RECOMMENDATION</span>
<span style="color:black">(Providers ST)</span></p>
<p class="MsoNormal">-- Consolidated the language and made it read as a recommendation.</p>
<p class="MsoNormal">-- ACTION: Change to “WG recommends” (as the WG has previously discussed).</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Page 18: M. URS PROVIDERS<b> - </b>1. Evaluation of URS providers and their respective processes (including training of panelists)</p>
<p class="MsoNormal">OPERATIONAL FIX (Providers ST)</p>
<p class="MsoNormal">-- Consolidated with the recommendations on pages 8-10.</p>
<p class="MsoNormal">-- ACTION: Include the reference to the consolidation with pages 8-10 in column 2.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><u>Review Revisions from the WG Discussions in Montreal:<o:p></o:p></u></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Page 1, A. THE COMPLAINT<b> - </b>4. Administrative review</p>
<p class="MsoNormal">OPERATIONAL FIX<b> </b>(Providers ST)</p>
<p class="MsoNormal">-- Noted that FORUM already checks this. Include the rationale when including in the Initial Report.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">A. THE<b> </b>COMPLAINT<b> - </b>6. Amending the Complaint in light of GDPR/Temp Spec</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Page 1: OPERATIONAL FIX<b> </b>(Providers ST)</p>
<p class="MsoNormal">-- Staff suggestion based on the WG discussion is to delete the recommendation, based on FORUM’s practice and EPDP recommendation #27.</p>
<p class="MsoNormal">-- Why delete this if it doesn’t raise inconsistencies?</p>
<p class="MsoNormal">-- FORUM is the only provide that auto-populates data. As we discussed in Montreal we are populating with anything that would need to be redacted for privacy purposes.</p>
<p class="MsoNormal">-- We could keep language and simply make reference to the paragraph that deals with it comprehensively.
</p>
<p class="MsoNormal">-- ACTION: Add in brackets/all caps that the language has been overcome by events and is better addressed section X/Y/Z below.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Page 2: OPERATIONAL FIX<b> </b>(Providers ST)</p>
<p class="MsoNormal">-- After review of the WG discussion the staff suggestion is to delete this recommendation.</p>
<p class="MsoNormal">-- Overlaps with EPDP recommendation #23.</p>
<p class="MsoNormal">-- ACTION: Insert bracketed text that this has been overcome by events and reference EPDP recommendation #23 as well as the recommendations on compliance.</p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Page 2: POLICY RECOMMENDATION (Providers ST) (bottom of page 2)</p>
<p class="MsoNormal">-- Change to a WG recommendation.</p>
<p class="MsoNormal">-- Delete the second sentence? </p>
<p class="MsoNormal">-- This specific language was proposed by MFSD.</p>
<p class="MsoNormal">-- ACTION: Start with this item on the next call on 04 December.</p>
</div>
</body>
</html>