<div dir="ltr"><div class="gmail_extra">Hi Stephanie,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks,</div><div class="gmail_extra">if I am not mistaking the drafting group is tasked to provide a charter for a possible new IAG to handle the comments receive and see how to accommodate that with the previous implementation. so I guess the focus would be in term of the process here, the charter list 3 options. all are open compared to the previous IAG iteration. however, I would be concerned with CCWG and GNSO review models due to the question of representation from SG/C compared to an open model. the 2 first models have appointed representatives which may give a weight in term of decision-making. I have less concerns with Chair selection models, while I won't support IRT one with GDD manager as chair. </div><div class="gmail_extra">I don't see any specific concern with the mission and scope. </div><div class="gmail_extra"><br></div><div class="gmail_extra">Best,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Rafik</div><div class="gmail_extra"><br><div class="gmail_quote">2018-01-04 4:55 GMT+09:00 Stephanie Perrin <span dir="ltr"><<a href="mailto:stephanie.perrin@mail.utoronto.ca" target="_blank">stephanie.perrin@mail.utoronto.ca</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Hi folks, <br>
</p>
<p>I volunteered for the small drafting team at council who are
working on the development of a new charter for an Implementation
Advisory Group for the WHOIS conflicts with law. I was on the IAG
for the last trigger discussion, and submitted a dissenting
opinion. The DPAs declared this whole thing a nonsense, in their
last comments on the procedure. If you have any comments on this
procedure that you wish me to convey, please let me know....next
meeting is tomorrow.</p>
<p>Cheers Stephanie<br>
</p>
<div class="m_647816598875880141moz-forward-container"><br>
<br>
-------- Forwarded Message --------
<table class="m_647816598875880141moz-email-headers-table" border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">Subject:
</th>
<td>Re: Attendance and recording: GNSO Council Drafting Team
Charter ICANN Procedure for Handling Whois Conflicts
Monday 18 December 2017 at 20:00 UTC</td>
</tr>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">Date: </th>
<td>Wed, 3 Jan 2018 19:34:01 +0000</td>
</tr>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">From: </th>
<td>Marika Konings <a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:marika.konings@icann.org" target="_blank"><marika.konings@icann.org></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">To: </th>
<td>Steve Chan <a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:steve.chan@icann.org" target="_blank"><steve.chan@icann.org></a>, Nathalie
Peregrine <a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:nathalie.peregrine@icann.org" target="_blank"><nathalie.peregrine@icann.org></a><wbr>, Heather
Forrest <a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:haforrestesq@gmail.com" target="_blank"><haforrestesq@gmail.com></a>,
<a class="m_647816598875880141moz-txt-link-abbreviated" href="mailto:kdrazek@verisign.com" target="_blank">kdrazek@verisign.com</a> <a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:kdrazek@verisign.com" target="_blank"><kdrazek@verisign.com></a>,
icannlists <a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:icannlists@winston.com" target="_blank"><icannlists@winston.com></a>, Stephanie
Perrin <a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:stephanie.perrin@mail.utoronto.ca" target="_blank"><stephanie.perrin@mail.<wbr>utoronto.ca></a>, Michele
Blacknight <a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:michele@blacknight.com" target="_blank"><michele@blacknight.com></a>, Pam Little
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:pam.little@alibaba-inc.com" target="_blank"><pam.little@alibaba-inc.com></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap valign="BASELINE">CC: </th>
<td><a class="m_647816598875880141moz-txt-link-abbreviated" href="mailto:gnso-secs@icann.org" target="_blank">gnso-secs@icann.org</a> <a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:gnso-secs@icann.org" target="_blank"><gnso-secs@icann.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
<div class="m_647816598875880141WordSection1">
<p class="MsoNormal">Dear All,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Best wishes for 2018!<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">In preparation for tomorrow’s meeting,
please find below as a reminder the notes & action items
from the last meeting. Attached you will find the draft
charter as originally circulated. If you already have any
feedback / input from your respective groups that you would
like to share ahead of the meeting, please share with this
list.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Best regards,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Marika<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Steve Chan
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:steve.chan@icann.org" target="_blank"><steve.chan@icann.org></a><br>
<b>Date: </b>Monday, December 18, 2017 at 22:03<br>
<b>To: </b>Nathalie Peregrine
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:nathalie.peregrine@icann.org" target="_blank"><nathalie.peregrine@icann.org></a><wbr>, Heather Forrest
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:haforrestesq@gmail.com" target="_blank"><haforrestesq@gmail.com></a>, <a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:kdrazek@verisign.com" target="_blank">"kdrazek@verisign.com"</a>
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:kdrazek@verisign.com" target="_blank"><kdrazek@verisign.com></a>, icannlists
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:icannlists@winston.com" target="_blank"><icannlists@winston.com></a>, Stephanie Perrin
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:stephanie.perrin@mail.utoronto.ca" target="_blank"><stephanie.perrin@mail.<wbr>utoronto.ca></a>, Michele
Blacknight <a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:michele@blacknight.com" target="_blank"><michele@blacknight.com></a>, Pam Little
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:pam.little@alibaba-inc.com" target="_blank"><pam.little@alibaba-inc.com></a>, Marika Konings
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:marika.konings@icann.org" target="_blank"><marika.konings@icann.org></a><br>
<b>Cc: </b><a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:gnso-secs@icann.org" target="_blank">"gnso-secs@icann.org"</a>
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:gnso-secs@icann.org" target="_blank"><gnso-secs@icann.org></a><br>
<b>Subject: </b>Re: Attendance and recording: GNSO
Council Drafting Team Charter ICANN Procedure for Handling
Whois Conflicts Monday 18 December 2017 at 20:00 UTC<u></u><u></u></span></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt">Dear All,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Further,
please find some informal notes and actions items that staff
collected during the course of the meeting. The recording of
course is the authoritative record.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Best,</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Steve</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">----------------------</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt">GNSO Council Drafting Team <wbr>call to discuss the draft <wbr>Charter concerning ICANN <wbr>Procedure for Handling Whois <wbr>Conflicts on Monday 18 18 <wbr>December 2017 at 2000 UTC</span></b><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt"><br>
<br>
<br>
</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">Notes/Action Items:</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- Heather to serve as <wbr>facilitator/champion for this <wbr>process, but in a neutral way.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- Keith happy to hold pen <wbr>and can rely on Marc Anderson <wbr>for IAG context.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- What's process for the <wbr>draft charter? Staff role to <wbr>develop? What's available now <wbr>is the standard template with <wbr>key questions flagged and <wbr>possible options. Should <wbr>take care in drafting charter <wbr>as it could serve as <wbr>precedent for future review <wbr>efforts.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- The procedure is a matter <wbr>of implementation No standard <wbr>procedure for reviewing an <wbr>implementation of GNSO <wbr>adopted resolutions.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- Look forward to getting <wbr>input from Michele and <wbr>Stephanie.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- Discussion could begin on <wbr>this call, help ensure that <wbr>this effort does not repeat <wbr>inability to reach conclusion <wbr>the first go around.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- Keep scope and timeline <wbr>narrow</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- What's the current <wbr>situation? What is the <wbr>subsequent group expected to <wbr>accomplish? <b>Marika Konings: </b>th<wbr>e procedure has been updated <wbr>with a new trigger, per the <wbr>recommendations of the <wbr>previous IAG. </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- The recommendations of the <wbr>subsequent group would be in <wbr>reference to an already <wbr>implemented policy. The <wbr>recommendations would be <wbr>treated differently than a <wbr>PDP then,.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- Question: is the <wbr>implementation, or suggested <wbr>modifications, consistent <wbr>with the underlying policy <wbr>recommendations? Or is <wbr>additional policy work needed?</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- Most focus has been on the <wbr>trigger. Some review of the <wbr>subsequent steps after <wbr>triggering may be important.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- This process will help <wbr>provide guidance for the <wbr>future to understand roles of <wbr>community and staff.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- How does GDPR fit into <wbr>this exercise as it relates <wbr>to Whois? The current trigger <wbr>does seem to fit under GDPR, <wbr>but is an unattractive option.<wbr> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt"> -- There is GDPR-specific <wbr>relief (e.g., relief against <wbr>compliance). Problem of the <wbr>day.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt"> -- And there is relief <wbr>related to ANY local privacy <wbr>law, more generically. The <wbr>trigger(s) being explored are <wbr>not GDPR specific.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- The scope of this review, <wbr>is it just limited to <wbr>focusing on Whois? It seems <wbr>to be the case: <b>Marika <wbr>Konings: </b>From the underlying <wbr>policy recommendations: In <wbr>order to facilitate <wbr>reconciliation of any <wbr>conflicts between local/<wbr>national mandatory privacy <wbr>laws or regulations and <wbr>applicable provisions of the <wbr>ICANN contract regarding the <wbr>collection, display and <wbr>distribution of personal data <wbr>via Whois, ICANN should.......</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- The trigger of going to a <wbr>national regulator does not <wbr>seem to be working. Explore <wbr>an additional trigger(s) to <wbr>initiate waiver process.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- Is there evidence of the <wbr>trigger not working? Or are <wbr>CP just unwilling to write to <wbr>national regulators to ask if <wbr>they are violating local law? <wbr>It seems to require an <wbr>admission of guilt to get the <wbr>waiver.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- There is some interest in <wbr>reviewing the underlying the <wbr>policy, which would require a <wbr>different process. That might <wbr>be what has caused this topic <wbr>to linger on Council list.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- Public comment provides <wbr>possible issues with <wbr>alternative trigger. Seems to <wbr>imply that you must already <wbr>be in violation to utilize <wbr>waiver.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- Could limit the scope of <wbr>what is reviewed (e.g., the <wbr>public comment and Akram <wbr>letter). And also note that <wbr>if policy issues are <wbr>uncovered, that they would be <wbr>resolved through another <wbr>mechanism.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- Whatever recommendations <wbr>this IAG would put forth to <wbr>Council, the Council would <wbr>need to confirm that they are <wbr>not inconsistent with <wbr>underlying policy <wbr>recommendations.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- Could group also explore <wbr>other ideas beyond previous <wbr>IAG? Should avoid just <wbr>repeating the outcomes of <wbr>previous IAG.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- How to narrow scope? Start <wbr>with public comments? </span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt">Keith Drazek: </span></b><span style="font-size:10.0pt">(1) Review <wbr>current implementation; (2) <wbr>re-consider previous triggers <wbr>not agreed to; (3) consider <wbr>other possible triggers not <wbr>previously considered; (4) <wbr>review everything based on <wbr>existing public comments.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- Other areas of focus: <wbr>objectives and goals, <wbr>membership (seems like it <wbr>should include those outside <wbr>Council), chair selection (<wbr>could follow from group <wbr>composition), group formation,<wbr> dependencies, and <wbr>dissolution (also follow from <wbr>group/review team composition)<wbr>, decision-making (also <wbr>dependent).</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- Key questions are scope <wbr>and composition. Take these <wbr>to respective SG/Cs.</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- Agreement that composition <wbr>is paramount and drives many <wbr>other elements (chair, staff <wbr>support). Will the group <wbr>operate more like an IRT or <wbr>WG? Who serves as the lead (e.<wbr>g., staff or community)?</span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt">-- Hopefully table for <wbr>January meeting (20 Jan <wbr>document and motions deadline)<wbr>.</span><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt">ACTION: Take draft charter to <wbr>respective SG/Cs and convene <wbr>again in early January?</span></b><u></u><u></u></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt">ACTION: Set up Doodle for <wbr>early Jan or week of the 8th.</span></b><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt"> </span><u></u><u></u></p>
<p class="MsoNormal"><span style="font-size:10.0pt"> </span><u></u><u></u></p>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Nathalie Peregrine
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:nathalie.peregrine@icann.org" target="_blank"><nathalie.peregrine@icann.org></a><br>
<b>Date: </b>Monday, December 18, 2017 at 12:55 PM<br>
<b>To: </b>Heather Forrest
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:haforrestesq@gmail.com" target="_blank"><haforrestesq@gmail.com></a>, <a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:kdrazek@verisign.com" target="_blank">"kdrazek@verisign.com"</a>
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:kdrazek@verisign.com" target="_blank"><kdrazek@verisign.com></a>, icannlists
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:icannlists@winston.com" target="_blank"><icannlists@winston.com></a>, Stephanie Perrin
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:stephanie.perrin@mail.utoronto.ca" target="_blank"><stephanie.perrin@mail.<wbr>utoronto.ca></a>, Michele
Blacknight <a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:michele@blacknight.com" target="_blank"><michele@blacknight.com></a>, Pam Little
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:pam.little@alibaba-inc.com" target="_blank"><pam.little@alibaba-inc.com></a>, Marika Konings
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:marika.konings@icann.org" target="_blank"><marika.konings@icann.org></a>, Steve Chan
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:steve.chan@icann.org" target="_blank"><steve.chan@icann.org></a><br>
<b>Cc: </b><a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:gnso-secs@icann.org" target="_blank">"gnso-secs@icann.org"</a>
<a class="m_647816598875880141moz-txt-link-rfc2396E" href="mailto:gnso-secs@icann.org" target="_blank"><gnso-secs@icann.org></a><br>
<b>Subject: </b>Attendance and recording: GNSO Council
Drafting Team Charter ICANN Procedure for Handling Whois
Conflicts Monday 18 December 2017 at 20:00 UTC</span><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"> <u></u><u></u></p>
</div>
<p class="MsoNormal">Dear all, <u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal">Please find below the AC recording,
attendance and AC chat transcript of the GNSO Council Drafting
Team call to discuss the draft Charter concerning ICANN
Procedure for Handling Whois Conflicts scheduled on Monday 18
December 2017 at 20:00 UTC<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><b>AC Recording</b>: <a href="https://participate.icann.org/p2q6sp8ir36/?OWASP_CSRFTOKEN=da98784bd396b38e57f1d982b189a0a8f647aa1f7e8f2c7c1c2566602aaf4d91" target="_blank">https://participate.icann.org/<wbr>p2q6sp8ir36/</a><u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><b>Attendance:</b> Pam Little, Keith
Drazek, Heather Forrest, Paul McGrady,
<u></u><u></u></p>
<p class="MsoNormal"><b>Apology:</b> Michele Neylon<u></u><u></u></p>
<p class="MsoNormal"><b><span lang="DA">Staff:</span></b><span lang="DA"> Marika Konings, Steve Chan, Nathalie Peregrine</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="DA"> </span><u></u><u></u></p>
<p class="MsoNormal"><b>AC Chat</b>:<u></u><u></u></p>
<p class="MsoNormal"> Nathalie Peregrine:Dear all, welcome to
the GNSO Council Drafting Team call to discuss the draft
Charter concerning ICANN Procedure for Handling Whois
Conflicts on Monday 18 December 2017 at 2000 UTC<u></u><u></u></p>
<p class="MsoNormal"> Nathalie Peregrine:Public Comment:
Revised ICANN Procedure for Handling WHOIS Conflicts with
Privacy Law: Process and Next Steps: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__www.icann.org_public-2Dcomments_whois-2Dprivacy-2Dlaw-2D2017-2D05-2D03-2Den&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=5xenFICRdRkSUfvjRkSPDPi2nqmjNR9z40DOTbddJVM&s=adugQauUKQvuUEMdEec1VcDBdyG9osdhkqinwHG6ad0&e=" target="_blank">https://urldefense.<wbr>proofpoint.com/v2/url?u=https-<wbr>3A__www.icann.org_public-<wbr>2Dcomments_whois-2Dprivacy-<wbr>2Dlaw-2D2017-2D05-2D03-2Den&d=<wbr>DwICaQ&c=<wbr>FmY1u3PJp6wrcrwll3mSVzgfkbPSS6<wbr>sJms7xcl4I5cM&r=PDd_<wbr>FX3f4MVgkEIi9GHvVoUhbecsvLhgsy<wbr>XrxgtbL10DTBs0i1jYiBM_<wbr>uTSDzgqG&m=<wbr>5xenFICRdRkSUfvjRkSPDPi2nqmjNR<wbr>9z40DOTbddJVM&s=<wbr>adugQauUKQvuUEMdEec1VcDBdyG9os<wbr>dhkqinwHG6ad0&e=</a><u></u><u></u></p>
<p class="MsoNormal"> Nathalie Peregrine:Letter from Akram
Atallah to GNSO Council re the Revised ICANN Procedure for
Handling Whois Conflicts with Privacy Law: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_correspondence_atallah-2Dto-2Dbladel-2Det-2Dal-2D01aug17-2Den.pdf&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=5xenFICRdRkSUfvjRkSPDPi2nqmjNR9z40DOTbddJVM&s=ynH32qa5Y9sFgNk_mo6bzIjPiNm0dL5Sc3B1RWP0UJo&e=" target="_blank">https://urldefense.<wbr>proofpoint.com/v2/url?u=https-<wbr>3A__gnso.icann.org_en_<wbr>correspondence_atallah-2Dto-<wbr>2Dbladel-2Det-2Dal-2D01aug17-<wbr>2Den.pdf&d=DwICaQ&c=<wbr>FmY1u3PJp6wrcrwll3mSVzgfkbPSS6<wbr>sJms7xcl4I5cM&r=PDd_<wbr>FX3f4MVgkEIi9GHvVoUhbecsvLhgsy<wbr>XrxgtbL10DTBs0i1jYiBM_<wbr>uTSDzgqG&m=<wbr>5xenFICRdRkSUfvjRkSPDPi2nqmjNR<wbr>9z40DOTbddJVM&s=<wbr>ynH32qa5Y9sFgNk_<wbr>mo6bzIjPiNm0dL5Sc3B1RWP0UJo&e=</a><u></u><u></u></p>
<p class="MsoNormal"> Pam Little:Hi Everyone<u></u><u></u></p>
<p class="MsoNormal"> Marika Konings:Staff could put this into
the form of a google doc and have you provide comments / edits
on the different sections? <u></u><u></u></p>
<p class="MsoNormal"> Marika Konings:Note that an update on
this topic has also been foreseen for Thursday's Council
meeting that would allow you to flag certain items for Council
input, which may help inform your subsequent deliberations and
decision on some of the items outlined in the document. <u></u><u></u></p>
<p class="MsoNormal"> Pam Little:I will try to dial in by phone<u></u><u></u></p>
<p class="MsoNormal"> Pam Little:Please carry out for a moment<u></u><u></u></p>
<p class="MsoNormal"> Nathalie Peregrine:You need to activate
your AC mic, by clicking on the telehpne icon at the top of
the toolbar<u></u><u></u></p>
<p class="MsoNormal"> Nathalie Peregrine:this will also allow
you to dial out to yourself should you prefer to connect via
the phone.<u></u><u></u></p>
<p class="MsoNormal"> Marika Konings:the procedure has been
updated with a new trigger, per the recommendations of the
previous IAG.<u></u><u></u></p>
<p class="MsoNormal"> Marika Konings:my understanding is that
the procedure is intended for individual registries /
registrars, while the current discussion seems to deal with
almost all contracted parties<u></u><u></u></p>
<p class="MsoNormal"> Marika Konings:I guess the question is
also whether GDPR is considered a 'local law'?<u></u><u></u></p>
<p class="MsoNormal"> Keith Drazek:I'm in Adobe now. Apologies<u></u><u></u></p>
<p class="MsoNormal"> Heather Forrest:Great Keith - thanks<u></u><u></u></p>
<p class="MsoNormal"> Marika Konings:I believe the underlying
policy only focuses on WHOIS<u></u><u></u></p>
<p class="MsoNormal"> Heather Forrest:I understood that we were
dealing specifically with WHOIS conflicts?<u></u><u></u></p>
<p class="MsoNormal"> Keith Drazek:It's focused on WHOIS and
conflicts with national privacy laws, correct?<u></u><u></u></p>
<p class="MsoNormal"> Marika Konings:From the underlying policy
recommendations: In order to facilitate reconciliation of any
conflicts between local/national mandatory privacy laws or
regulations and applicable provisions of the ICANN contract
regarding the collection, display and distribution of personal
data via Whois, ICANN should.......<u></u><u></u></p>
<p class="MsoNormal"> Keith Drazek:Thanks Marika<u></u><u></u></p>
<p class="MsoNormal"> Marika Konings:so it is limited to WHOIS<u></u><u></u></p>
<p class="MsoNormal"> Keith Drazek:Yes<u></u><u></u></p>
<p class="MsoNormal"> Pam Little:That's what I thought too<u></u><u></u></p>
<p class="MsoNormal"> Marika Konings:For those interested in
reviewing the original report that forms the basis for the
procedure: <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__gnso.icann.org_en_issues_tf-2Dfinal-2Drpt-2D25oct05.htm&d=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=PDd_FX3f4MVgkEIi9GHvVoUhbecsvLhgsyXrxgtbL10DTBs0i1jYiBM_uTSDzgqG&m=5xenFICRdRkSUfvjRkSPDPi2nqmjNR9z40DOTbddJVM&s=FztMCfR9oT5btckkoo2gqrwFNOiZ9GJ3kDs5ChhSVhg&e=" target="_blank">https://urldefense.<wbr>proofpoint.com/v2/url?u=https-<wbr>3A__gnso.icann.org_en_issues_<wbr>tf-2Dfinal-2Drpt-2D25oct05.<wbr>htm&d=DwICaQ&c=<wbr>FmY1u3PJp6wrcrwll3mSVzgfkbPSS6<wbr>sJms7xcl4I5cM&r=PDd_<wbr>FX3f4MVgkEIi9GHvVoUhbecsvLhgsy<wbr>XrxgtbL10DTBs0i1jYiBM_<wbr>uTSDzgqG&m=<wbr>5xenFICRdRkSUfvjRkSPDPi2nqmjNR<wbr>9z40DOTbddJVM&s=<wbr>FztMCfR9oT5btckkoo2gqrwFNOiZ9G<wbr>J3kDs5ChhSVhg&e=</a><u></u><u></u></p>
<p class="MsoNormal"> Paul McGrady:Got it. Retracting my prior
comment about how broad this is. <u></u><u></u></p>
<p class="MsoNormal"> Heather Forrest:Thanks, Marika, for that
link to the original report. I intend to re-read that this
week.<u></u><u></u></p>
<p class="MsoNormal"> Heather Forrest:+1 Keith re focus on
trigger <u></u><u></u></p>
<p class="MsoNormal"> Heather Forrest:It's in drifting
discussion away from the trigger that we've gotten bogged down
on this in Council for the past year and a half or so... this
is NOT about the underlying policy<u></u><u></u></p>
<p class="MsoNormal"> Pam Little:Thank you all for the comments
and clarifications.<u></u><u></u></p>
<p class="MsoNormal"> Keith Drazek:Totally agree, this is not
GDPR-specific at all.<u></u><u></u></p>
<p class="MsoNormal"> Marika Konings:If you review the report
of public comments, you'll find some feedback on possible
issues with the alternative trigger. <u></u><u></u></p>
<p class="MsoNormal"> Keith Drazek:I don't think we want to
re-open the policy. <u></u><u></u></p>
<p class="MsoNormal"> Keith Drazek:The CPH thinks that the
policy is solid, it's just the current implementation needs
adjustment.<u></u><u></u></p>
<p class="MsoNormal"> Heather Forrest:@Marika - good suggestion
to ask the group to work with the public comments<u></u><u></u></p>
<p class="MsoNormal"> Keith Drazek:Thanks Marika, very helpful.<u></u><u></u></p>
<p class="MsoNormal"> Keith Drazek:(1) Review current
implementation; (2) re-consider previous triggers not agreed
to; (3) consider other possible triggers not previously
considered; (4) review everything based on existing public
comments.<u></u><u></u></p>
<p class="MsoNormal"> Marika Konings:we may need to further
emphasize in the charter that the trigger is just the first
step in the procedure, there are quite a few steps that follow
to make sure that everyone is clear on that. <u></u><u></u></p>
<p class="MsoNormal"> Keith Drazek:Agreed Heather re
composition<u></u><u></u></p>
<p class="MsoNormal"> Marika Konings:note there are also a
couple of options you may want to consider for composition /
representation<u></u><u></u></p>
<p class="MsoNormal"> Keith Drazek:Thanks Marika, that's
important for the precedent-setting nature of our work. <u></u><u></u></p>
<p class="MsoNormal"> Keith Drazek:@Marika, are those options
in the document staff developed? Apologies for not knowing<u></u><u></u></p>
<p class="MsoNormal"> Heather Forrest:OK - let's focus our
attention for charter on (1) scope/objective and (2)
composition, and take input from our respective SG/Cs on these
two key points<u></u><u></u></p>
<p class="MsoNormal"> Keith Drazek:Let's do early the week of
the 8th<u></u><u></u></p>
<p class="MsoNormal"> Keith Drazek:+1 Paul<u></u><u></u></p>
<p class="MsoNormal"> Heather Forrest:I agree Keith - doc
deadline should be around the 20th<u></u><u></u></p>
<p class="MsoNormal"> Marika Konings:is it helpful to put this
in a google doc format to facilitate your input or you prefer
to share feedback via email?<u></u><u></u></p>
<p class="MsoNormal"> Nathalie Peregrine:Doc deadline is the
20th jan.<u></u><u></u></p>
<p class="MsoNormal"> Marika Konings:makes sense :-)<u></u><u></u></p>
<p class="MsoNormal"> Nathalie Peregrine:Of course.<u></u><u></u></p>
<p class="MsoNormal"> Keith Drazek:Sounds like a plan. Thanks
to staff for prepping the document that I need to review more
carefully. <u></u><u></u></p>
<p class="MsoNormal"> Keith Drazek:Thanks Heather!<u></u><u></u></p>
<p class="MsoNormal"> Pam Little:Thanks everyone. Bye now<u></u><u></u></p>
<p class="MsoNormal"> Marika Konings:thanks all<u></u><u></u></p>
<p class="MsoNormal"> Heather Forrest:Thanks everyone<u></u><u></u></p>
<p class="MsoNormal"> <u></u><u></u></p>
<p class="MsoNormal"><span lang="DA"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="DA"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="DA"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="DA"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="DA">Kind regards,</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="DA"> </span><u></u><u></u></p>
<p class="MsoNormal"><span lang="DA">Nathalie</span><u></u><u></u></p>
<p class="MsoNormal"><span lang="DA"> </span><u></u><u></u></p>
</div>
</div>
</div>
<br>______________________________<wbr>_________________<br>
NCSG-PC mailing list<br>
<a href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a><br>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" rel="noreferrer" target="_blank">https://lists.ncsg.is/mailman/<wbr>listinfo/ncsg-pc</a><br>
<br></blockquote></div><br></div></div>