<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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
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:667832417;
mso-list-type:hybrid;
mso-list-template-ids:222960426 67698711 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-number-format:alpha-lower;
mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:1.75in;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.75in;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:3.25in;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.25in;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:4.75in;
text-indent:-9.0pt;}
@list l1
{mso-list-id:770199161;
mso-list-type:hybrid;
mso-list-template-ids:1621901280 2139232284 67698713 67698689 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:68.1pt;
text-indent:-50.0pt;
mso-ansi-font-size:11.0pt;
font-family:"Calibri",sans-serif;
color:black;
mso-ansi-font-weight:normal;
mso-bidi-font-weight:normal;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:72.1pt;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:117.1pt;
text-indent:-.25in;
font-family:Symbol;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:144.1pt;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:180.1pt;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:216.1pt;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:252.1pt;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:288.1pt;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:324.1pt;
text-indent:-9.0pt;}
@list l2
{mso-list-id:824854067;
mso-list-template-ids:-502873238;}
@list l2:level1
{mso-level-number-format:alpha-lower;
mso-level-text:"%1\)";
mso-level-tab-stop:.75in;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;
mso-ascii-font-family:Calibri;
mso-fareast-font-family:"Times New Roman";
mso-hansi-font-family:Calibri;
mso-bidi-font-family:Calibri;
color:black;}
@list l2:level2
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:1.25in;
text-indent:-.25in;}
@list l2:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;
font-family:Symbol;
mso-bidi-font-family:Symbol;}
@list l2:level4
{mso-level-tab-stop:2.25in;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;}
@list l2:level5
{mso-level-tab-stop:2.75in;
mso-level-number-position:left;
margin-left:2.75in;
text-indent:-.25in;}
@list l2:level6
{mso-level-tab-stop:3.25in;
mso-level-number-position:left;
margin-left:3.25in;
text-indent:-.25in;}
@list l2:level7
{mso-level-tab-stop:3.75in;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;}
@list l2:level8
{mso-level-tab-stop:4.25in;
mso-level-number-position:left;
margin-left:4.25in;
text-indent:-.25in;}
@list l2:level9
{mso-level-tab-stop:4.75in;
mso-level-number-position:left;
margin-left:4.75in;
text-indent:-.25in;}
@list l3
{mso-list-id:1389113251;
mso-list-type:hybrid;
mso-list-template-ids:-461865578 904815544 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l3:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.0in;
text-indent:-.25in;
font-family:"Calibri",sans-serif;
mso-fareast-font-family:"Times New Roman";}
@list l3:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.5in;
text-indent:-.25in;
font-family:"Courier New";}
@list l3:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.0in;
text-indent:-.25in;
font-family:Wingdings;}
@list l3:level4
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.5in;
text-indent:-.25in;
font-family:Symbol;}
@list l3:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.0in;
text-indent:-.25in;
font-family:"Courier New";}
@list l3:level6
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:3.5in;
text-indent:-.25in;
font-family:Wingdings;}
@list l3:level7
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.0in;
text-indent:-.25in;
font-family:Symbol;}
@list l3:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:4.5in;
text-indent:-.25in;
font-family:"Courier New";}
@list l3:level9
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:5.0in;
text-indent:-.25in;
font-family:Wingdings;}
@list l4
{mso-list-id:1402102271;
mso-list-template-ids:-502873238;}
@list l4:level1
{mso-level-number-format:alpha-lower;
mso-level-text:"%1\)";
mso-level-tab-stop:.75in;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;
mso-ascii-font-family:Calibri;
mso-fareast-font-family:"Times New Roman";
mso-hansi-font-family:Calibri;
mso-bidi-font-family:Calibri;
color:black;}
@list l4:level2
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:1.25in;
text-indent:-.25in;}
@list l4:level3
{mso-level-number-format:bullet;
mso-level-text:;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;
font-family:Symbol;
mso-bidi-font-family:Symbol;}
@list l4:level4
{mso-level-tab-stop:2.25in;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;}
@list l4:level5
{mso-level-tab-stop:2.75in;
mso-level-number-position:left;
margin-left:2.75in;
text-indent:-.25in;}
@list l4:level6
{mso-level-tab-stop:3.25in;
mso-level-number-position:left;
margin-left:3.25in;
text-indent:-.25in;}
@list l4:level7
{mso-level-tab-stop:3.75in;
mso-level-number-position:left;
margin-left:3.75in;
text-indent:-.25in;}
@list l4:level8
{mso-level-tab-stop:4.25in;
mso-level-number-position:left;
margin-left:4.25in;
text-indent:-.25in;}
@list l4:level9
{mso-level-tab-stop:4.75in;
mso-level-number-position:left;
margin-left:4.75in;
text-indent:-.25in;}
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">Please find below the notes and action items from today’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">As a reminder, the next meeting will be Thursday, 18 June at 14:00 UTC.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><br>
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">Marika, Berry, and Caitlin<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>
<p class="MsoNormal"><b><u><span style="font-size:11.0pt;color:black">Action Items<o:p></o:p></span></u></b></p>
<p class="MsoNormal"><b><u><span style="font-size:11.0pt;color:black"><o:p><span style="text-decoration:none"> </span></o:p></span></u></b></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black">1. After reviewing the Team’s progress today, Leadership suggests we start with item 35 tomorrow and review Rec. 6 during our meeting on Tuesday, 23 June. In the meantime, Support Staff to rewrite/reorganize
Rec. 6 in line with today’s discussion.<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">2. Laureen to propose alternate wording to footnote 9, factoring in the different positions expressed during today's call. FN9: Compliance will not be in a position to address the merits of the
request itself or the legal discretion of the Contracted Party making the determination. Proposal to delete the last clause (or the legal discretion of the CP making the determination).
<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. Margie to draft footnote for Rec. 4 regarding NIS EU law.<o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;color:black"><o:p> </o:p></span></b></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;color:black">EPDP Phase 2 - Meeting #65</span></b><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">Proposed Agenda</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">Wednesday 17 June 2020 at 14.00 UTC<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;color:black"> <o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:67.7pt;margin-bottom:.0001pt;text-indent:-49.7pt;mso-list:l1 level1 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Roll Call & SOI Updates (5 minutes)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:67.7pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:67.7pt;margin-bottom:.0001pt;text-indent:-49.7pt;mso-list:l1 level1 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Confirmation of agenda (Chair)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:67.7pt;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:67.7pt;margin-bottom:.0001pt;text-indent:-49.7pt;mso-list:l1 level1 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Welcome and housekeeping issues (Chair) (5 minutes)<o:p></o:p></span></p>
<p class="MsoListParagraph" style="margin:0in;margin-bottom:.0001pt"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.95in;margin-bottom:.0001pt;text-indent:-50.0pt;mso-list:l1 level1 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><span style="mso-list:Ignore">4.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Continue run through of yellow items (items identified for further discussion / clarification)<o:p></o:p></span></p>
<ul type="disc">
<li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 11 (Rec. 8)</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Proposed deletion of this sentence: Information resulting from the alert mechanism is also expected to be included
in the SSAD Implementation Status Report (see recommendation #19) to allow for further consideration of potential remedies to address abusive behavior.
<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Can this sentence be moved to the small team for Rec. 19?<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Proposal to add this element in the suggested scope of MfE<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">RySG – suggestion was to delete this sentence entirely; however, proposed a compromise to, instead, add to the scope
of Rec. 19. The small group should consider this.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The focus of the mechanism is on implementation aspects only. At the moment, the abuse provisions are part of the policy,
so there may be a need to move these elements to implementation. The small team should consider this.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Footnote 9: ICANN Compliance will not be in a position to address the merits of the request itself or the legal discretion
of the Contracted Party making the determination. Proposal to delete the last clause (or the legal discretion of the CP making the determination). Unclear what legal discretion means in this context. Additionally, if further guidance is received, ICANN Compliance
may be in a position to review how the CP applied this determination. <o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The footnote should be kept as is<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Believe ICANN Compliance expressed an unwillingness to do this<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Do not understand why CPs have difficulties with the bracketed language to be discussed in the evolutionary model.
Troubled why this section is problematic at this juncture when it has been there for quite some time.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Is there a way to rephrase this footnote – the legal discretion of the CP is not very helpful. Could contemplate scenarios
where DPA guidance is received on how to apply the GDPR, whether it’s the balancing test or whether it’s in reference to other permissible lawful basis under Article 6. ICANN should be able to review if subsequent guidance is received. This language forecloses
any role for ICANN Compliance to ensure CPs are abiding by the law.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Do not think it is ICANN Compliance’s role or remit to ensure CPs are complying with the law. Need to ensure that policy
recs are flexible enough so that CPS can comply with the law.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">ICANN Compliance does not interpret the law; ICANN Compliance defers to CPs to interpret the law.
<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This conversation supposes that every case involves a balancing test; this is not correct – some evaluations do not
involve personal data<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Confused if ICANN Compliance always grants a waiver if a CP believes it is following its local law – that does not
seem correct.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There are paths where data that is not covered by the GDPR is involved; however, you need to see if there is a valid
case for disclosure for any case.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Understand good CPs comply, but how do we deal with the bad CPs? The current language seems to give bad CPs a free
pass. There is a CP that denies every request, irrespective of it’s a valid request.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Action: Laureen to come up with alternative language for the Team to consider.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 12:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">If a requestor is of the view that its request was denied in violation of the procedural requirements of this policy, a complaint MAY be filed with ICANN Compliance</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Significant issue for BC. If there is a situation regarding systemic abuse, there needs to be a mechanism to deal with
this. Need the ability to submit substantive requests.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This is a type of guarantee that cannot be given. Even if this language is erased, there is no guarantee that Compliance
is going to do anything. You can only complain that CPs are violating the policy.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">ICANN Compliance MUST make available an alert mechanism by which requestors as well as data subjects whose data has
been disclosed can alert ICANN Compliance if they are of the view that disclosure or non-disclosure is the result of systemic abuse by a Contracted Party. This alert mechanism is not an appeal mechanism – to contest disclosure or non-disclosure affected parties
are expected to use available dispute resolution mechanisms such as courts or Data Protection Authorities – but it should help inform ICANN Compliance of potential systemic abuse which should trigger appropriate action<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This is not about guarantees; this is about forms of recourse. Being able to report on the number of alerts vs. number
of requests will give us statistical guidance to assist in going forward.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This provision is not just meant to address systemic abuse. If there is a domain name with no personal data, ICANN
Compliance should be able to enforce disclosure.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Cases where there is no personal data should not be denied; however, this is not a compliance issue – how would you
even know if there is no personal data? <o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The issue is Compliance is not willing to look at the substance.
<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 13 - 14</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">: awaiting GAC input on examples
of urgent requests – GAC Team came back recently – no need to further illustrate the categories listed.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Question for the group – any concern with GAC-proposed approach? Adding definition of critical infrastructure?<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Agree with GAC Proposal – leave four bullet points and reference the proposed definition in a footnote<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 15:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Remove “or in another standardized
place that may be designated by ICANN from time to time.”<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">No objections – remove language.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 16</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">: MAY reassign the priority level
during the review of the request, in accordance with the requirements above. <span style="color:black">
Would the EPDP team consider instead that a request that does not meet the requirements for Priority 1 or 2 may be rejected and may be refiled?</span><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This would be an easier approach<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">However, would not be open to also allowing for a longer response time instead of dealing with the same request twice.
<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Idea of reassignment as part of evolution may be the right approach.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The steps outlined in the recommendation are logical and could be followed and imposed<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 17</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">: definition of Priority 2 requests
- <span style="color:black">In Rec #NEW, Priority 2, can the EPDP team please clarify if this priority is intended to be available only to ICANN-approved dispute resolution service providers, or should it also be available to parties and potential parties
in administrative proceedings?</span><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This is limited to providers<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Clarify this in the text<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 18:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">In Rec #NEW, Priority 3 seems to contemplate a bifurcation within this priority level resulting in 4 priority levels. For implementation purposes, the system would require
a fourth category, even if the contracted party were to choose to treat the two priority levels the same. Would it make more sense to create a fourth priority level to allow for this?</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">No need to create a new priority level. This language gives CPs the discretion to prioritize certain types of requests
if CPs feel this is warranted<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This is not a new priority level, this is a flag that could be put on a request<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Leave as is<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 19:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">In Rec #NEW, a. Abuse of urgent requests: For clarity during implementation, does the EPDP team contemplate any recommendations regarding abuse of the use of other priority
levels? For example, what if a requester regularly incorrectly cites Priority 2, and those requests are downgraded. Would that be considered abuse?</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If we limit the ability of Priority 2 requests to providers, this danger is negligible<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">No change necessary<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 20</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">: Rec. 4<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Either delete “Digital service provider (DSP)” or clarify what the intended purpose is.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Should not use these terms unless we define what we mean<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Do not understand this as a requestor purpose<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Keep digital service provider, add a footnote reference for NIS<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">How does this relate to a purpose for disclosure of registration data?<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Purpose is fulfillment of a legal obligation<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Even if there is a definition, that does not make it a purpose. Criminal investigation is a purpose; criminal law is
not<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Margie to draft footnote for Item 20<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 21:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Unclear that the reference to Paragraph 9 is appropriate. If there is no personal data involved (and not otherwise prohibited by law), the requested data must be disclosed
</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The change in order has asked the disclosing party to process personal data where it doesn’t have a reason to do so
at that stage. When CP gets a request, the CP has to perform a prima facie case to see if it’s a valid request. By changing 7 to number 1, it is creating a legal risk – process should revert back to how it was.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Phase 1 allowed information that is not subject to GDPR to be redacted. SSAD is the way to get access to data that
doesn’t need to be redacted. If we can’t do this, we are weakening our ability to comply with GDPR but not over-comply with GDPR.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Couldn’t the CGM’s completeness and syntax check + accreditation allow for the basis to check the data?<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This list should not be a step by step, so the order doesn’t really matter – just have to follow steps in a way the
individual CP feels is appropriate<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Still receive requests that state “give me the data b/c I have a trademark” – if that is the basis of the request,
can’t look if there is personal data b/c do not believe that is an appropriate legal basis.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If the CP denies the request on some grounds unrelated to the fact that it is non-personal data when the data does
not pertain to a natural person is unacceptable.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Just heard that a request could be rejected before it’s assessed if there is personal data or not<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">It is not just about what is lawful and what is not. A request can be rejected b/c it was filed improperly. If requestors
submit the requests properly, this will not be an issue.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Offered a cure for the problem of legal v. natural – would involve a thorough validation of legal entities – some sort
of accreditation that demonstrates existence a company that would be globally applicable<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Consider adding – assuming the request is full and complete<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Alan Woods to provide example text<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 23:
</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Delete “without reviewing the underlying data”</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Moving step 7 up materially changes the recommendation. The threshold determination in 5 no longer makes sense.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">These are steps that each CP must perform, but there is no requirement that they must be performed in this exact order.<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 24</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">:
<span style="color:black">Can the EPDP team please explain what is the purpose of making a threshold determination? The paragraph used to require a Contracted Party to “make a threshold determination without reviewing the underlying data.” Paragraph 5a) no
longer includes this language. Further, Paragraph 7 no longer indicates whether the registration data ought to be evaluated together with the request, rather it only requires the Contracted Party to “evaluate the request.” It is unclear how Paragraphs 5a)
and 7 are distinct. Can the EPDP team please clarify? Paragraph 7: ICANN org notes that there do not appear to be any mandatory requirements specifying what it means to “evaluate the request.” Accordingly, ICANN Contractual Compliance would only be able to
assess whether the CP has conducted “an evaluation”. Can the EPDP team please confirm there are no mandatory requirements specified for this evaluation?</span><o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">First issue – if you delete “without reviewing underlying data” – confused about what the threshold determination is.
What is the difference b/w this and evaluate? Thought steps were implied that go in a certain order.
<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-left:.5in;mso-list:l3 level1 lfo2"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Since legal v. natural will not be addressed in Phase 2, the language in the Final Report may need to change.
<o:p></o:p></span></li></ul>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:1.0in;margin-bottom:.0001pt">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:.25in;margin-bottom:.0001pt;mso-list:l0 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">EPDP Team feedback<o:p></o:p></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:.25in;margin-bottom:.0001pt;mso-list:l0 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Confirm next steps<o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin-left:.95in;margin-bottom:.0001pt;text-indent:-50.0pt;mso-list:l1 level1 lfo1">
<![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><span style="mso-list:Ignore">5.<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Wrap and confirm next EPDP Team meeting (5 minutes):<o:p></o:p></span></p>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoNormal" style="margin-left:.25in;mso-list:l4 level1 lfo4"><span style="font-size:11.0pt;color:black">Thursday 18 June
</span><span style="font-size:11.0pt">at 14.00 UTC. Topics to be addressed: continue run through of yellow items.<o:p></o:p></span></li><li class="MsoNormal" style="margin-left:.25in;mso-list:l4 level1 lfo4"><span style="font-size:11.0pt;color:black">Confirm action items</span><span style="font-size:11.0pt"><o:p></o:p></span></li></ol>
<ol style="margin-top:0in" start="1" type="a">
<li class="MsoNormal" style="margin-left:.25in;mso-list:l2 level1 lfo5"><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></li></ol>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Times New Roman",serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p>
</div>
</body>
</html>