<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;
color:windowtext;}
.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:256720828;
mso-list-template-ids:-1551830620;}
@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:625817840;
mso-list-template-ids:636544990;}
@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:1291276839;
mso-list-template-ids:-1092997196;}
@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:1660839887;
mso-list-template-ids:1987983454;}
@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:1973976607;
mso-list-template-ids:1873730366;}
@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;}
@list l5
{mso-list-id:1981183707;
mso-list-template-ids:440045844;}
@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;}
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">Dear EPDP Team,<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">Apologies for the delay, but please find attached the notes and action items from yesterday’s EPDP Team meeting.<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">Best regards,<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">Caitlin, Berry and Marika<o:p></o:p></span></p>
<div style="mso-element:para-border-div;border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal" style="border:none;padding:0in"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
<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">EPDP Team Meeting #43<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:#767676">Wednesday, 6 February 2019</span><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">Notes and Action Items<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">High-level Notes/Actions:</span></b><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">Action item #1</span></b><span style="font-size:11.0pt;color:black">: Staff support team to circulate the second set of legal questions that have been sent to Bird & Bird for EPDP Team information.
(COMPLETED)<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">Action item #2</span></b><span style="font-size:11.0pt;color:black">: ICANN Org to respond to questions posed by RySG in relation to Controller Agreements (recommendation #13) and Contractual
Compliance (Recommendation #7), as soon as possible. (COMPLETED)<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">Action item #3</span></b><span style="font-size:11.0pt;color:black">: Registrar team encouraged to review BC input on Recommendation 9 - Org field - and provide feedback on the mailing list.<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">Action item #4:</span></b><span style="font-size:11.0pt;color:black"> EPDP Team to further review / consider Data Elements to be Transferred from Registrars to Registries (Rec 5) and put forward
proposed language for the Final Report, factoring in today's discussion (that could also be in relation to Rec #22, Impact on Other Policies).
<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">Action item #5</span></b><span style="font-size:11.0pt;color:black">: Staff Support Team to update Recommendation #5 (Data Elements to be Transferred from Registrars to Registries) in line with
edits suggested by Ayden during the meeting. (COMPLETED)<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">Action item #6</span></b><span style="font-size:11.0pt;color:black">: Leadership to work with legal committee on possible question in relation to Thick WHOIS. Margie to provide initial question
draft for Legal Team review.<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">Action item #7</span></b><span style="font-size:11.0pt;color:black">: In response to ICANN-raised issues, staff support team to circulate proposed language to address process for amendments
to Registry - Registrar Agreements. (COMPLETED)<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">Action item #8</span></b><span style="font-size:11.0pt;color:black">: In response to ICANN-raised issues, RySG reps to work with ICANN Org on proposed path forward in relation to bulk registration
data access to ICANN. <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">Action item #9</span></b><span style="font-size:11.0pt;color:black">: EPDP Team to continue discussion on the mailing list in relation to recommendation #12 (Reasonable Access) in view of coming
to agreement by tomorrow's meeting.<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">Questions for ICANN Org from the EPDP Team</span></b><span style="font-size:11.0pt;color:black">: None<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">Notes & Action items</span></b><span style="font-size:11.0pt;color:black"><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;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"><span style="font-size:11.0pt;color:black">Proposed Agenda:<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">1. Roll Call & SOI Updates<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">Attendance will be taken from Adobe Connect<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">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:l1 level1 lfo1;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;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">2. Welcome and Updates from EPDP Team Chair (5 minutes)<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.25in;text-indent:-.25in"><span style="font-size:11.0pt;color:black"> a. Review of outstanding action items<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.25in;text-indent:-.25in"><span style="font-size:11.0pt;color:black"> b. Other updates, if applicable<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Target to end this meeting in 1 hour and 15 minutes to avoid conflicts with other meetings<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l3 level1 lfo2;vertical-align:baseline">
<span style="font-size:11.0pt">Set of legal questions have been sent to Bird & Bird, addressing city field / redaction, meaning of accuracy with regards to GDPR, geographic implications / stable establishments.
<o:p></o:p></span></li></ul>
<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">Action item #1</span></b><span style="font-size:11.0pt;color:black">: Staff support team to circulate the second set of legal questions that have been sent to Bird & Bird for EPDP Team information.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l5 level1 lfo3;vertical-align:baseline">
<span style="font-size:11.0pt">Encourage continued mailing list deliberations. See input / questions in relation to recommendation #13 - ICANN Org requested to respond to questions posed by RySG as well as rec #7 (compliance) questions from James. Note also
issues flagged in relation to Rec #9 - Org field. <o:p></o:p></span></li></ul>
<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">Action item #2</span></b><span style="font-size:11.0pt;color:black">: ICANN Org to respond to questions posed by RySG in relation to Controller Agreements (recommendation #13) and Contractual
Compliance (Recommendation #7), as soon as possible.<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">Action item #3</span></b><span style="font-size:11.0pt;color:black">: Registrar team encouraged to review BC input on Recommendation 9 - Org field - and provide feedback on the mailing list.
<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">3. Recommendation #5 – Transmission of Registration data from Registrar to Registry (30 minutes)<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.25in;text-indent:-.25in"><span style="font-size:11.0pt;color:black"> a. RySG to present updated language proposal<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.25in;text-indent:-.25in"><span style="font-size:11.0pt;color:black"> b. Discuss proposal<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.25in;text-indent:-.25in"><span style="font-size:11.0pt;color:black"> c. Confirmation of agreement reached or next steps to come to agreement<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4;vertical-align:baseline">
<span style="font-size:11.0pt">See updated language circulated by RySG - two-pronged approach taken. Concept of the workbooks, although vital to provide the context, are specifically as an annex as work done to come to a conclusion, not the policy recommendation
itself. Bullet two, in relation to purpose 1B - depending on the individual registry and controllership, they might not need the transfer of registrant data to fulfil their purposes. As such, proposed rewritten bullet 2 - explaining this concept of "mean data
set" - each purpose has its own minimum data set. Collection can be unique, but it is for each one of the purposes / processing set. Need to figure out what is the common data set collected across all purposes - would be mean data set. This also includes data
elements that may not be transmitted to each registry as certain registries may not need it for its purposes. Don't want to push registries to take data that they don't want and need. At the same time, there can be a departure from the minimum data set for
registries that do need this additional data. Took out reference to rec 22 - it will still serve its purpose, which will also include consideration of Thick Whois policy. No need to complicate it here by referencing to rec 22.
<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4;vertical-align:baseline">
<span style="font-size:11.0pt">Consider using "aggregate minimum data set", instead of 'mean' data set.
<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4;vertical-align:baseline">
<span style="font-size:11.0pt">How can this EPDP overwrite another Consensus Policy? Need further analysis of the impact. Consider referring this to the GNSO Council.
<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4;vertical-align:baseline">
<span style="font-size:11.0pt">What happens if a registrar doesn't think a registry needs the data, but the registry does need the data? Could create an untenable situation. Seems to remove ICANN's role in this decision of what information is required to be
sent to registry. <o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4;vertical-align:baseline">
<span style="font-size:11.0pt">This group would not be deleting the Thick Whois policy but is saying that the GNSO Council has to look as this and other policies because Compliance with GDPR , as is our mandate, requires it.
<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4;vertical-align:baseline">
<span style="font-size:11.0pt">EPDP Team has been working on this for a long time now and did not find a justification for transferring all data, but just for a subset / mean data set. Additional data requires additional justification, which can, for some be
6 I b and for some 6 I f. Remember, for 6 I f, a party needs to claim to have a legitimate interest. You cannot force someone to have an interest.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4;vertical-align:baseline">
<span style="font-size:11.0pt">Each purpose has its own data set and its own minimum data set - in this recommendation trying to figure out which data has to be transferred to registries across all purposes (mean data set).
<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4;vertical-align:baseline">
<span style="font-size:11.0pt">The "Thick" Whois Consensus Policy requires itself to be revised, should conflicts with privacy/data protection law become apparent anyway. So recommendation 5 seems perfectly compatible with it. It should be seen to be helpful
to its implementation.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4;vertical-align:baseline">
<span style="font-size:11.0pt">Balancing in relation to thick WHOIS may need to be reconsidered - did not factor in GDPR at the time - not for this team, has to be done somewhere else. Covered by recommendation #22.
<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4;vertical-align:baseline">
<span style="font-size:11.0pt">Consider better defining or naming the concept of mean data set - aggregate minimum data set.<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4;vertical-align:baseline">
<span style="font-size:11.0pt">Not often that the work in one PDP that conflicts with the work of another PDP. No way to reconcile those two.
<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4;vertical-align:baseline">
<span style="font-size:11.0pt">"Provided an appropriate legal basis exists" that is the work that went into the data elements workbooks.
<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4;vertical-align:baseline">
<span style="font-size:11.0pt">Important to recognize in the report that the EPDP Team has gone through the details of mapping all the processing activities and legal basis.
<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4;vertical-align:baseline">
<span style="font-size:11.0pt">Consider posing question to Ruth whether there is a legal basis for transfer from data from registrar to registry under 6(1)b.
<o:p></o:p></span></li><li class="MsoNormal" style="color:black;mso-list:l0 level1 lfo4;vertical-align:baseline">
<span style="font-size:11.0pt">Possible rewording: "As part of this analysis, the EPDP Team has identified a set of data elements that are required to be transferred from the registrar to the registry in order to fulfill the Purposes for Processing Registration
Data. This set of data elements constitutes an “aggregate minimum data set.” This is an aggregate minimum data set of all identified Purposes that registrars will be required to transfer to registries. This aggregate minimum data set also includes those data
elements that MAY NOT be transferred from the registrar to the registry, where such a registry does not require such a transfer (with due regard to that registry’s terms, conditions, and policies)."<o:p></o:p></span></li></ul>
<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">Action item #4:</span></b><span style="font-size:11.0pt;color:black"> EPDP Team to further review / consider Data Elements to be Transferred from Registrars to Registries (Rec 5) and put forward
proposed language for the Final Report, factoring in today's discussion (that could also be in relation to Rec #22, Impact on Other Policies).<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">Action item #5</span></b><span style="font-size:11.0pt;color:black">: Staff Support Team to update Recommendation #5 (Data Elements to be Transferred from Registrars to Registries) in line
with edits suggested by Ayden during the meeting. <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">Action item #6</span></b><span style="font-size:11.0pt;color:black">: Leadership to work with legal committee on possible question in relation to Thick WHOIS. Margie to provide initial question
draft for Legal Team review.<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">4. ICANN Org Questions (30 minutes)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">Per last week’s action item, 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<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:-.5in"><span style="font-size:11.0pt;color:black">a. Consider topics flagged<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:-.5in"><span style="font-size:11.0pt;color:black">b. Discuss proposed approach (‘what happens if these topics are not addressed / covered in the Final Report?’)<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:-.5in"><span style="font-size:11.0pt;color:black">c. Confirmation of agreement reached or next steps to come to agreement<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></p>
<ul style="margin-top:0in" type="disc">
<li class="MsoNormal" style="color:black;mso-list:l4 level1 lfo5;vertical-align:baseline">
<span style="font-size:11.0pt">Process for amendments to Registry - Registrar Agreements: objective of this provision was to streamline process for RRA amendments. Might be beneficial to have included in the policy recommendations? Consider addressing this
in implementation. Consider adding a general recommendation that would state something like: "policy should include a predictable and transparent process for RRA amendments". Or include under the implementation section language such as: "as part of the implementation,
a process for amendments to Registry - Registrar agreements needed to implement EPDP recommendations should be considered".
<o:p></o:p></span></li></ul>
<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">Action item #7</span></b><span style="font-size:11.0pt;color:black">: In response to ICANN-raised issues, staff support team to circulate proposed language to address process for amendments
to Registry - Registrar Agreements. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"><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">Notices to Registered Name Holders Regarding Data Processing - already covered by GDPR, this is too prescriptive, not necessary. Work through in implementation - too specific here. Some of it may still be covered, but to be considered
in implementation. No need for policy language that duplicates legal obligations.
<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">Bulk Registration Data Access to ICANN - many registries transferred data that included personal data, this appendix is aimed to clarify that no personal data is to be transferred. Does this rise up to a recommendation level,
or is this an action that ICANN could take to notify registries or is this a contract amendment? Better addressed as a contract amendment. Current agreement says that Registry MAY sent a full escrow deposit - now they have to strip it as a result of this provision.
ICANN Org does not want to receive a full escrow deposit. What would happen if this provision is not continued.
<o:p></o:p></span></li></ul>
<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">Action item #8</span></b><span style="font-size:11.0pt;color:black">: In response to ICANN-raised issues, RySG reps to work with ICANN Org on proposed path forward in relation to bulk registration
data access to ICANN. <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">5. Recommendation #12 – Reasonable Access (30 minutes)<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:-.5in"><span style="font-size:11.0pt;color:black"> a. Review revised proposal<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:-.5in"><span style="font-size:11.0pt;color:black"> b. Discuss revised proposal<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:.5in;text-indent:-.5in"><span style="font-size:11.0pt;color:black"> c. Confirmation of agreement reached or next steps to come to agreement<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">Action item #9</span></b><span style="font-size:11.0pt;color:black">: EPDP Team to continue discussion on the mailing list in relation to recommendation #12 (Reasonable Access) in view of coming
to agreement by tomorrow's meeting.<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">6. Review of additional topics raised (if time allows)<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">7. Wrap and confirm next meeting to be scheduled for Thursday, 7 February 2019 at 14.00 UTC (5 minutes)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> a. Confirm action items<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<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><i><span style="font-size:10.0pt;color:black">Marika Konings</span></i></b><span style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:black">Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) </span></i><span style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:black">Email: <a href="mailto:marika.konings@icann.org"><span style="color:#0563C1">marika.konings@icann.org</span></a> </span></i><span style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:black"> </span></i><span style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:black">Follow the GNSO via Twitter @ICANN_GNSO</span></i><span style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><i><span style="font-size:10.0pt;color:black">Find out more about the GNSO by taking our <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__learn.icann.org_courses_gnso&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=5DXgId95wrCsHi--pxTiJD7bMB9r-T5ytCn7od3CF2Q&s=Cg5uQf0yAfw-qlFZ0WNBfsLmmtBNUiH0SuI6Vg-gXBQ&e="><span style="color:#0563C1">interactive
courses</span></a> and visiting the <a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__gnso.icann.org_sites_gnso.icann.org_files_gnso_presentations_policy-2Defforts.htm-23newcomers&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=5DXgId95wrCsHi--pxTiJD7bMB9r-T5ytCn7od3CF2Q&s=tT-E2RoAucUb3pfL9zmlbRdq1sytaEf765KOEkBVCjk&e="><span style="color:#0563C1">GNSO
Newcomer pages</span></a>. </span></i><span style="font-size:10.0pt;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>