<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;}
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:12.0pt;
font-family:"Calibri",sans-serif;}
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:738866343;
mso-list-template-ids:1067384406;}
@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:986863389;
mso-list-template-ids:2114330570;}
@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:1883512323;
mso-list-template-ids:906267424;}
@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:1912690194;
mso-list-template-ids:-1981676920;}
@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:2042049188;
mso-list-template-ids:-699368790;}
@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 class=MsoNormal><span style='font-size:11.0pt;color:black'>Dear EPDP Team,<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 the notes and action items from the last EPDP meeting on Thursday, 31 January 2019.<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 Meeting #41</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'>31 January 2019</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'>Action Item #1</span></b><span style='font-size:11.0pt;color:black'>: EPDP Leadership to propose updated language for Rec. 11 (data retention) based on the discussion from today’s meeting.</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'>Action Item #2</span></b><span style='font-size:11.0pt;color:black'>: Registry and Registrar EPDP Team Members to review implementation bridge options with respective stakeholder groups and come forward with a proposal for the next EPDP Team meeting on Tuesday, 5 February.</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'>Action Item #3</span></b><span style='font-size:11.0pt;color:black'>: EPDP Team to review additional ICANN org questions and indicate on the email list if any of these need to be addressed in the Final Report</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><b><u><span style='font-size:11.0pt;color:black'>Notes</span></u></b><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </span><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 (5 minutes)</span></b><b><span style='font-size:11.0pt'><o:p></o:p></span></b></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'> </span></b><b><span style='font-size:11.0pt'><o:p></o:p></span></b></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><b><span style='font-size:11.0pt'><o:p></o:p></span></b></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </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 lfo1;vertical-align:baseline'><span style='font-size:11.0pt'>Today's meeting will mark the end of public comment review<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo1;vertical-align:baseline'><span style='font-size:11.0pt'>Between today and tomorrow, the Leadership Team will review proposed edits to the draft recommendations and come back with proposed language for inclusion in Final Report. <o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo1;vertical-align:baseline'><span style='font-size:11.0pt'>The Support Team will send an updated draft of the Final Report to the EPDP Team tomorrow, Friday, 1 Feb.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo1;vertical-align:baseline'><span style='font-size:11.0pt'>Following receipt of the proposed language, EPDP Team Members should flag any issues they believe warrant further discussion.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo1;vertical-align:baseline'><span style='font-size:11.0pt'>There will be meetings on Tuesday, Wednesday, and Thursday of next week.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo1;vertical-align:baseline'><span style='font-size:11.0pt'>In terms of getting the Final Report out - we plan to distribute the next draft tomorrow, Friday, 1 Feb.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo1;vertical-align:baseline'><span style='font-size:11.0pt'>Leadership will also send out the consensus call paperwork early next week.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l1 level1 lfo1;vertical-align:baseline'><span style='font-size:11.0pt'>There is a status of review document on the wiki page. The next step is for leadership to look at comments received and propose a path forward. Support Team is planning to update the Final Report based on suggested edits as well as agreed-upon text.<o:p></o:p></span></li></ul><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>EPDP Team Feedback:</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:l4 level1 lfo2;vertical-align:baseline'><span style='font-size:11.0pt'>The recommendations should be voted as a package - they should not be voted on in isolation.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l4 level1 lfo2;vertical-align:baseline'><span style='font-size:11.0pt'>Crystal clear recommendations are a good goal, but in the process of consensus building, this may be impossible.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l4 level1 lfo2;vertical-align:baseline'><span style='font-size:11.0pt'>There needs to be sufficient time to review a final draft so that everyone can see what the report says.<o:p></o:p></span></li></ul><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </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. Reminder: process for email discussions and upcoming deadlines</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. Review of outstanding 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'>c. Other updates, if applicable</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </span><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 public comments on Initial Report and/or revised recommendations</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;color:black'> </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. Recommendation 11 – Data retention (20 minutes)</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>i. Review small team updates and input provided (see PCRT at https://community.icann.org/x/U4cWBg and small team recommendations). ii. Review input provided (RySG, RrSG, GAC) (5 minutes)</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>Confirmation of agreement reached or next steps to come to agreement (5 minutes)</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </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:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>Edits came from Ry/Rr public comments<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>Paragraph 1: One year retention period linked to the TDRP was originally recommended - if it is being retained for purposes of the TDRP, any data retained could only be used for the TDRP.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>Paragraph 2: The EPDP Team did identify the TDRP as a means to justify the retention period. Registrars, if they use retained data for something under the TDRP, it would be under their own controllership.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>Paragraph 3: in the absence of having text in the actual recommendation - it should not be construed to mean that contracted parties cannot set their own retention periods for their own purposes. The current waiver procedure must be maintained. Consider a fast track for waivers accepted, that parties within the same jx would be subject to the same waiver without having to apply separately.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>Waiver procedures do not need to be applied to this recommendation. We may need a general disclaimer that notes that local laws have precedence.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>It seems that public comments from non-CPH have not been factored into the text of the updated recommendation.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>Should additional time be considered - public comments note 3 - 6 years. The language here is too restrictive - there may be other uses beyond the Transfer Policy.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>To make a case to retain the data past one year - does the benefit of investigating something that happened on a name that's not under the registrant's control outweigh the risk to the data subject?<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>Saying data might be necessary at some point in the future is not a good enough reason to retain it<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>The Team could consider remaining open to requests to change the retention period based on certain requirements.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>Retention periods under one year are highly problematic for investigations.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>How proportional is it to save data and for how long. The argument has been made to retain data longer.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>A balance is important here - what worked in the past may not work going forward, and we need to recognize new limitations and adjust accordingly.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>The EPDP Team, as soon as practicable, recommends ICANN to undertake a review of all active process and procedures - including other lawful needs.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>Not comfortable with ICANN conducting a study to determine retention for other needs. It’s likely this study would be biased.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>It's not just about the retention period but also who would have access to the data - this would be part of the study.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>We need to remember what we are doing here - do any public comments received warrant a change to the language. At this point, there does not appear to be comments that warrant change to the language. With respect to longer retention periods - no one would come up with a robust rationale as to why we need a longer period - therefore, we should keep what we have.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l0 level1 lfo3;vertical-align:baseline'><span style='font-size:11.0pt'>Action Item: EPDP Leadership to propose updated language for Rec. 11 based on today's conversation.<o:p></o:p></span></li></ul><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'>4. Implementation Transition Period (30 minutes)</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;color:black'>The GNSO Council Leadership has requested the team further discuss next steps regarding implementation transition period and notes it may be helpful to include a recommendation in the Final Report.</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </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:l2 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>This item was discussed in Toronto, and the Team discussed the bridging of a policy that will be adopted in the interim.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>The gap is the time b/w when the Temp Spec expires and the new policy goes into effect.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>The CPH have mixed feelings - could there be a compliance framework MOU with ICANN org, i.e., as long as CPH as doing their best efforts to comply with the new policy. Others are asking for something more formal.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>The Council Leadership is requesting a recommendation to come from the community, rather than ICANN org.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>There is not a consensus position within the RySG among the possible avenues forward. It may be more productive to defer this topic until next Tuesday.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>A framework should have input beyond the contracted parties. However, it would be problematic if there was zero enforcement of the Temp Spec.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>The general sentiment re: this gap is that the decision should rest with the EPDP Team.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>Would this compliance framework be enforceable?<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>To the question of timing - if the Team is planning to issue a recommendation of a compliance framework, that could be considered in parallel with finalization of the Final Report.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>The risk of having something more formal - this could be challenged by a given contracted party as an extension of the Temp Spec - and this may open the door to challenging the Temp Spec was implemented as an SSR emergency.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>Important to get some guidance from ICANN org on their preferred path forward.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>Need to think through timelines - this should be fleshed out with some degree of specificity by Tuesday. We need to think about providing a solution in a timely manner. Contracted parties should get support around a model and begin fleshing it out.<o:p></o:p></span></li><li class=MsoNormal style='color:black;mso-list:l2 level1 lfo4;vertical-align:baseline'><span style='font-size:11.0pt'>Action item: CPH to Put formal question in front of stakeholder group and come forward with a proposal for Tuesday's meeting.<o:p></o:p></span></li></ul><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'>5. ICANN Org Questions</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;color:black'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'>There are six questions posed by ICANN within this table. Read the first three questions in five minutes.</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. ICANN Org Liaisons to introduce questions for discussion</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;color:black'>1. RDAP and SLAs – what recommendations and/or guidance needs to be included in the Final Report, or is this to be addressed during implementation?</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </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:l3 level1 lfo5;vertical-align:baseline'><span style='font-size:11.0pt'>This work comes from a spreadsheet emailed to the EPDP Team. The spreadsheet sought to identify changes from the Temp Spec and also areas where the Initial Report was silent.<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'>Is there a good reason why the language was not included in the Initial Report?<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'>What will happen to RDAP is the EPDP TEam is silent on this?<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'>If there are additional items that need to be discussed, please flag them so we can add to the agendas next week.<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'>Question: if the Team is silent, is this to be confirmed as policy, or not?<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'>If the Temp Spec does not confirm, requirements from RA/RAA would control.<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'>If the Team did not confirm the Temp Spec to be approved as policy, it would not be retained as policy.<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'>The difference b/w the Temp Spec and what the EPDP Team is doing is the the EPDP Team is creating a new policy, while the Temp Spec is part of the contracts until May 25.<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'>There is no need to include any of these items in the Team's Phase 1 report.<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'>RDAP has not been implemented, and this is not necessary for GDPR compliance. What problem would be solved by putting this language in the Final Report?<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'>There should be an RDAP mention in the policy, otherwise there is no obligation.<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'>The Team's work to make its processes GDPR compliant - we will not include in Phase 1 of its work. The Support Team can consider adding proposed language in the Final Report. <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'>Action Item: EPDP Team to review additional ICANN org questions and indicate on the list if any of these need to be addressed in the Final Report<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'>On notices to RNH - this is changing specific requirements in the RAA - adds elements that conform to GDPR requirements.<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'>Consent provision - language has restrictions on consent based on GDPR<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'>Bulk registrations - Temp Spec requires only thin data<o:p></o:p></span></li></ul><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;color:black'>2. RDDS Search Capabilities - should the requirements in the Temp Spec be confirmed by the EPDP Team in the Final Report or is this to be further considered in phase 2?</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> 3. Bulk data registration access to ICANN – should the requirements in the Temp Spec be confirmed by the EPDP Team in the Final Report?</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;color:black'>4. Process for amendments to Registry – Registrar agreements – should the process in the Temp Spec be confirmed as a policy recommendation, or is this to be addressed during implementation?</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;color:black'>5. Does the ‘consent’ provision in the Temporary Specification require confirmation in the Final Report or is this to be addressed during implementation as consent is already defined in the GDPR?</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal style='margin-left:.5in'><span style='font-size:11.0pt;color:black'>6. Notices to Registered Name Holders Regarding Data Processing - is this required to be addressed in the Final Report or is this part of implementation or in direct consultation with registrars?</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. Confirmation of agreement reached or next steps to come to agreement</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;color:black'>6. Wrap and confirm next meeting to be scheduled for Tuesday, 5 February 2019 at 14.00 UTC (5 minutes)</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;color:black'>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'>Confirm questions for ICANN Org, if any</span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </span><span style='font-size:11.0pt'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;color:black'> </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'><o:p> </o:p></span></p></div></body></html>