<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Dear Heather -</div><div>I haven't seen any legal justification for the separation between the Temporary and the Consensus Period.</div><div>I would have to check but I believe the first GDPR review is in two years, insofar it would at least make sense to align the PDP with these 2 years.</div><div><br></div><div>Kind regards,</div><div>Erika </div><div><br><div>Sent from my iPhone</div></div><div><br>On Jun 4, 2018, at 2:47 AM, Heather Forrest <<a href="mailto:haforrestesq@gmail.com">haforrestesq@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">Colleagues,<div><br></div><div>Donna, Rafik and I met with Marika to review and structure the questions submitted to the Google doc for our upcoming call with the Board on next steps on the Temporary Specification. In doing so, we have merged our questions with overarching questions from the Board. </div><div><br></div><div>Please review the below to make sure that they make sense and capture your Google doc contributions faithfully. We're short on time, and need to circulate these to the Board with as much advance time as possible, so may I please suggest a 24 hour turnaround for any requested edits?</div><div><br></div><div>Many thanks and best wishes,</div><div><br></div><div>Heather</div><div><br></div><div><br></div><div><br></div><div>
<p class="MsoNormal" align="center" style="margin:0cm 0cm 0.0001pt;text-align:center;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-size:12pt;color:black">Board-GNSO
Council Discussion<span></span></span></b></p>
<p class="MsoNormal" align="center" style="margin:0cm 0cm 0.0001pt;text-align:center;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-size:12pt;color:black">Next
steps following Board adoption of Temporary Specification<span></span></span></b></p>
<p class="MsoNormal" align="center" style="margin:0cm 0cm 0.0001pt;text-align:center;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-size:12pt;color:black"><span> </span></span></b></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-size:12pt;color:black"><span> </span></span></b></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-size:12pt;color:black">Purpose of call: </span></b><span style="font-size:12pt;color:black">Identify which of the below questions can be answered by the GNSO
Council, which can be answered by ICANN Board, and which require advice of
ICANN Legal.<span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-size:12pt;color:black"><br>
SCOPE: <span></span></span></b></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black"><span> </span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(1) how to evolve the Temp Spec, " as is” , into a consensus
policy, <span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(2) how to handle/incorporate possible changes to the Temp Spec
that could result from resolving the outstanding items in the Annex to the Temp
Spec, and <span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(3) other changes required to achieve consensus.<span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black"><span> </span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-size:12pt;color:black">Questions from GNSO Council:<span></span></span></b></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(4) What is the intent of the EPDP? Is it simply to confirm the
Temporary Specification, or something more? What room is there in scoping to
anticipate that the EPDP may conclude that the Temporary Specification cannot
be confirmed “as is”, and make changes in order to achieve consensus
policy?<span> </span><span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(5) The Temporary Specification reasoning for including WHOIS as a
security and stability issue is based on the new ICANN Bylaws; at time of
contract signing, that wasn’t the case. Doesn’t that open a possible avenue to
challenge it altogether? Wouldn’t phasing the EPDP allowing a quick Consensus
Policy made of uncontroversial parts of the Temp Spec increase the assurances
that this wouldn’t hamper ICANN Org’s compliance ability?<span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(6) What happens should the Board decide to either modify the
Temporary Specification or completely replace the temporary specification by a
new one at a later point in time? Does this change the scope of the ongoing
EPDP (note: Council does not intend to run multiple EPDPs simultaneously), and
if so, how is the EPDP expected to deal with such changes while it may be half
way through its process? <span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(7) Section 8.2 of the Temporary Specification states that
implementation details of the Temporary Specification may be modified by a 2/3
vote of the ICANN Board. If such a circumstance occurs, what is the Board’s
opinion regarding how such changes would impact the EPDP?<span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(8) The Temporary Specification covers a number of additional
policies that go beyond the requirements of the RA and RAA as they relate to
Registration Data Directory Services. How does the Board believe the GNSO
Council should handle these areas of overlap?<span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(9) Does ICANN have/will ICANN develop a list of policies and
contractual clauses that are impacted by the temporary specification (beyond
what is currently identified in the Annex)? This would help with scoping the
work.<span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;vertical-align:baseline;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(10) What happens if the GNSO is not
able to reach consensus at the end of the 1 year period? (see also Timing)<span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;vertical-align:baseline;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(11) How does the Board expect the EPDP
to follow and/or to incorporate ICANN´s ongoing legal strategy and the
decisions of EU country courts?<span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;vertical-align:baseline;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(12) As evidenced by the recent legal
action involving EPAG, there are parties who believe aspects of the Temporary
Specification as written are not compliant with the GDPR. How does the Board
think the GNSO Council should approach this matter when structuring and scoping
the PDP?<span></span></span></p><p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;vertical-align:baseline;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black"><br></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-size:12pt;color:black">TIMING:<span></span></span></b></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black"><span> </span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(1) Under the Bylaws, which date is considered as the start of the
EPDP: 17 May (when the resolution was adopted), 26 May (when the Temp Spec came
into effect), or a date chosen by the GNSO Council, <span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(2) Will every future change to the Temp Spec be considered as an
additional Temp Spec that requires an additional EPDP, and <span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(3) What happens if the Temp Spec expires and the Consensus Policy
is not ready?<span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black"><span> </span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-size:12pt;color:black">Questions from GNSO Council</span></b><span style="font-size:12pt;color:black">: <span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(4) Does the initial 90-day (and maximum one-year) period - and
thus the maximum timeline for the GNSO’s policy work - commence on 17 May (date
of Board resolution) or 25 May (effective date of the temporary specification)?
We note that the operative language from the RAA/RA specifies that “In
establishing any Temporary Policy, the Board shall state the period of time for
which the Temporary Policy is adopted and shall immediately implement the
Consensus Policy development process set forth in ICANN's Bylaws”, and the
Board resolution is clear that the specification is effective beginning on 25
May. This could be interpreted to mean that the one-year clock starts from the
effective date of the specification rather than Board action via resolution,
which is a difference of 8 days.<span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(5) What happens should the Board decide to either modify the
temporary specification or completely replace the temporary specification by a
new one at a later point in time? Does the amended temporary specification
become a new temporary specification, effectively re-starting the clock on the
Temp Spec and the ongoing EPDP? If changes to the Temporary Specification as it
is today are certain to occur, and the amended temporary specification becomes
a new temporary specification, why not delay starting the ePDP (assuming clock
re-starts)? Note Council’s intention is not running multiple EPDP, but rather
revising scope of the one ongoing EPDP.<span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;vertical-align:baseline;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(6) How is the re-confirmation
process expected to occur as the temporary policy is only valid for 90 day
intervals? <span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;vertical-align:baseline;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(7) Has the Board considered what
actions it may take in the event that, at the end of the one-year period, the
Temporary Specification is not confirmed as a Consensus Policy and no other
Consensus Policy has been developed to replace it?<span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black"><span> </span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black"><span> </span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-size:12pt;color:black">PARTICIPATION OF OTHER STAKEHOLDERS
IN THE EPDP:<span></span></span></b></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black"><span> </span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(1) Participation of the GAC: How will the EPDP take into account GAC
advice? Should the Board facilitate a session between the GNSO and the GAC on
this issue, and when?<span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(2) Participation of other stakeholders in the EPDP?<span> </span><span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black"><span> </span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><b><span style="font-size:12pt;color:black">Questions from the GNSO Council:<span></span></span></b></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black">(3) What is the Board's expectation with regard to the Council's
ongoing communication with Board/involvement of Board during the scoping
process?<span></span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 0.0001pt;line-height:normal;font-size:11pt;font-family:Calibri,sans-serif"><span style="font-size:12pt;color:black"><span> </span></span></p>
<p class="MsoNormal" style="margin:0cm 0cm 8pt;line-height:107%;font-size:11pt;font-family:Calibri,sans-serif"><span> </span></p>
<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jun 1, 2018 at 3:57 AM, Marika Konings <span dir="ltr"><<a href="mailto:marika.konings@icann.org" target="_blank">marika.konings@icann.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="m_-5475126564359776525WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt">Reminder, please provide your input
<u>no later than tomorrow, Friday 1 June by 23.00 UTC</u> so that these questions can be shared with the ICANN Board ahead of the meeting that is planned for next Tuesday.
<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Best regards,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Marika<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="color:black">From: </span></b><span style="color:black">council <<a href="mailto:council-bounces@gnso.icann.org" target="_blank">council-bounces@gnso.icann.<wbr>org</a>> on behalf of Marika Konings <<a href="mailto:marika.konings@icann.org" target="_blank">marika.konings@icann.org</a>><br>
<b>Date: </b>Thursday, May 24, 2018 at 16:55<br>
<b>To: </b>"<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>" <<a href="mailto:council@gnso.icann.org" target="_blank">council@gnso.icann.org</a>><br>
<b>Subject: </b>[council] For your input - questions for the ICANN Board following the adoption of the temporary specification<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt"><u></u> <u></u></span></p>
</div>
<p class="MsoNormal"><span style="font-size:11.0pt">Dear All,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt">As discussed during the Council meeting earlier today, please include your input as well as that of your respective SG/C with regards to which questions / issues that should be discussed with the ICANN Board
following the adoption of the temporary policy specification in this google doc:
<a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1I5fyQTqYmcKft-2D4yiOKP6WMcCST0a1sZGtAY1jofAb4_edit-3Fusp-3Dsharing&d=DwMGaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=7_PQAir-9nJQ2uB2cWiTDDDo5Hfy5HL9rSTe65iXLVM&m=_LDSa4WNNNDS1qBTamfRZhtmu8GFTQF8LUge1_Z2xaU&s=ysjJgSENKPUrufQ3oIkeGU19KsIPUYGA5ZbwZ2j2sy8&e=" target="_blank">
https://docs.google.com/<wbr>document/d/1I5fyQTqYmcKft-<wbr>4yiOKP6WMcCST0a1sZGtAY1jofAb4/<wbr>edit?usp=sharing [docs.google.com]</a>. A number of initial questions that have come up in the various conversations have been included as a starting point.
</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Best regards,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt">Marika </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:11.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><i><span style="font-size:11.0pt">Marika Konings</span></i></b><u></u><u></u></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Vice President, Policy Development Support – GNSO, Internet Corporation for Assigned Names and Numbers (ICANN) </span></i><u></u><u></u></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Email: <a href="mailto:marika.konings@icann.org" target="_blank">
marika.konings@icann.org</a> </span></i><u></u><u></u></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt"> </span></i><u></u><u></u></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">Follow the GNSO via Twitter @ICANN_GNSO</span></i><u></u><u></u></p>
<p class="MsoNormal"><i><span style="font-size:11.0pt">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=_LDSa4WNNNDS1qBTamfRZhtmu8GFTQF8LUge1_Z2xaU&s=JbAIzF_PGZcEeBD8WceN7sjiCTQNnZxVV0JgkC_PQXc&e=" target="_blank">interactive
courses [learn.icann.org]</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=_LDSa4WNNNDS1qBTamfRZhtmu8GFTQF8LUge1_Z2xaU&s=C7GmV-QMuICNyJrCQtKXaP4r4W_06og6bMm3SzDjz2g&e=" target="_blank">GNSO
Newcomer pages [gnso.icann.org]</a>. </span></i><u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
</div>
<br>______________________________<wbr>_________________<br>
council mailing list<br>
<a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/council" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/council</a><br>
<br></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>council mailing list</span><br><span><a href="mailto:council@gnso.icann.org">council@gnso.icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/council">https://mm.icann.org/mailman/listinfo/council</a></span><br></div></blockquote></body></html>