<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;}
.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:88504163;
mso-list-template-ids:-524626654;}
@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:354160975;
mso-list-template-ids:1345748600;}
@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:1181941800;
mso-list-template-ids:1557057114;}
@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:1692880389;
mso-list-template-ids:-732370590;}
@list l4
{mso-list-id:1902013378;
mso-list-template-ids:-1882008610;}
@list l4: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 l4: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 l4: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 l4: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 l4: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 l4: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 l4: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 l4: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 l4: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 style='margin:0in;margin-bottom:.0001pt'><span style='color:black'>Dear All,<o:p></o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'><o:p> </o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'>Below, please find the notes and action items from today’s EPDP Team meeting. As a reminder, our next meeting will be </span><span style='color:black'>Monday, 19 November at 14.00 UTC.<o:p></o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'><o:p> </o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'>Best regards,<o:p></o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'><o:p> </o:p></span></p><div style='mso-element:para-border-div;border:none;border-bottom:solid windowtext 1.5pt;padding:0in 0in 1.0pt 0in'><p style='margin:0in;margin-bottom:.0001pt;border:none;padding:0in'><span style='color:black'>Marika, Berry and Caitlin<o:p></o:p></span></p></div><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'><o:p> </o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><b><span style='color:black'><o:p> </o:p></span></b></p><p style='margin:0in;margin-bottom:.0001pt'><b><span style='color:black'>EPDP Team Meeting #27</span></b><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><b><span style='color:black'>16 November 2018</span></b><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><b><span style='color:black'>High-level Action Items</span></b><o:p></o:p></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 style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l3 level1 lfo1;vertical-align:baseline'>Margie to suggest modifications to the UDRP/URS paragraph re: complainant access to registration data pre-filing to the list by COB today so other team members may opine on it.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l3 level1 lfo1;vertical-align:baseline'>Support staff to note the issue of WHOIS accuracy to be discussed in Phase 2. <o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l3 level1 lfo1;vertical-align:baseline'>Thomas to add language to the responsible parties text to recognize recent ICANN memo on the joint controllership topic.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l3 level1 lfo1;vertical-align:baseline'>Support staff to send updated initial report draft with all relevant supporting documentation and relevant links.<o:p></o:p></li></ol><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'>Notes & Action items</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'> </span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><i><span style='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: </span></i><a href="https://community.icann.org/x/uQXVBQ"><i><span style='color:#1155CC'>https://community.icann.org/x/uQXVBQ</span></i></a><o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt'><o:p> </o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'>1. <b>Roll Call & SOI Updates</b> </span><o:p></o:p></p><ul style='margin-top:0in' type=disc><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l4 level1 lfo2;vertical-align:baseline'>Attendance will be taken from Adobe Connect<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l4 level1 lfo2;vertical-align:baseline'>Please remember to mute your microphones when not speaking, and state your name before speaking for transcription purposes.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l4 level1 lfo2;vertical-align:baseline'>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></li></ul><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'>2. <b>Welcome and Updates from EPDP Team Chair </b></span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'> a. Review of outstanding action items</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'> b. Other updates, if applicable</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><ul style='margin-top:0in' type=disc><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l2 level1 lfo3;vertical-align:baseline'>Today's goal is to continue going through the outstanding items for the Initial Report. <o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l2 level1 lfo3;vertical-align:baseline'>Thomas will also have an opportunity to finish discussing his memo.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l2 level1 lfo3;vertical-align:baseline'>ICANN Org liaisons may be asked to give a high-level overview of the memo.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l2 level1 lfo3;vertical-align:baseline'>Benedict delivered Purpose O last night, so this will also be added to the agenda.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l2 level1 lfo3;vertical-align:baseline'>The PCST (budget committee) decided to hold the third F2F in Toronto, Canada from 16 January - 18 January. Additionally, the team began a discussion about reengaging CBI.<o:p></o:p></li></ul><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'>3. <b>Continue review & discussion of comments / input received on Initial Report</b></span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'> Objective of discussion:</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'>(1) Review proposed changes / comments on the Initial Report that require EPDP Team consideration</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'>(2) Agree on if/how these proposed changes / comments are to be applied to the Initial Report</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'> a. Commence review of proposed changes / comments on the Initial Report</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><ul style='margin-top:0in' type=disc><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>The RrSG is meeting today to further discuss their comments, so for the Team's purposes today, we will not be discussing the Registrar issues at this time.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>Issues highlighted in green were dealt with yesterday.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>Beginning with Issue k, staff noted that per the PDP manual, recommendations to the GNSO Council can take many shapes or forms, including requests / advice to the GNSO Council. The recommendations, after adoption, are generally segregated to see who is responsible for carrying out the recommendation.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>If there is not a problem with asking the GNSO Council to do something, there may not be a problem. It would be helpful to go back to Kristina to better understand the issue. It will be important to specifically note when this group's work may impact other policies, including GNSO policies.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>Under letter m, what is the BC proposing to change?<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>The BC notes problems with the functioning of the URS/UDRP since Complainants no longer have access to data prior to filing UDRP/URS complaints.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>This issue was highlighted on this list, so Support Staff added some language to the Initial Report to reflect the expressed issues, noting there is not currently consensus whether this should be a recommendation or not. If further clarification is needed, please write to the list. <o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>The Team does need to address the concern of unlimited access to non-public data under the guise of filing a UDRP.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>Action Item: Margie to suggest modifications to the UDRP/URS paragraph to the list so other team members may opine on it.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>Issue j: this was discussed early on in the context of the triage report. There was confusion regarding what "in another mechanism" means, so the text "determined by the EPDP Team" was added for further clarification. The mechanism may refer to future work in relation to access to full registration data.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>The team did speak at length about future work regarding standard access framework; however, why is there a mechanism for access to full registration data from the registry operator?<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>If this language is confusing, it could be deleted. <o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>Do not see the value this bullet point provides - suggest removing.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>No disagreement to removing. This work is being addressed, just not at this stage.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>Preliminary recommendation 24 (letter n) - waiting for Kristina to provide further guidance.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>Going back to Issue n, it seems that agreement was reached to remove preliminary recommendation 24. (Note: this is now recommendation 21 in the updated report, so searching for exact language is better here.) <o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>Because this is confusing, can we discuss very deliberately what changes are proposed?<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>On 14 November, ICANN published a report on the Transfer Policy. Any review of any policy that ICANN undertakes should look at the implications of GDPR. This recommendation may be unnecessary.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>Is there a way to inform the GNSO they should do this now? <o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>There is no value in the recommendation as its written now.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>The Team needs to consider accurate data and this should not be pushed further down the road and never dealt with.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>A recommendation, noting the question, is useful.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>Items T and U - accuracy of registration data.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>Coming out of the meeting in Los Angeles, we noted we would not diminish the accuracy recommendations. This is a parking lot issue.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>Registrar proposal - minor wording change, but this small change does not affect the meaning one way or the other, so it's OK to keep the previously-agreed to language. In that spirit, Rrs oppose the BC addition.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>All attempts to ensure accuracy have to be weighed, including the cost impact.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>How is accuracy defined here? It may be helpful to describe it here. <o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>The accuracy provision says that the data subject must be able to correct data. If the controller believes there are inaccuracies, the controller has the obligation to try to fix it.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>This is a parking lot issue so does not need to be discussed right now, so long as the report mentions it, that is sufficient. <o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>Action item: Support staff to note the issue of WHOIS accuracy will be considered further in Phase 2. <o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4;vertical-align:baseline'>Regarding issue v, this is an example of the team deliberating on the issue. The third sentence regarding other relevant parties is ambiguous and seems confusing to implement.<o:p></o:p></li></ul><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt'><o:p> </o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'> b. Confirm approach for addressing these</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'> c. Confirm next steps, if any</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'> </span><o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:11.0pt'><o:p> </o:p></span></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'>4. <b>Confirm / discuss any input on the Thomas’s Responsibilities text (if any)</b></span><o:p></o:p></p><ul style='margin-top:0in' type=disc><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>ICANN's summary of response to Thomas's memo:<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>Instead of redlining, ICANN org thought it would be easier to read via a separate document.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>The Team's recommendation for joint controllership is different from what is currently in the Temp Spec.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>ICANN org's role is to provide information and implementation-related issues and concerns.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>Question: are there joint controllers or are they sole controllers? The examples the Art. 29 WP gives with respect to joint controllers are usually companies that operate on the same platform.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>How should the team work together going forward? <o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>ICANN org liaisons are flexible and are at the team's disposal to address this both in the initial report and after.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>The Team needs to get to a defendable solution to put in its Initial Report.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>Do any changes need to be made to the report at this time?<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>There is a risk that ICANN org liaisons will go back into listening mode, and unless ICANN org liaisons are an active participant in the process, this Team cannot make progress. <o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>Who are the authors of the memo so that the Team can make direct contact with the authors?<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>It would be helpful to offer concrete proposals to the community. <o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>Despite the Hamilton memo suggesting joint controllership, ICANN, in its cookbook suggests independent controllership. If this memo is not a position paper, what is it? Why did ICANN come to the conclusion that an independent controllership is present? If more analysis is necessary, how can ICANN come to the conclusion that a joint controllership is not present?<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>ICANN memo has one primary driver - there is a fear that we move to a certain construction without knowing to the full extent what the liability could be. Art. 26 was established for scenarios where the data subject is confronted with complex data processing schemes with multiple parties.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>The Team should set up a dedicated group, including contracted parties, to set up a road map for items that need to be considered in a JCA.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>The alternatives are joint controllership or sole controllership for ICANN's purposes.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>There has been factual analysis to support joint controllership. <o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>The GDPR does not specify a joint controller agreement is necessary, but rather, a joint controller <i>arrangement </i>is necessary. In this instance, the RA, the RAA, and the RRA is the arrangement.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>This is something that should have been sorted out in 2017. While this memo is welcome, how can this report be released absent a balanced discussion of the controllership issue? If ICANN has issues with it, what will ICANN add to counter that and how can this be denoted in the report?<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>The frustration is that this memo is coming so late in the day. While a written question may not have been directed to ICANN org, ICANN org was aware of the responsible parties analysis before the specific question was directed. If the Team manages to get to the finish line, we need assurance that this isn't going to be frustrated by an ICANN org determination that opposes the EPDP Team's conclusions.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>Where everyone agrees is that contracted parties and ICANN all need to sit down and work on a GDPR compliant arrangement.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>When ICANN says independent controller, is ICANN comfortable with co-controller instead?<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>It's not a matter of what ICANN org is comfortable with, but rather - what is the correct classification under GDPR.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>If ICANN has any documentation that went into the cookbook regarding sole controllership, please share with the EPDP team.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>While the implementation may be difficult, the factual determination comes first. It may be best to list all of the places we agree and note the places we do not agree.<o:p></o:p></li><li style='color:black;margin-top:0in;margin-bottom:0in;margin-bottom:.0001pt;mso-list:l1 level1 lfo5;vertical-align:baseline'>When making edits on the google doc, please make it clear what line number you are referring to.<o:p></o:p></li></ul><p class=MsoNormal style='margin-bottom:12.0pt'><b><span style='font-size:11.0pt'><o:p> </o:p></span></b></p><p style='margin:0in;margin-bottom:.0001pt'><b><span style='color:black'> 5. Wrap and confirm next meeting to be scheduled for Monday 19 November at 14.00 UTC.</span></b><b><o:p></o:p></b></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'> a. Confirm action items</span><o:p></o:p></p><p style='margin:0in;margin-bottom:.0001pt'><span style='color:black'> b. Confirm questions for ICANN Org, if any</span><o:p></o:p></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'><o:p> </o:p></span></p></div></body></html>