<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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@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: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;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;}
span.apple-tab-span
{mso-style-name:apple-tab-span;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@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:215437190;
mso-list-template-ids:-153740490;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:519049165;
mso-list-template-ids:-733459526;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2
{mso-list-id:879972403;
mso-list-template-ids:-302764058;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l2:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l2:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3
{mso-list-id:1115561222;
mso-list-template-ids:779783222;}
@list l3:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l3:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l3:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l4
{mso-list-id:1199507011;
mso-list-template-ids:-176112020;}
@list l5
{mso-list-id:1695763419;
mso-list-template-ids:-1952140834;}
@list l5:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l5:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l5:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l5:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l6
{mso-list-id:2047830673;
mso-list-template-ids:822791730;}
@list l6:level1
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l6:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l6:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l6:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l6:level5
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l6:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l6:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l6:level8
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l6:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;color:black'>Dear All,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>Below, please find notes and action items from today’s call, EPDP Team Meeting #35. The next EPDP Team meeting will be Thursday, 20 December at 1400 UTC.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>Thank you. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>Best regards,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>Marika, Berry, and Caitlin<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>__<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'>EPDP Team Call #35</span></b><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'>Tuesday, 18 December 2018 14:00 UTC</span></b><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'>High-Level Notes/Actions</span></b><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><ol style='margin-top:0in' start=1 type=1><li class=MsoNormal style='color:black;mso-list:l4 level1 lfo1;vertical-align:baseline'><span style='font-size:11.0pt'>EPDP Support Staff to circulate draft recommendation regarding registrar disclosure of privacy/proxy data to requestor, as developed by the team discussion during the meeting. This draft recommendation will replace the language in Section 2.6 of Appendix A. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l4 level1 lfo1;vertical-align:baseline'><span style='font-size:11.0pt'>EPDP Leadership to summarize the EPDP Team’s discussion of registrant consent to publication of private data and send to the mailing list for further discussion.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l4 level1 lfo1;vertical-align:baseline'><span style='font-size:11.0pt'>The EPDP Legal Committee will hold its first meeting tomorrow, Wednesday, 19 December at 1400 and will discuss and refine potential questions to submit for further legal guidance. <o:p></o:p></span></li></ol><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'>Question to ICANN</span></b><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>What is the rationale for the bolded wording in this Temporary Specification section: <b><i>As soon as commercially reasonable</i></b><i>, Registrar <b>MUST</b> provide the opportunity for the Registered Name Holder to provide its Consent to publish the additional contact information outlined in Section 2.3 of Appendix A for the Registered Name Holder.</i></span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>What was the community input into this Temporary Specification section that, in each of the two cases, led to the wording, “as soon as commercially reasonable,” and “MUST“?</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'>Notes</span></b><b><span style='font-size:11.0pt'><o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><i><span style='font-size:11.0pt;color:black'>These high-level notes are designed to help the EPDP Team navigate through the content of the call and are not meant as a substitute for the transcript and/or recording. The MP3, transcript, and chat are provided separately and are posted on the wiki at: https://community.icann.org/x/ZwPVBQ</span></i><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'>1. Roll Call & SOI Updates</span></b><span style='font-size:11.0pt'><o:p></o:p></span></p><ul style='margin-top:0in' type=disc><li class=MsoNormal style='color:black;mso-list:l5 level1 lfo2;vertical-align:baseline'><span style='font-size:11.0pt'>Attendance will be taken from Adobe Connect<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l5 level1 lfo2;vertical-align:baseline'><span style='font-size:11.0pt'>Remember to mute your microphones when not speaking and state your name before speaking for transcription purposes.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l5 level1 lfo2;vertical-align:baseline'><span style='font-size:11.0pt'>Please remember to review your SOIs on a regular basis and update as needed. Updates are required to be shared with the EPDP Team. <o:p></o:p></span></li></ul><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'>2. Welcome and Updates from EPDP Team Chair (5 minutes)</span></b><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'> a. Review of outstanding action items</span></b><span style='font-size:11.0pt'><o:p></o:p></span></p><ul style='margin-top:0in' type=disc><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>Support Staff will be circulating language regarding geographic differentiation and policy impact analysis this week for the EPDP Team's review. <o:p></o:p></span></li></ul><p class=MsoNormal><span style='font-size:11.0pt;color:black'> <b>b. Other updates, if applicable</b></span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> <b>c. Announce LC Members and introduce agenda for first meeting (EDPB questions)</b></span><span style='font-size:11.0pt'><o:p></o:p></span></p><ul style='margin-top:0in' type=disc><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>First meeting will be held tomorrow (18 Dec, 1400 UTC) during the normal EPDP call time<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>Members of the LC include: <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>Board - Leon <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>BC - Margie <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>IPC - Diane <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>ISPCP - Thomas <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>RySG - Kristina <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>RrSG - Emily <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>GAC - Laureen <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>ALAC - Hadia <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>EPDP Leadership - Kurt, Rafik<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>The first meeting's agenda will be to review the SOW and EDPB questions to refine for ultimate review by legal counsel.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>Who decided the criteria for the legal committee? <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>In following the CCWG Work Stream 2 model, the idea was only to have attorneys on the Legal Committee; however, since not all groups have attorneys, the rule is not absolute.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>EPDP Members should refrain from using colored language in their emails to the team. <o:p></o:p></span></li></ul><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'> d. Review of commonly-asked Google Form questions </span></b><span style='font-size:11.0pt'><o:p></o:p></span></p><ul style='margin-top:0in' type=disc><li class=MsoNormal style='color:black;mso-list:l3 level1 lfo5;vertical-align:baseline'><span style='font-size:11.0pt'>Document will be sent to the Team with the notes for today.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l3 level1 lfo5;vertical-align:baseline'><span style='font-size:11.0pt'>Please email additional questions regarding the Google Form to: gnso-epdp-lead@icann.org.<o:p></o:p></span></li></ul><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'>3. Continue review of list of topics for further discussion </span></b><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>Privacy/Proxy Services - how the P/P records appear in the public WHOIS</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><ul style='margin-top:0in' type=disc><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>If there is a privacy/proxy service, the Registrar must return the full WHOIS data. BC wanted to confirm Section 2.6 of Appendix A. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>It may make sense to add language similar to Section 2.6 of Appendix A as a policy recommendation. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>This is a good idea because if a requester jumps through hoops to ultimately receive P/P data, it will be wasted time for both the requestor and the registrar.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>PPSAI work is currently on pause. This makes sense if the service is offered by the registrar or a service offered by an affiliate of the registrar. In the event the service is independent of the registrar, the registrar could not return the underlying data. The language may need to be tightened up for situations in which a registrar is unaware that a P/P service is being used.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>The registrar can only deliver underlying information if it is aware there is underlying information.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>P/P services would be legal persons and not natural persons.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>The Team could work on the current wording, but it makes sense to solve for the majority case and not the edge case.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>The RAA includes rules for registrar’s P/P services and it applies to registrar affiliates as well. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>Not advocating for removal of this requirement, but more specific language is needed to capture non-affiliated cases.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>For reference, the RAA rules relating to privacy/proxy apply to services "offered or made available by Registrar or its Affiliates in connection with each registration" (3.4.1.5)<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>Possible draft language: The EPDP recommends that in the case of a domain name registration where a Privacy/Proxy service, offered or made available by Registrar or its Affiliates in connection with a registration is used, (e.g. where data associated with a natural person is masked), Registrar MUST return in response to any query full WHOIS data, including the existing proxy/proxy pseudonymized email.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>Action support staff to capture the above language and email to the EPDP Team.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>Email from ICANN org to IPC - delay of PPSAI IRT - ICANN org believes the EPDP will address some of the issues.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>If the PPSAI work requires something from this team, OK, but this team's job should not be doing the PPSAI IRT's work. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>PPSAI situations there may be privacy customers Privacy Customer 125 could still be personal data since it is capable of identifying a person. Anonymized emails can still be personal data. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>To the extent that the EPDP team (within its charter scope) has specific guidance on the issues as they relate to PP services, that may be helpful to the PPSAI IRT when they finalize their proposed model and draft agreements. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>If the PPSAI IRT needs something specific from the EPDP Team, the burden is on them to come forward with what they need.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>The Team should not make assumptions - we may not be automatically providing the needed guidance the PPSAI IRT needs to complete its work.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>If the Team can provide guidance, or if the PPSAI IRT can provided questions to us, there should be a communication path b/w the two groups.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo6;vertical-align:baseline'><span style='font-size:11.0pt'>We need to discuss and agree what will be on the agenda. Only a minority of members wanted to discuss P/P. <o:p></o:p></span></li></ul><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>Registrant Consent to Publication – option for registrants to request to have all of their RDS data published</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><ul style='margin-top:0in' type=disc><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>It is important to allow registrants to make this decision. Registrars may not offer this if not required to, so it would be better to make this a requirement and honor the registrant's choice.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>The EPDP Team's job is to say - does the Temp Spec allow ICANN and contracted parties compliant with the GDPR? Creating a consensus policy requiring this is creating an implementation impossibility that cannot be implemented prior to 25 May. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>As an alternative, if there is a process by which a registered name holder could actively request their information be published could be OK. The default would be redaction. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>We should be able to do this, but we may not be able to do this by May 2019. Asking the GNSO to start a new PDP is pushing this too far down the road as to make it not viable at all.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>There may be mechanisms allowing for consent, but this should be MAY for both registrars and registrants.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>This should not be mandatory, could be voluntary, but getting consent to publish data on the basis of consent is not easy. While companies may already do this, they may not be doing it well or in a GDPR-compliant way. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>IPC believes this should be a must - registrars must make the option available to registrants.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>How will registries know if there is consent to publish the data, so it makes more sense to make this a "must" rather than a "may".<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>If a registrant knows enough about publication of data, they can make an informed decision as to which registrar to use.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>Regarding Art. 6(1)(b) - notes taking steps prior to entering into a contract - this may be more straightforward rather than meddling with consent in Art. 8.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>If you are doing consent-based processing, you need to evidence the consent and the content of that consent comprehensively.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>For everyone on these calls, shopping around for registrars may be simple, but for the typical registrant - it is not simple. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>You need equivalent of an apple agreement to cover consent, but then you would have to deal with withdrawal of consent. We should park this issue for now. It is not for the group to figure this out as we do not have time.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>Art. 6(1)(b) - if in order to enter into a contract, the controller must process data subject's data prior to entering into the contract, that's what the language in Art. 6(1)(b) is meant to represent. Registrars should not be forced to take risks for the sake of certain people. Certain businesses may not be in a position to assume the risk.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>What if we took out the words when commercially feasible and replace it with "may". <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>We are not talking about a concept involving implementation costs - providing the data that is optional to publish was the law of the land. Registrars should be required to explain to registrants what data they have the option to publish.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>There seems to be an assumption that everyone is working from the same basis of knowledge, which may not be the case with some registrars and registrants. If it not going to be a "must", we could have a "may" in the recommendations. The reference to "gun shy" was not meant to be inflammatory. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>Registrants asking for their information to be published are making this request for their own benefit - they are not doing it for the benefit of third parties. (they may be using it for marketing, advertising) Ultimately, this should be optional since this is an add-on or value-added service. This could also be captured in the Team's report.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>One of the complaint of registrars is that ICANN heaps regulations on the "good guys". While "may" could be OK, in a situation with the "bad guys", this may allow bad registrars to give another layer of obfuscation with their bad customers. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>If consent is not transferred to the registry, are we defeating the purpose?<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>Does this issue become moot when RDAP is deployed?<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>It is not clear why offering the option of publishing details and getting consent - why is that so difficult? It sounds straightforward. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>The risk here is getting it wrong - if there is no legal basis for publishing data, this is a risk. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>How can you withdraw consent and remove the data from the escrow provider, the registries and other relevant parties?<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>The technical implementation issue is a red herring.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>The technical issues are not insurmountable here. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>"soon as commercially reasonable" is important for small registrars. It should still be a "may". <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>Leadership to summarize this conversation via email. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l6 level1 lfo7;vertical-align:baseline'><span style='font-size:11.0pt'>Support Staff to send draft language re: P/P services to the list.<o:p></o:p></span></li></ul><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt'><br><span style='color:black'>Consent by the Registrant to Publish and/or Disclose for technical contact</span><o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>4. Wrap and confirm next meeting to be scheduled for Thursday, 20 December 2018 at 14.00 UTC</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> a. Confirm action items</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> b. Confirm questions for ICANN Org, if any</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt'><br><br><br><br><br><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p></div></body></html>