<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Brian, <br>
</p>
<p>you seem to be under a fundamental misunderstanding about the
concepts of the balancing test and decision-making as the decision
whether to disclose the data is the fundamental decision about the
data of the data subject in this case. I thought this would be
understood by all and therefore would not need mentioning. <br>
</p>
<p>Automated decision making about how to handle the data and
therefore the decision whether to disclose fundamentally affects
the rights of the data subject.</p>
<p>Best,</p>
<p>Volker<br>
</p>
<div class="moz-cite-prefix">Am 24.09.2019 um 00:36 schrieb King,
Brian via Gnso-epdp-team:<br>
</div>
<blockquote type="cite"
cite="mid:BY5PR10MB43387A6EF0983E09332CB3B39F850@BY5PR10MB4338.namprd10.prod.outlook.com">
<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:"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:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle20
{mso-style-type:personal-reply;
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;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hi all,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">It seems that we are mixing up a couple
concepts that require clarification in order for this
conversation to be more productive.
<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">First, the concept of automated
decision-making should be clarified. As discussed in the Bird
& Bird memo, the concept of automated decision-making is
limited to decisions about the data subject (not decisions
about whether to disclose their data). The types of decisions
about the data subject protected by GDPR include decisions
carrying the legal significance of denial of child or housing
benefit or refused admission to a country or denial of
citizenship. It’s necessary to clarify here that while the
third parties who request and might process this data need be
cautious about their own automated decision-making when using
the requested data, the decision about whether to disclose the
data itself is not Article 22 decision-making.
<o:p></o:p></p>
<p class="MsoNormal">
<o:p></o:p></p>
<p class="MsoNormal">Then, the section of the Bird & Bird
memo that Ayden references describes requirements if the types
of decision-making spelled out above is explicitly authorized
by national law. Those provisions are irrelevant to our work
for two reasons: 1) again, the disclosure decision is not the
type of legally significant decision-making that Article 22 is
intended to prevent, and 2) even if it were, the disclosure
decisions we’re talking about are grounded in 6.1.f or some
other 6.1. basis and not on the basis of a national law
permitting such decision-making. <o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;color:black" lang="EN-GB">Brian J.
King
</span></b><span style="font-size:10.0pt;color:black"
lang="EN-GB"> <br>
Director of Internet Policy and Industry Affairs<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:black"
lang="EN-GB"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:black"
lang="EN-GB">T +1 443 761 3726</span><u><span
style="font-size:10.0pt;color:#0563C1"><a
href="http://www.markmonitor.com" moz-do-not-send="true"><span
style="color:#0563C1" lang="EN-GB"><br>
</span><span style="color:#0563C1">markmonitor.com</span></a></span></u><span
style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;color:black" lang="EN-GB">MarkMonitor<br>
</span></b><span style="font-size:10.0pt;color:black"
lang="EN-GB">Protecting companies and consumers in a digital
world<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><b>From:</b> Gnso-epdp-team
<a class="moz-txt-link-rfc2396E" href="mailto:gnso-epdp-team-bounces@icann.org"><gnso-epdp-team-bounces@icann.org></a>
<b>On Behalf Of </b>Ayden Férdeline<br>
<b>Sent:</b> Monday, September 23, 2019 2:40 PM<br>
<b>To:</b> Greg Aaron <a class="moz-txt-link-rfc2396E" href="mailto:greg@illumintel.com"><greg@illumintel.com></a><br>
<b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:gnso-epdp-team@icann.org">gnso-epdp-team@icann.org</a><br>
<b>Subject:</b> Re: [Gnso-epdp-team] Proposed agenda - EPDP
Team meeting #20 on Tuesday 24 September at 14.00 UTC<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Greg,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I believe the existing legal advice,
contained in Bird & Bird's legal memo of 10 September
2019 (question 3), supports the need for natural persons to
have a right to object to data processing activities.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">On page 10 of the memo Bird & Bird
advised, <i>"The initial and annual notice and opt-out
process suggested by the EPDP would not be sufficient: an
individual would be given general notice that an automated
process may be used, but would not know that a decision
has actually been taken on this basis and, unless an
individual was aware of this, he or she would not be in a
positon to take advantage of the safeguards required by
the GDPR."</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">They also advised (same page):<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><i>"... safeguards require the controller
to notify the data subject as soon as possible that a
decision has been taken, at which point the data subject
has up to one month to require the controller to
reconsider the decision, with significant operational
implications for any urgent requests."</i><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I still need to consult with NCSG
colleagues regarding the language that I proposed, but I
believe any building block k language that does not ensure
there are mechanisms in place that allow registrants to
exercise their rights under the GDPR would be unacceptable
to us.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Ayden<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">On Monday, 23 September 2019 18:10, Greg
Aaron <<a href="mailto:greg@illumintel.com"
moz-do-not-send="true">greg@illumintel.com</a>> wrote:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p>Adyen’s proposal has major flaws, and IMHO is a
non-starter.<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>One: it does not propose a deadline for the
registry/registrar to provide any substantive response,
i.e. the data or a denial. Instead, it seems to allow
contracted parties to not provide a substantive response
for sixteen days, and maybe more. That sets a very long
response floor and expectation for the entire gTLD world.
The effective result will be: no flow of data.<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>Two: as we discussed in Los Angeles, we are trying to
automate what can be automated, including automated
decision-making where it is possible. For anything that
is automated, an ACK letter is not necessary -- instead
the data (or a 6(1)f denial) should just come back in
reply. That would leverage RDAP, which is a goal of
ours. See also the TSG paper.<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>Three: a written ACK is appropriate for requests that are
made offline, outside the system. Even then, an
acknowledgement of receipt can be issued automatically and
immediately by the contracting party (with a tracking
number). That’s SOP for any system that requires the
tracking of submissions, and most registrars already do it
with customer service tickets. <o:p></o:p></p>
<p> <o:p></o:p></p>
<p>Four: the proposal assumes that data subjects must be
informed every time a request for their data comes in, and
that data subjects have the right to decline the
processing. The GDPR does not require either of
those. Instead, GDPR requires that the data subject be
made aware before of the processing that may happen, and
who generally the recipients may be. Appropriately, the
Temp Spec already covers this – it requires registrars to
notify their registrants of the specific purposes for
which their data will be processed, and potential
recipients, so case-based notification is not required.
(Temp Spec, Section 7.) If the policy needs to be more
specific and tell registrants that they are subject to
GDPR Article 6 disclosures, then we should make that
happen. Unfortunately Adyen’s proposal builds in a way
for data subjects to hide their criminal activity and
cover their tracks. That is not necessary under the law,
and it is contrary to the GDPR’s intent. SSAC provided
the legal-sub team with draft questions about these topics
in the last submission round, and hopefully those will go
to Bird & Bird soon.<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>All best,<o:p></o:p></p>
<p>--Greg<o:p></o:p></p>
<p> <o:p></o:p></p>
<p> <o:p></o:p></p>
<p> <o:p></o:p></p>
<div>
<p class="MsoNormal"><b>From:</b> Gnso-epdp-team <<a
href="mailto:gnso-epdp-team-bounces@icann.org"
moz-do-not-send="true">gnso-epdp-team-bounces@icann.org</a>>
<b>On Behalf Of </b>Ayden Férdeline<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b>Sent:</b> Sunday, September 22,
2019 7:06 PM<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b>To:</b> Alex Deacon <<a
href="mailto:alex@colevalleyconsulting.com"
moz-do-not-send="true">alex@colevalleyconsulting.com</a>><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b>Cc:</b> <a
href="mailto:gnso-epdp-team@icann.org"
moz-do-not-send="true">gnso-epdp-team@icann.org</a><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b>Subject:</b> Re: [Gnso-epdp-team]
Proposed agenda - EPDP Team meeting #20 on Tuesday 24
September at 14.00 UTC<o:p></o:p></p>
</div>
<p> <o:p></o:p></p>
<div>
<p>Hi Alex,<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>I envision this being some form of written
communication (most likely an email) that lets the SSAD
requestor know that their request has been successfully
received and is being processed. I also imagine it
containing a copy of their request.<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>Thanks,<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>Ayden <o:p></o:p></p>
</div>
<div>
<div>
<p> <o:p></o:p></p>
</div>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<o:p></o:p></p>
</div>
<div>
<p>On Sunday, 22 September 2019 22:45, Alex Deacon <<a
href="mailto:alex@colevalleyconsulting.com"
moz-do-not-send="true">alex@colevalleyconsulting.com</a>>
wrote:<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p>Ayden, <o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>Can you describe what form this "Receipt
Acknowledgement Letter" would take? <o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>Alex<o:p></o:p></p>
</div>
<div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<div>
<div>
<div>
<p>___________<o:p></o:p></p>
</div>
<div>
<p><b>Alex Deacon</b><o:p></o:p></p>
</div>
<div>
<p>Cole Valley Consulting<o:p></o:p></p>
</div>
<div>
<p><a
href="mailto:alex@colevalleyconsulting.com"
target="_blank" moz-do-not-send="true">alex@colevalleyconsulting.com</a><o:p></o:p></p>
</div>
<div>
<p>+1.415.488.6009<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
</div>
</div>
</div>
<div>
<p> <o:p></o:p></p>
</div>
</div>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<div>
<p>On Sat, Sep 21, 2019 at 11:41 AM Ayden Férdeline
<<a href="mailto:icann@ferdeline.com"
moz-do-not-send="true">icann@ferdeline.com</a>>
wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC
1.0pt;padding:0in 0in 0in
6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<p>Hi,<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>Regarding building block k, I have alternate
language that I would like to table for
consideration please.<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p><u>The language circulated in the below email is:</u><o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<p><b>Building Block k) </b><i>(Receipt of
acknowledgement)</i><o:p></o:p></p>
<p><span style="font-family:"Times New
Roman",serif">The EPDP Team recommends that,
consistent with the EPDP Phase 1 recommendations,
the response time for acknowledging receipt of a
SSAD request should be without undue delay, but
not more than two (2) business days from receipt,
unless shown circumstances does not make this
possible.</span><o:p></o:p></p>
<p><span style="font-family:"Times New
Roman",serif">The response should also
include information about the subsequent steps as
well as the timeline consistent with the
recommendations outlined below.</span><o:p></o:p></p>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p><u>Proposed new language (changes in red):</u><o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<p><b>Building Block k) </b><i>(<u><span
style="color:red">A</span></u>cknowledgement<u><span
style="color:red"> of request</span></u>)</i><o:p></o:p></p>
<p>The EPDP Team recommends that <u><span
style="color:red">upon receipt of an SSAD
request, the receiving entity shall issue a
Receipt Acknowledgement Letter which summarizes
the applicant’s requests. This should happen
without undue delay and, ideally, within two
business days of the request being received by
the receiving entity. This response shall
include information about the subsequent steps
to be taken as well as a timeline for its
processing. Following the issuance of the
Receipt Acknowledgement Letter, the applicant
shall have a fourteen-calendar-day period within
which it may make certain types of corrections
to its request. This is to permit the applicant
to correct data entry errors, change contact
information, and to withdraw the request if it
is no longer required. Similarly, the receiving
entity of the request shall inform the data
subject(s) whose personal information is sought,
unless prohibited to make such a disclosure by
law, and provide the data subject with a
reasonable window of time and the opportunity
within which they may object to their data being
processed.</span></u><o:p></o:p></p>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>Kind regards,<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<div>
<div>
<p>Ayden Férdeline<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
</div>
<div>
<p> <o:p></o:p></p>
</div>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐<o:p></o:p></p>
</div>
<div>
<p>On Saturday, 21 September 2019 02:19, Marika
Konings <<a
href="mailto:marika.konings@icann.org"
target="_blank" moz-do-not-send="true">marika.konings@icann.org</a>>
wrote:<o:p></o:p></p>
</div>
<div>
<p> <o:p></o:p></p>
</div>
<blockquote
style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p>Dear EPDP Team,<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>Please find attached the proposed agenda for
the next EPDP Team meeting which is scheduled
for Tuesday 24 September at 14.00 UTC. To
facilitate your preparation, please review the
attached documents which include in addition to
the relevant section from the zero draft, the
relevant section from the SSAD worksheet that
contains information in relation to the
objective of addressing the topic as well as
materials to review.<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>Best regards,<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>Caitlin, Berry and Marika<o:p></o:p></p>
<p> <o:p></o:p></p>
<p>===========<o:p></o:p></p>
<p> <o:p></o:p></p>
<p><b><span style="color:black">EPDP Phase 2 -
Meeting #20</span></b><o:p></o:p></p>
<p><b><span style="color:black">Proposed Agenda</span></b><o:p></o:p></p>
<p><span style="color:black">Tuesday, 24 September
2019 at 14.00 UTC</span><o:p></o:p></p>
<p><span style="color:black"> </span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:67.7pt;margin-bottom:.0001pt"><span
style="color:black">1.</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Roll Call &
SOI Updates (5 minutes)</span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:67.7pt;margin-bottom:.0001pt"><span
style="color:black"> </span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:67.7pt;margin-bottom:.0001pt"><span
style="color:black">2.</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Confirmation of
agenda (Chair)</span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:67.7pt;margin-bottom:.0001pt"><span
style="color:black"> </span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:67.7pt;margin-bottom:.0001pt"><span
style="color:black">3.</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Welcome and
housekeeping issues (Chair) (5 minutes)</span><o:p></o:p></p>
<p style="margin-left:1.0in">a)<span
style="font-size:7.0pt;font-family:"Times
New Roman",serif">
</span><span style="color:black">Reminder - the
EPDP Team members to populate the contents of
the lawful basis table <b>by Wednesday 25
September
</b>(see </span><a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1U9jt9nOHs9QMjWTDl7UPaT-2D-2D-25099aD2lHZI_edit&d=DwMGaQ&c=OGmtg_3SI10Cogwk-ShFiw&r=qQNCXqU_XE2XIdXbawYmk-YDflYH6pd8ffXlzxU37OA&m=X14udqL03ET9WHiBXsNzWXmbi78EqiJHd1J3CmTF6Hs&s=Kt8K3nGmOOIpxKvVSFee5y-kLOb-WuCAgN8iZLbhIA0&e="
target="_blank" moz-do-not-send="true">https://docs.google.com/document/d/1U9jt9nOHs9QMjWTDl7UPaT--
9aD2lHZI/edit</a><span style="color:black">)</span><o:p></o:p></p>
<p style="margin-left:1.0in"><span
style="color:black">b)</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Reminder -
submit alternate form if members are not
attending the Jan 2020 F2F meeting</span><o:p></o:p></p>
<p><span style="color:black"> </span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:68.1pt;margin-bottom:.0001pt"><span
style="color:black">4.</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Acceptable Use
Policy (Building block d & h) – first
reading (30 minutes).</span><o:p></o:p></p>
<p style="margin-left:1.0in"><span
style="color:black">a)</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Initial
discussion</span><o:p></o:p></p>
<p style="margin-left:1.0in"><span
style="color:black">b)</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Feedback from
EPDP Team</span><o:p></o:p></p>
<p style="margin-left:1.0in"><span
style="color:black">c)</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Confirm next
steps </span><o:p></o:p></p>
<p style="margin-left:1.0in"><span
style="color:black"> </span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:68.1pt;margin-bottom:.0001pt"><span
style="color:black">5.</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Receipt of
acknowledgement (building block k) – first
reading (30 minutes)</span><o:p></o:p></p>
<p style="margin-left:1.0in"><span
style="color:black">a)</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Initial
discussion</span><o:p></o:p></p>
<p style="margin-left:1.0in"><span
style="color:black">b)</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Feedback from
EPDP Team</span><o:p></o:p></p>
<p style="margin-left:1.0in"><span
style="color:black">c)</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Confirm next
steps </span><o:p></o:p></p>
<p style="margin-left:1.0in"><span
style="color:black"> </span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:68.1pt;margin-bottom:.0001pt"><span
style="color:black">6.</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Who should be
responsible for disclosure decision (15
minutes)</span><o:p></o:p></p>
<p style="margin-left:1.0in"><span
style="color:black">a)</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Review
additional team input provided (see </span>
<a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_10VRZRziGDXvckC-5Fy3ob-5FSGB-2D1NN9WrL6Y6A3XQuniv8_edit&d=DwMGaQ&c=OGmtg_3SI10Cogwk-ShFiw&r=qQNCXqU_XE2XIdXbawYmk-YDflYH6pd8ffXlzxU37OA&m=X14udqL03ET9WHiBXsNzWXmbi78EqiJHd1J3CmTF6Hs&s=v6JLhdSt_Hruy8Hx7Z7EnRQbk2oWBXc_BWbgVZtxqoo&e="
target="_blank" moz-do-not-send="true">https://docs.google.com/document/d/10VRZRziGDXvckC_y3ob_SGB-1NN9WrL6Y6A3XQuniv8/edit</a><span
style="color:black">) </span><o:p></o:p></p>
<p style="margin-left:1.0in"><span
style="color:black">b)</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Consider team
input and approach forward</span><o:p></o:p></p>
<p style="margin-left:1.0in"><span
style="color:black">c)</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Confirm next
steps</span><o:p></o:p></p>
<p><span style="color:black"> </span><o:p></o:p></p>
<p
style="mso-margin-top-alt:5.0pt;margin-right:0in;margin-bottom:0in;margin-left:68.1pt;margin-bottom:.0001pt"><span
style="color:black">7.</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Wrap and
confirm next EPDP Team meeting (5 minutes):</span><o:p></o:p></p>
<p style="margin-left:1.5in"><span
style="color:black">a)</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Thursday 26
September 2019 at 14.00 UTC</span><o:p></o:p></p>
<p style="margin-left:1.0in"><span
style="color:black">b)</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Confirm action
items</span><o:p></o:p></p>
<p style="margin-left:1.0in"><span
style="color:black">c)</span><span
style="font-size:7.0pt;font-family:"Times
New Roman",serif;color:black">
</span><span style="color:black">Confirm
questions for ICANN Org, if any</span><o:p></o:p></p>
<p> <o:p></o:p></p>
<p><b><i><span
style="font-size:10.0pt;color:black">Marika
Konings</span></i></b><o:p></o:p></p>
<p><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><o:p></o:p></p>
<p><i><span style="font-size:10.0pt;color:black">Email: <a
href="mailto:marika.konings@icann.org"
target="_blank" moz-do-not-send="true"><span
style="color:#0563C1">marika.konings@icann.org</span></a> </span></i><o:p></o:p></p>
<p><i><span style="font-size:10.0pt;color:black"> </span></i><o:p></o:p></p>
<p><i><span style="font-size:10.0pt;color:black">Follow
the GNSO via Twitter @ICANN_GNSO</span></i><o:p></o:p></p>
<p><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="
target="_blank" moz-do-not-send="true"><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="
target="_blank" moz-do-not-send="true"><span
style="color:#0563C1">GNSO Newcomer
pages</span></a>. </span></i><o:p></o:p></p>
<p> <o:p></o:p></p>
</div>
</blockquote>
<div>
<p> <o:p></o:p></p>
</div>
<div>
<p>_______________________________________________<o:p></o:p></p>
</div>
<div>
<p>Gnso-epdp-team mailing list<o:p></o:p></p>
</div>
<div>
<p><a href="mailto:Gnso-epdp-team@icann.org"
target="_blank" moz-do-not-send="true">Gnso-epdp-team@icann.org</a><o:p></o:p></p>
</div>
<div>
<p><a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__mm.icann.org_mailman_listinfo_gnso-2Depdp-2Dteam&d=DwMGaQ&c=OGmtg_3SI10Cogwk-ShFiw&r=qQNCXqU_XE2XIdXbawYmk-YDflYH6pd8ffXlzxU37OA&m=X14udqL03ET9WHiBXsNzWXmbi78EqiJHd1J3CmTF6Hs&s=lvOCLjofgKkBFNMYjp3LmStd_aTFtj2Us5eQluWJSVI&e="
target="_blank" moz-do-not-send="true">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a><o:p></o:p></p>
</div>
<div>
<p>_______________________________________________<o:p></o:p></p>
</div>
<div>
<p>By submitting your personal data, you consent to
the processing of your personal data for purposes
of subscribing to this mailing list accordance
with the ICANN Privacy Policy (<a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_policy&d=DwMGaQ&c=OGmtg_3SI10Cogwk-ShFiw&r=qQNCXqU_XE2XIdXbawYmk-YDflYH6pd8ffXlzxU37OA&m=X14udqL03ET9WHiBXsNzWXmbi78EqiJHd1J3CmTF6Hs&s=3DZDjBGkOKP7XI4Pi7YqohFX1I8ToC05JxZ0C7Vbzmc&e="
target="_blank" moz-do-not-send="true">https://www.icann.org/privacy/policy</a>)
and the website Terms of Service (<a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_privacy_tos&d=DwMGaQ&c=OGmtg_3SI10Cogwk-ShFiw&r=qQNCXqU_XE2XIdXbawYmk-YDflYH6pd8ffXlzxU37OA&m=X14udqL03ET9WHiBXsNzWXmbi78EqiJHd1J3CmTF6Hs&s=yt2dDOp7-cys530sDAKGx4RO8sDCWwtzPt2WX8glR8c&e="
target="_blank" moz-do-not-send="true">https://www.icann.org/privacy/tos</a>).
You can visit the Mailman link above to change
your membership status or configuration, including
unsubscribing, setting digest-style delivery or
disabling delivery altogether (e.g., for a
vacation), and so on.<o:p></o:p></p>
</div>
</blockquote>
</div>
</blockquote>
<div>
<p> <o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Gnso-epdp-team mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gnso-epdp-team@icann.org">Gnso-epdp-team@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/gnso-epdp-team">https://mm.icann.org/mailman/listinfo/gnso-epdp-team</a>
_______________________________________________
By submitting your personal data, you consent to the processing of your personal data for purposes of subscribing to this mailing list accordance with the ICANN Privacy Policy (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/policy">https://www.icann.org/privacy/policy</a>) and the website Terms of Service (<a class="moz-txt-link-freetext" href="https://www.icann.org/privacy/tos">https://www.icann.org/privacy/tos</a>). You can visit the Mailman link above to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on.</pre>
</blockquote>
<div class="moz-signature">-- <br>
Volker A. Greimann<br>
General Counsel and Policy Manager<br>
<strong style="border-bottom: 3px solid #5C46B5">KEY-SYSTEMS GMBH</strong><br>
<br>
T: +49 6894 9396901<br>
M: +49 6894 9396851<br>
F: +49 6894 9396851<br>
W: <a class="moz-txt-link-abbreviated" href="http://www.key-systems.net">www.key-systems.net</a><br>
<br>
Key-Systems GmbH is a company registered at the local court of
Saarbruecken, Germany with the registration no. HR B 18835<br>
CEO: Alexander Siffrin<br>
<br>
Part of the CentralNic Group PLC (LON: CNIC) a company registered
in England and Wales with company number 8576358.</div>
</body>
</html>