<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:"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;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
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-reply;
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 and notes captured by staff from the<span class=apple-converted-space> </span></span>RPM PDP Working Group<span style='color:black'> call held on</span> 12 September<span style='color:black'> 2018 (1</span>7<span style='color:black'>:00-1</span>9:00<span style='color:black'> UTC). Staff have posted to the wiki space the action items and notes. <i>Please note that these will be high-level notes and are not meant as a substitute for the recording.</i> The recording, AC chat, and attendance records are posted on the wiki<span class=apple-converted-space> </span>at</span>: <a href="https://community.icann.org/display/RARPMRIAGPWG/2018-09-12+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG">https://community.icann.org/display/RARPMRIAGPWG/2018-09-12+Review+of+all+Rights+Protection+Mechanisms+%28RPMs%29+in+all+gTLDs+PDP+WG</a>. <o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>See also the attached referenced document.<o:p></o:p></p><p class=MsoNormal><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'>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<o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'>==</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial",sans-serif'> </span><o:p></o:p></p><p class=MsoNormal><b>ACTION ITEMS: </b><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><b>A. THE COMPLAINT – 6. Amending the Complaint in light of GDPR/Temp Spec<o:p></o:p></b></p><p class=MsoNormal><u>Page 5-6</u>: <b>ACTION ITEM:</b> Change the language to "data required to advance the complaint" or similar (Lori Schulman’s suggestion).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>B. NOTICE – 1. Receipt by Registrant Notice (feedback from Complainant & Respondent)<o:p></o:p></b></p><p class=MsoNormal><u>Page 10</u>:<b> ACTION ITEM:</b> Change to "via the online form [if available]..."<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>J. LANGUAGE ISSUES -- 1. Language issues, including current requirements for complaint, notice of complaint, response, determination<o:p></o:p></b></p><p class=MsoNormal><u>Page 34</u>: <b>ACTION ITEM:</b> 1st Bullet Point: Documents Sub Team should reconsider the recommendation in light of Maxim's earlier feedback.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal><b>NOTES:</b><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>1. Review Agenda/Statements of Interest Updates:<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>-- Kathy Kleiman joined as a visiting scholar at Princeton.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>2. Discussion of URS Draft Policy Recommendations (see attached Super Consolidated URS Topics Table):<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>A. THE COMPLAINT – 6. Amending the Complaint in light of GDPR/Temp Spec<o:p></o:p></b></p><p class=MsoNormal><u>Page 5-6</u>:<o:p></o:p></p><p class=MsoNormal>-- Technical recommendation for GDPR and also outreach re Doe Complaints<o:p></o:p></p><p class=MsoNormal>-- But the Provider may not be receiving the "full registration data" from the Registrars and thus may not be "disclosing" the "full registration data" to the Complainant. Full WHOIS registration data includes *phone number* which is not a piece of data needed by Providers or Complainants. This something we should address, maybe with just a little modification.<o:p></o:p></p><p class=MsoNormal>-- This also should be a phase 2 topic to be considered in Phase 2 on UDRP as it covers both systems. Suggest deferring to Phase 2.<o:p></o:p></p><p class=MsoNormal>-- Disagree: Have an issue with URS. The Temp Spec doesn't address this. We can have the same suggestions in both phases. Each phase addresses different mechanisms and each mechanism can have similar recommendation. Also support the argument about timeliness of issue.<o:p></o:p></p><p class=MsoNormal>-- Agree that can have the same suggestions in both phases. Also, if we don’t put such (obvious) options out to public comment, I think it’s pretty sure that some of said public will comment on them, albeit questioning why the WG hasn’t considered them.<o:p></o:p></p><p class=MsoNormal><b>ACTION ITEM:</b> change to "relevant registration data" or "data required to advance the complaint" since providers may not be getting "full registration data".<o:p></o:p></p><p class=MsoNormal>-- Because of the urgency there is not harm, and since we are on URS, to have a recommendation that relates to URS -- and shouldn't wait until a Phase 2 Initial Report. Could be superseded by the Temp Spec though.<o:p></o:p></p><p class=MsoNormal><b><i>The WG Agrees to move the recommendations into the Initial Report with background, as well as the suggestion to defer to Phase 2.<o:p></o:p></i></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>B. NOTICE – 1. Receipt by Registrant Notice (feedback from Complainant & Respondent)<o:p></o:p></b></p><p class=MsoNormal><u>Page 10</u>:<o:p></o:p></p><p class=MsoNormal>-- Another technical recommendation tied to implementation and enforcement of GDPR. Suggest putting it out for public comment.<o:p></o:p></p><p class=MsoNormal>-- EDPDP Team may also have recommendations relating to this issue.<o:p></o:p></p><p class=MsoNormal>-- Not urgent and could wait until Phase 2 and not all registries have implemented the online form.<o:p></o:p></p><p class=MsoNormal><b>ACTION ITEM:</b> Change to "via the online form [if available]..."<o:p></o:p></p><p class=MsoNormal><b><i>The WG agrees to move the recommendations into the Initial Report with background, as well as the suggestion to defer to Phase 2.<o:p></o:p></i></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>E. DEFENSES -- 1. Scope of Defenses and 2. Unreasonable delay in filing a complaint (i.e. laches)<o:p></o:p></b></p><p class=MsoNormal><u>Page 19</u>:<o:p></o:p></p><p class=MsoNormal>-- Suggest moving this to Phase 2 as it also relates to UDRP.<o:p></o:p></p><p class=MsoNormal>-- Support getting public comment on these two recs on page 19.<o:p></o:p></p><p class=MsoNormal>-- Put out these draft policy recommendations as they exists and ask for comment.<o:p></o:p></p><p class=MsoNormal>-- Could also include for public comment the suggestion to address these in Phase 2.<o:p></o:p></p><p class=MsoNormal>-- Uniform guidance could be developed by ICANN.<o:p></o:p></p><p class=MsoNormal><b><i>The WG agrees to move the recommendations into the Initial Report with background, as well as the suggestion to defer to Phase 2.<o:p></o:p></i></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>F. REMEDIES – 1. Scope of remedies.<o:p></o:p></b></p><p class=MsoNormal><u>Page 23</u>: <b><i>The WG agrees to use this as a placeholder/umbrella for other recommendations that are related.</i></b><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>2. Duration of Suspension Period and 3. Review of Implementation<o:p></o:p></b></p><p class=MsoNormal><u>Pages 26-27</u>:<o:p></o:p></p><p class=MsoNormal>-- Registrars issues with renewals -- Need to have accounts in the bank with the same currency with the payer. Maybe not be able to accept certain payments. Should be some other way of registering the same name through some other registrar. Need this feedback in public comment. <o:p></o:p></p><p class=MsoNormal>-- If there are recommendations about obligations for registrars this could affect contracts, so must be considered whether it is in scope.<o:p></o:p></p><p class=MsoNormal><b><i>The WG agrees to include in the Initial Report with a question about the option to use another registrar.<o:p></o:p></i></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>G. APPEAL – 1. Appeals process<o:p></o:p></b></p><p class=MsoNormal><u>Page 30</u>: <b><i>The WG agrees to include in the Initial Report.</i></b><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>2. De novo review<o:p></o:p></b></p><p class=MsoNormal><u>Pages 30-31</u>: <b><i>The WG agrees to include as an umbrella topic, but will need to address the details, or call out this as a separate category in the Initial Report (perhaps not a recommendation, but a question); wait until the WG goes through the individual proposals.</i></b><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>H. POTENTIALLY OVERLAPPING PROCESS STEPS -- 1. Potential overlap concerning duration of respondent appeal, review and extended reply periods along the URS process timeline<o:p></o:p></b></p><p class=MsoNormal><u>Page 31-32</u>: <b><i>The WG agrees to include as an umbrella topic, but will need to address the details, or call out this as a separate category in the Initial Report (perhaps not a recommendation, but a question); wait until we go through the individual proposals.</i></b><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>J. LANGUAGE ISSUES -- 1. Language issues, including current requirements for complaint, notice of complaint, response, determination<o:p></o:p></b></p><p class=MsoNormal><u>Page 34</u>:<o:p></o:p></p><p class=MsoNormal><b>ACTION ITEM:</b> 1st Bullet Point: Documents Sub Team should reconsider the recommendation in light of Maxim's earlier feedback.<o:p></o:p></p><p class=MsoNormal>2nd Bullet Point: <b><i>The WG agrees to include in the Initial Report.</i></b><o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>L. EDUCATION & TRAINING -- 1. Responsibility for education and training of complainants, registrants, registry operators and registrars<o:p></o:p></b></p><p class=MsoNormal><u>Pages 38-39</u>: <b><i>The WG agrees to include the recommendations in the Initial Report. Include a question about who should compile the FAQ and where it should be hosted/published.</i></b><o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p></div></body></html>