<div dir="ltr"><div class="gmail_extra">Hi Ayden,</div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks for the work done and getting comments. Please resolve the comments in document and clean it up</div><div class="gmail_extra">@PC members please review the document and share your opinion asap.<br>since the draft was shared weeks ago and the deadline to submit the comment is the Friday 7th July, so the deadline for approval is the 6th July. </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">2017-07-04 1:00 GMT+09:00 Ayden Férdeline <span dir="ltr"><<a href="mailto:icann@ferdeline.com" target="_blank">icann@ferdeline.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>A reminder, please, that we need feedback on this comment re: handling WHOIS conflicts with privacy law. Thank you.<br></div><span class="im HOEnZb"><div><br></div><div><a href="https://docs.google.com/document/d/1lA-O2jiPv5JMoCYpG5HD0S_5O3yaiYkoRvfll3YsTX4/edit?usp=sharing" target="_blank">https://docs.google.com/<wbr>document/d/1lA-<wbr>O2jiPv5JMoCYpG5HD0S_<wbr>5O3yaiYkoRvfll3YsTX4/edit?usp=<wbr>sharing</a><br></div><div><br></div><div class="m_-5864786020720421217protonmail_signature_block"><div class="m_-5864786020720421217protonmail_signature_block-user"><div>Best wishes, Ayden <br></div></div><div class="m_-5864786020720421217protonmail_signature_block-proton m_-5864786020720421217protonmail_signature_block-empty"><br></div></div><div><br></div></span><div class="HOEnZb"><div class="h5"><blockquote class="m_-5864786020720421217protonmail_quote" type="cite"><div>-------- Original Message --------<br></div><div>Subject: Fw: Re: [DRAFT] Potential NCSG Comment on ICANN Procedure for Handling WHOIS Conflicts with Privacy Law<br></div><div>Local Time: June 30, 2017 12:55 PM<br></div><div>UTC Time: June 30, 2017 11:55 AM<br></div><div>From: <a href="mailto:icann@ferdeline.com" target="_blank">icann@ferdeline.com</a><br></div><div>To: ncsg-pc <<a href="mailto:ncsg-pc@lists.ncsg.is" target="_blank">ncsg-pc@lists.ncsg.is</a>><br></div><div><br></div><div>Would be great to receive some feedback from EDRi on this comment. The submission deadline for this comment is in seven days time, and it still needs work. Please see the Google Doc <a href="https://docs.google.com/document/d/1lA-O2jiPv5JMoCYpG5HD0S_5O3yaiYkoRvfll3YsTX4/edit?usp=sharing" title="here" rel="nofollow" target="_blank">here</a>; your suggested edits are warmly welcomed, especially in regards to the recommendation(s). Thanks very much!<br></div><div><br></div><div class="m_-5864786020720421217protonmail_signature_block"><div class="m_-5864786020720421217protonmail_signature_block-user"><div>Best wishes, Ayden <br></div></div><div class="m_-5864786020720421217protonmail_signature_block-proton m_-5864786020720421217protonmail_signature_block-empty"><br></div></div><div><br></div><blockquote class="m_-5864786020720421217protonmail_quote" type="cite"><div>-------- Original Message --------<br></div><div>Subject: Re: [DRAFT] Potential NCSG Comment on ICANN Procedure for Handling WHOIS Conflicts with Privacy Law<br></div><div>Local Time: June 30, 2017 1:53 PM<br></div><div>UTC Time: June 30, 2017 11:53 AM<br></div><div>From: <a href="mailto:icann@ferdeline.com" target="_blank">icann@ferdeline.com</a><br></div><div>To: Maryant Fernandez Perez <<a href="mailto:maryant.fernandez-perez@EDRI.ORG" target="_blank">maryant.fernandez-perez@EDRI.<wbr>ORG</a>><br></div><div><a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU" target="_blank">NCSG-DISCUSS@LISTSERV.SYR.EDU</a> <<a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU" target="_blank">NCSG-DISCUSS@LISTSERV.SYR.EDU</a><wbr>><br></div><div><br></div><div><div>Maryant, hi-<br></div><div><br></div><div>Thank you very much for your email. I am pleased to hear that EDRi may be able to provide input into this comment on handling WHOIS conflicts with privacy laws. Our Policy Committee is agile, so if we receive comments or suggested edits up to 72 hours before the comment submission deadline of 7 July 23:59 UTC, we should be able to review them. Thanks again!<br></div><div><br></div><div>Best wishes,<br></div></div><div><br></div><div class="m_-5864786020720421217protonmail_signature_block"><div class="m_-5864786020720421217protonmail_signature_block-user"><div>Ayden Férdeline<br></div><div><a title="http://www.linkedin.com/in/ferdeline" href="http://www.linkedin.com/in/ferdeline" rel="noreferrer nofollow noopener" target="_blank">linkedin.com/in/ferdeline</a><br></div></div><div class="m_-5864786020720421217protonmail_signature_block-proton m_-5864786020720421217protonmail_signature_block-empty"><br></div></div><div><br></div><blockquote type="cite" class="m_-5864786020720421217protonmail_quote"><div>-------- Original Message --------<br></div><div>Subject: Re: [DRAFT] Potential NCSG Comment on ICANN Procedure for Handling WHOIS Conflicts with Privacy Law<br></div><div>Local Time: June 28, 2017 1:11 PM<br></div><div>UTC Time: June 28, 2017 11:11 AM<br></div><div>From: <a href="mailto:maryant.fernandez-perez@EDRI.ORG" target="_blank">maryant.fernandez-perez@EDRI.<wbr>ORG</a><br></div><div>To: <a href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU" target="_blank">NCSG-DISCUSS@LISTSERV.SYR.EDU</a><br></div><div><br></div><div><span class="m_-5864786020720421217font" style="font-family:Helvetica,Arial,sans-serif">Hi,<br> <br> I've set our own internal deadline for this Friday, 30 June COB.<br> I hope to be able to get back to you by then. I can't promise
anything at this stage because it wasn't foreseen in our work
schedule, but I'll try my best.<br> <br> Thanks,<br> Maryant</span></div><div><br></div><div class="m_-5864786020720421217moz-cite-prefix">Le 28/06/17 à 13:09, Rafik Dammak a
écrit :<br></div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra">Hi Maryant,<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">thanks for message, it will be great to
get more feedback<br></div><div class="gmail_extra">any idea by when you can get input from
EDRI members?<br></div><div class="gmail_extra">btw there was a public session
yesterday about GDPR and its impacts <a rel="noreferrer nofollow noopener" href="https://schedule.icann.org/event/B3ot/gdpr-and-its-potential-impact-looking-for-practical-solutions" target="_blank">https://schedule.<wbr>icann.org/event/B3ot/gdpr-and-<wbr>its-potential-impact-looking-<wbr>for-practical-solutions</a><br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Best,<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Rafik<br></div><div class="gmail_extra"><br></div><div class="gmail_extra"><div><br></div><div class="gmail_quote"><div>2017-06-28 19:46 GMT+09:00 Maryant
Fernandez Perez <span dir="ltr"><<a rel="noreferrer nofollow noopener" href="mailto:maryant.fernandez-perez@edri.org" target="_blank">maryant.fernandez-perez@edri.<wbr>org</a>></span>:<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div bgcolor="#FFFFFF"><div><span class="m_-5864786020720421217font" style="font-family:Helvetica,Arial,sans-serif">Hi Ayden & all,<br> <br> Some of EDRi members may be willing to provide input,
as in EDRi we have extensively worked on the GDPR and
in its implementation.<br> I'm aware the the official deadline is 7 July.<br> What's the last internal deadline to comment on it?<br> <br> Thanks and best regards,<br> Maryant</span></div><div><br></div><pre class="m_-5864786020720421217gmail-m_-7674322604804484831moz-signature" cols="72">--
Maryant Fernandez Perez
Senior Policy Advisor
European Digital Rights (EDRi)
20 Rue Belliard
1040 Brussels (Belgium)
<a rel="noreferrer nofollow noopener" class="m_-5864786020720421217gmail-m_-7674322604804484831moz-txt-link-freetext" href="https://edri.org" target="_blank">https://edri.org</a>
Tel: <a rel="noreferrer nofollow noopener" href="tel:+32%202%20274%2025%2070" value="+3222742570" target="_blank">+32 2 274 25 70</a>
PGP: D59A 1D3F 50CC 231B DCFE 3F2C 92FA 6F29 3D74 0B42
@edri | @maryantfp
Donate to EDRi! <a rel="noreferrer nofollow noopener" class="m_-5864786020720421217gmail-m_-7674322604804484831moz-txt-link-freetext" href="https://edri.org/donate/" target="_blank">https://edri.org/donate/</a>
Subscribe to the EDRi-gram, our fortnightly roundup of digital rights news! <a rel="noreferrer nofollow noopener" class="m_-5864786020720421217gmail-m_-7674322604804484831moz-txt-link-freetext" href="http://edri.org/newsletters/" target="_blank">http://edri.org/newsletters/</a>
<br></pre><div class="m_-5864786020720421217gmail-m_-7674322604804484831moz-cite-prefix">Le
14/06/17 à 00:05, Ayden Férdeline a écrit :<br></div><div><div class="m_-5864786020720421217gmail-h5"><blockquote type="cite"><div><div>Hello all,<br></div><div><br></div><div>I have revised our draft comment on the
effectiveness of the updated ICANN Procedure for
Handling WHOIS Conflicts with Privacy Law.
Paragraphs 3 and 7, in particular, are new. Your
review of and feedback on this proposed comment
is warmly welcomed. The submission deadline is 7
July, but I am hoping we may be able to finalise
the comment before this date, given we have
ICANN 59 approaching in just over a week's time.
Thank you!<br></div></div><div><br></div><div><a rel="noreferrer nofollow noopener" href="https://docs.google.com/document/d/1lA-O2jiPv5JMoCYpG5HD0S_5O3yaiYkoRvfll3YsTX4/edit?usp=sharing" target="_blank">https://docs.google.com/docume<wbr>nt/d/1lA-O2jiPv5JMoCYpG5HD0S_5<wbr>O3yaiYkoRvfll3YsTX4/edit?usp=s<wbr>haring</a><br></div><div><br></div><div class="m_-5864786020720421217gmail-m_-7674322604804484831protonmail_signature_block"><div class="m_-5864786020720421217gmail-m_-7674322604804484831protonmail_signature_block-user"><div>Best wishes, Ayden Férdeline <br></div></div><div class="m_-5864786020720421217gmail-m_-7674322604804484831protonmail_signature_block-proton
gmail-m_-7674322604804484831protonmail_signature_block-empty"><br></div></div><div><br></div><blockquote class="m_-5864786020720421217gmail-m_-7674322604804484831protonmail_quote" type="cite"><div>-------- Original Message --------<br></div><div>Subject: [DRAFT] Potential NCSG Comment on
ICANN Procedure for Handling WHOIS Conflicts
with Privacy Law<br></div><div>Local Time: May 13, 2017 8:36 PM<br></div><div>UTC Time: May 13, 2017 7:36 PM<br></div><div>From: <a rel="noreferrer nofollow noopener" class="m_-5864786020720421217gmail-m_-7674322604804484831moz-txt-link-abbreviated" href="mailto:icann@FERDELINE.COM" target="_blank">icann@FERDELINE.COM</a><br></div><div>To: <a rel="noreferrer nofollow noopener" class="m_-5864786020720421217gmail-m_-7674322604804484831moz-txt-link-abbreviated" href="mailto:NCSG-DISCUSS@LISTSERV.SYR.EDU" target="_blank">NCSG-DISCUSS@LISTSERV.SYR.EDU</a><br></div><div><br></div><div>Dear colleagues,<br></div><div><br></div><div>I have drafted a comment on behalf of the
NCSG on the effectiveness of the updated <a rel="noreferrer nofollow noopener" title="ICANN Procedure" href="https://www.icann.org/public-comments/whois-privacy-law-2017-05-03-en" target="_blank">ICANN
Procedure</a> for Handling WHOIS Conflicts
with Privacy Law. I warmly welcome your
comments, suggestions, and edits so that we
can strengthen this comment.<br></div><div><br></div><div><a href="https://docs.google.com/document/d/1lA-O2jiPv5JMoCYpG5HD0S_5O3yaiYkoRvfll3YsTX4/edit?usp=sharing" rel="noreferrer nofollow noopener" target="_blank">https://docs.google.com/docume<wbr>nt/d/1lA-O2jiPv5JMoCYpG5HD0S_5<wbr>O3yaiYkoRvfll3YsTX4/edit?usp=s<wbr>haring</a><br></div><div><br></div><div>The deadline for submission of comments on
this topic is in 30 days, on 12 June. I would
like to get this to the Policy Committee to
review one week earlier, on 5 June, so I
kindly ask that you make your comments before
this time if you can please. Thanks!<br></div><div><br></div><div>Best wishes,<br></div><div><br></div><div class="m_-5864786020720421217gmail-m_-7674322604804484831protonmail_signature_block"><div class="m_-5864786020720421217gmail-m_-7674322604804484831protonmail_signature_block-user"><div>Ayden Férdeline<br></div><div><a title="http://www.linkedin.com/in/ferdeline" href="http://www.linkedin.com/in/ferdeline" rel="noreferrer nofollow noopener" target="_blank">linkedin.com/in/ferdeline</a><br></div></div><div class="m_-5864786020720421217gmail-m_-7674322604804484831protonmail_signature_block-proton
gmail-m_-7674322604804484831protonmail_signature_block-empty"><br></div></div><div><br></div></blockquote><div><br></div></blockquote><div><br></div></div></div></div></blockquote></div><div><br></div></div></div></blockquote><div><br></div><pre class="m_-5864786020720421217moz-signature" cols="72">--
Maryant Fernandez Perez
Senior Policy Advisor
European Digital Rights (EDRi)
20 Rue Belliard
1040 Brussels (Belgium)
<a rel="noreferrer nofollow noopener" class="m_-5864786020720421217moz-txt-link-freetext" href="https://edri.org" target="_blank">https://edri.org</a>
Tel: <a href="tel:+32%202%20274%2025%2070" value="+3222742570" target="_blank">+32 2 274 25 70</a>
PGP: D59A 1D3F 50CC 231B DCFE 3F2C 92FA 6F29 3D74 0B42
@edri | @maryantfp
Donate to EDRi! <a rel="noreferrer nofollow noopener" class="m_-5864786020720421217moz-txt-link-freetext" href="https://edri.org/donate/" target="_blank">https://edri.org/donate/</a>
Subscribe to the EDRi-gram, our fortnightly roundup of digital rights news! <a rel="noreferrer nofollow noopener" class="m_-5864786020720421217moz-txt-link-freetext" href="http://edri.org/newsletters/" target="_blank">http://edri.org/newsletters/</a>
<br></pre></blockquote><div><br></div></blockquote><div><br></div></blockquote><div><br></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>