<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:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
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:828835672;
mso-list-type:hybrid;
mso-list-template-ids:1108240908 287864966 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l3:level1
{mso-level-start-at:3;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:85.7pt;
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:121.7pt;
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:157.7pt;
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:193.7pt;
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:229.7pt;
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:265.7pt;
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:301.7pt;
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:337.7pt;
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:373.7pt;
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;}
@list l5
{mso-list-id:1765492681;
mso-list-type:hybrid;
mso-list-template-ids:297276188 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l5:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l5:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l5:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l5:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
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;font-family:"Calibri",sans-serif;color:black">Dear EPDP Team:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">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;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Marika, Berry, and Caitlin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">--<o:p></o:p></span></p>
<p class="MsoNormal"><b><u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p><span style="text-decoration:none"> </span></o:p></span></u></b></p>
<p class="MsoNormal"><b><u><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Action Items<o:p></o:p></span></u></b></p>
<ol start="1" type="1">
<li class="MsoListParagraph" style="color:black;mso-list:l5 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">EPDP Team members to review the
<a href="https://community.icann.org/display/EOTSFGRD/g.+Draft+Final+Report+-+Phase+2">
Recommendation Input Review tables</a> and provide further information in response to clarifying questions for the remaining yellow items (<b>beginning at Item 42 for Recommendation 9</b>) in advance of the next meeting on Tuesday, 23 June.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l5 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Brian and Matt S. to work together on an updated formulation of Rec. 7 (must vs. should, footnote 43), taking into account
the team’s discussion.<o:p></o:p></span></li><li class="MsoListParagraph" style="color:black;mso-list:l5 level1 lfo1"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Support Staff to update the draft final report in accordance with the agreements from today’s meeting.<o:p></o:p></span></li></ol>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">EPDP Phase 2 - Meeting #66</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Proposed Agenda</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Thursday 18 June 2020 at 14.00 UTC<o:p></o:p></span></p>
<p class="MsoNormal"><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 lfo2">
<![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 lfo2">
<![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 lfo2">
<![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>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="color:black;margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Propose discussing Rec. 6 at our next team and allow staff to rewrite the recommendation based on yesterday’s discussion<o:p></o:p></span></li></ul>
<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 lfo2">
<![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>
<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 lfo4">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">EPDP Team feedback<o:p></o:p></span></li></ol>
<ul style="margin-top:0in" type="disc">
<li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 35 </span>
</b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">– second paragraph in this recommendation: “<span style="color:black">The SSAD MUST allow for the automated disclosure of data in response to” – this update should be rejected as this may unnecessarily
limit the automation part of the recommendation. Can this go back to the original formulation?
</span><b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">We requested that we allow for centralized decisions not only automated decisions
<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Automated disclosure narrows the sentence – automated processing allows for more automation<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">As long as it’s clear that the SSAD will allow automated decisions
<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Would like to explicitly mention the disclosure of the data – perhaps say “allow for automation of the processing, including the automation of the disclosure of data”<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Everyone is OK with automating the receipt and processing requests, and now members are trying to shoehorn automated decision making here. This paragraph has no reason to be here because it is
dealt with in Recommendation 7. Either we stick with the original language or delete the paragraph; the current modification is unacceptable.<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Agreement to revert to the original formulation.<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Items 36</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> – in one of the previous meetings, we discussed this part of the recommendation extensively. The language
was originally SHOULD, and it was changed to MUST, but CPs were concerned about forced disclosure without any exemption. Footnote 43 outlines a process where CPs can notify ICANN Compliance when it believes is unable to automate the processing.<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">CPs have provided alternative language<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Can the Team agree up front that there will be automated decision making in limited circumstances (where technically, legally, and commercially feasible), and that this is fundamental to the report?<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There should be a way for CPs to put the brakes on if they cannot automate. Concerned about FN 43 to put the brakes on immediately, but there doesn’t seem to be the ability to assess if the brakes
were properly applied. This seems to be a one-way street – there needs to be more meat on this so that ICANN can assess whether the concern is justified. There is an imbalance here.<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">There should be a procedure where the impacted groups are able to weigh in if they are in agreement with what has been designated as automated no longer is in light of guidance – there needs to
be some kind of notice and comment process.</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Not comfortable with the use of the word “MUST” – need to use “SHOULD”. Data protection law is generally a risk management decision, so there will inevitably be different interpretations of what
is “legally permissible”. We all promote the concept of making this simple and inexpensive where feasible, but let’s not pretend that something is feasible when it’s not.</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">NCSG has moved far outside of its comfort zone – what would be the operational difference b/w must and should? Believe footnote 43 should be part of the main policy. Now, the concern is we are
kicking the football to implementation guidance and the mechanism outlined in Rec. 19. Before we accept this language, what is happening in Rec. 19? If there is an acceptable process for Rec. 19, we can accept this language. If Rec. 19 turns into an alternative
policy-making process, we cannot accept this.</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The team can provisionally agree on this rec before Rec. 19 – if there is no agreement on Rec. 19, we can revisit this language.</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Footnote 43 should be incorporated into the policy; footnotes should not have important text.</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">“Must automatically disclose data for any categories, subject to [caveat]” instead of “automatically process”.
</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From the RySG perspective, Rys had concerns with “should” to “must” and did not feel like the footnote language was sufficient to address the concerns. Rr suggestion is good here, in that they
leave in the MUST but as a balance, but they leave it to the CP to determine what is technically and commercially feasible and legally permissible. CPs reside in different jx, so where the CP makes this determination that must automatically process is OK –
strikes a good balance. It also allows for evolution.</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If CPs make the determination, there is no need for a footnote.</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">IPC cannot live with CP in its sole discretion to decide whether to automate. This would not be enforceable by ICANN compliance. Interested in working on this exception process and how this would
work.</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Proposal – maintain the text as is on the screen where CPs must automatically process and elevate FN 43 into the policy (rather than a FN).
</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">We have not done a DPIA despite certain parties screaming for it. In order for a CP to stop automate processing where they believe it is legally impermissible, they will have to do a DPIA. This
is not cost-free, and we do not have a proper scoping of this. </span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This should be a SHOULD and there should not a high bar for a CP to get out of this if they believe the processing is not technically or commercially feasible or legally permissible</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The change from SHOULD to MUST needs guardrails. If it is a must, the CP needs to make the decision.
</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Technically and commercially feasible may need to be treated separately. If this is a bilateral agreement b/w two parties, this could be discussed; however, with thousands of agreements, this is
unworkable. Technically and commercially feasible should be separated out.</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Rrs cannot have a process where the onus of proving that something is not legally permissible is on the Rr to prove. The DPIA needs to be done by ICANN. Just b/c something is legally impermissible
in one jx, that doesn’t mean it needs to be pushed through for all jx. This language needs a lot more work.</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The role of ICANN Compliance should be a check that this exemption request process is not being abused. This would be close to a rubber stamp process by Compliance – just to guard against abuse.</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 39 from ICANN org asks some of the questions the Team has been speaking.</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Some colleagues are still OK with automating based on what they believe is legally permissible. The language Rrs suggested allows CPs to make their own determination. This may result in more automation;
in some cases, it will result in less automation. It’s very hard to come up with a one-size-fits-all solution. While we have focused on GDPR, there are other laws that may be applicable.</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">No amount of guardrails or caveats can turn a should into a must if there are so many unknowns</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">What should the role of ICANN be? This refers to ICANN Compliance, and policy should probably refer to ICANN org instead of ICANN Compliance specifically as it’s not a foregone conclusion that
ICANN Compliance will handle this</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 40</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> – even for decisions where the central gateway may direct automated disclosure, there may be manual processing
at the central gateway, so there is some language added here – the CGM MAY request additional information to determine if the criteria for automated disclosure has been met.
</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Additional information may not be always be personal information</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Do not see the harm in allowing this and it gives flexibility for the future</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Why do we have this in if we cannot think of a concrete example? If it’s not clear to the CGM at the beginning, it doesn’t meet the criteria, and it should be manual.
</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Example – data previously disclosed – has this ever been disclosed before? If yes, it could be automated</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">The CGM makes determination on whether the criteria for automation has been met</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">What this is allowing is that the evolutionary mechanism may come up with new scenarios where the SSAD could disclose information – as CPs have pointed out repeatedly, Rrs are in many jx – some
may be in a position to release information to the SSAD. This just allows flexibility to future decisions.</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If we make sure that there is no transfer of personal data, that would be acceptable</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Limiting this to no personal data unnecessarily limits this</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 41</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> – GAC team requested an addition. RySG is asking for further context.</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Based on Chris L-E’s explanation, OK with the particular edit, but the B&B analysis did not take this into account but neither were a lot of other law enforcement requests. This edit is OK, but
there may be other problems. </span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">“or processing is to be carried out under an Article 2 exemption” – the or is ambiguous</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Chris to look at the sentence
</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">“applicable” doesn’t always mean it’s only law enforcement – some jx may be able to request data subject to contract or treaty, there are also Rrs are set up in multiple countries</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">“or” could go after jurisdictions “or where processing is to be carried out under Article 2</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">With either (i) local jx or (ii) confirmed article 2 exemption</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 42 – </span>
</b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Priority matrix should not be implementation guidance as there is text that is part of policy rec and part is implementation guidance. If the team agrees, which part should be in the policy
language? (also relevant in the context of rec. 19 b/c anything that is the policy rec. cannot be changed except through a PDP)</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">If it’s moved into the policy rec., we would be locked in place</span><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></b></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Policy rec could be such – initial rec is: [x] but this can be adjusted per the evolutionary model so it gives the flexibility that we intended to give.<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Understanding is that at the very least the numbers in the third column were initial numbers that could be changed in implementation without changing the policy.<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Item 43</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> – is this to be negotiations b/w ICANN org and CPs or are these policy requirements?
<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This may be tied to the Rec. 19 conversation.<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">When did the Team decide on one business day?
<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">This is still an open question as to what business day means.<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Recollection that we are still discussing business days.<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Team to provide input by the next meeting.
<b><o:p></o:p></b></span></li><li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:49.7pt;margin-bottom:.0001pt;mso-list:l3 level1 lfo3">
<span style="font-size:11.0pt;font-family:"Calibri",sans-serif">In the Google docs, if groups want to provide input on the clarifying questions on what has been flagged, please add this to the Google doc.
<b><o:p></o:p></b></span></li></ul>
<ol style="margin-top:0in" start="2" type="a">
<li class="MsoListParagraph" style="margin-top:0in;margin-bottom:0in;margin-left:.25in;margin-bottom:.0001pt;mso-list:l0 level1 lfo4">
<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"><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 lfo2">
<![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 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Monday, 22 June at 14:00 UTC – Small Team for Rec. 19</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoNormal" style="margin-left:.25in;mso-list:l4 level1 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Tuesday, 23 June at 14:00 UTC – continue run-through of yellow items</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li><li class="MsoNormal" style="margin-left:.25in;mso-list:l4 level1 lfo5"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Confirm action items</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><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 lfo6"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">Confirm questions for ICANN Org, if any</span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p></o:p></span></li></ol>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"><o:p> </o:p></span></p>
</div>
</body>
</html>