<div>Hi all,<br></div><div><br></div><div>I have done some final polishing to the letter, and have attached a proposed final draft. I hope we may be able to reach agreement soon on sending this letter. Also - I was wondering, should it carry a name, perhaps of the Chair, or is it okay to be signed 'NCSG'?</div><div><br></div><div class="protonmail_signature_block"><div class="protonmail_signature_block-user"><div>Many thanks, Ayden <br></div></div><div class="protonmail_signature_block-proton protonmail_signature_block-empty"><br></div></div><div><br></div><blockquote class="protonmail_quote" type="cite"><div>-------- Original Message --------<br></div><div>Subject: Re: [NCSG-PC] [Draft] Letter to ICANN re: BC and IPC correspondence<br></div><div>Local Time: 13 October 2017 7:59 PM<br></div><div>UTC Time: 13 October 2017 18:59<br></div><div>From: icann@ferdeline.com<br></div><div>To: Stephanie Perrin <stephanie.perrin@mail.utoronto.ca>, ncsg-pc@lists.ncsg.is<br></div><div><br></div><div>I think it is the perfect tone for this letter. As we saw in Hong Kong this month, our public silence is being manipulated and used to make the false claim that we are being consulted with and are an integral part of ICANN's efforts to comply
with the GDPR, when we are not. Thanks for these edits Stephanie. We need to reshape the narrative and get it all documented. <br></div><div><br></div><div><div>Ayden Férdeline <br></div><div>Sent from ProtonMail Mobile<br></div></div><div><div><br></div><div><div><br></div><div>On Fri, Oct 13, 2017 at 7:14 pm, Stephanie Perrin <<a class="" href="mailto:stephanie.perrin@mail.utoronto.ca">stephanie.perrin@mail.utoronto.ca</a>> wrote:<br></div></div><blockquote type="cite" class="protonmail_quote"><p><span class="size" style="font-size:undefinedpx"><span class="font" style="font-family:Lucida Grande">I jumped in today
(apologies for being anonymous, always forget my google
password) and made quite a few changes. I like the idea, but
I think we should be a bit more specific. In terms of informing
the DPAs....Swineheart is trying to get people to the IWGDPT
meeting in Paris, I think everyone has been briefed at the
data commissioners meeting in Hong kong (remember a whole crew
from ICANN went) that there is a draft statement coming. So
they know we have been briefing them for two years, we need to
sharpen that a bit.</span></span><br></p><p><span class="size" style="font-size:undefinedpx"><span class="font" style="font-family:Lucida Grande">Let me know if you
think it was a bit too strong. I will confess, I am losing my
patience with this lot. They spend gobs of money gadding
around trying to nullify end user rights. Totally ignore us.
Ought to be ashamed of themselves.</span></span><br></p><p><span class="size" style="font-size:undefinedpx"><span class="font" style="font-family:Lucida Grande">Stephanie</span></span> <br></p><div><br></div><div class="moz-cite-prefix">On 2017-10-13 07:05, Rafik Dammak wrote: <br></div><blockquote type="cite"><div dir="ltr"><div class="gmail_extra">hi,<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">reminder for everyone to review the letter and share comments.<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"><div>Rafik <br></div><div> <br></div><div> <br></div><div class="gmail_quote"><div>2017-10-11 4:28 GMT+09:00 Ayden Férdeline <span dir="ltr"><<a href="mailto:icann@ferdeline.com">icann@ferdeline.com</a>></span>: <br></div><div> <br></div><blockquote style="margin: 0px 0px 0px 0.8ex;" class="gmail_quote"><div>Also - I have now revised this letter again taking into account the helpful feedback that was received over the past 48 hours; moving forward, please feel free to edit the document directly if you have any changes you'd like
to see made. Thanks!<span class="HOEnZb"><span class="colour" style="color:#888888"></span></span><br></div><span class="HOEnZb"><span class="colour" style="color:#888888"><div><br></div><div class="m_2124695277728767332protonmail_signature_block"><div class="m_2124695277728767332protonmail_signature_block-user"><div>Ayden <br></div></div><div class="m_2124695277728767332protonmail_signature_block-proton
m_2124695277728767332protonmail_signature_block-empty"><br></div></div><div><br></div></span></span><blockquote type="cite" class="m_2124695277728767332protonmail_quote"><span class=""><div>-------- Original Message --------<br></div><div>Subject: Re: [NCSG-PC] [Draft] Letter to ICANN
re: BC and IPC correspondence<br></div></span><div><div class="h5"><div>Local Time: 10 October 2017 7:44 PM <br></div><div>UTC Time: 10 October 2017 18:44 <br></div><div>From: <a href="mailto:icann@ferdeline.com">icann@ferdeline.com</a> <br></div><div>To: Rafik Dammak <<a href="mailto:rafik.dammak@gmail.com">rafik.dammak@gmail.com</a>> <br></div><div>ncsg-pc <<a href="mailto:ncsg-pc@lists.ncsg.is">ncsg-pc@lists.ncsg.is</a>> <br></div><div><br></div><div>Hi Rafik, <br></div><div><br></div><div><div>Thank you very much for your comments. <br></div><div><br></div><div>It would be great if we could finalise this letter by Friday and perhaps even send it out that day. I very much welcome edits directly to the Google Doc; everyone on this list, please help write it and shape
its contents! <br></div></div><div><br></div><div>I would also like to propose that we write a monthly letter to ICANN on this topic until May 2018, when enforcement of the GDPR comes into effect. That way we can document for the data protection authorities that
we have been informing ICANN in excess of six months of their need to comply with this regulation. <br></div><div><br></div><div>The feedback from Nick Shorey on the PC call today - that we need to help engineer a conversation between the DPAs and their GAC representatives - is an interesting one, and one which seemed to have support in the
chat. How would we go about this, however? Do we write to the GAC? Do we express this desire to them in Abu Dhabi during our face-to-face with them? <br></div><div><br></div><div><div>Best wishes, <br></div><div><br></div><div>Ayden <br></div></div><div class="m_2124695277728767332protonmail_signature_block"><div class="m_2124695277728767332protonmail_signature_block-proton
m_2124695277728767332protonmail_signature_block-empty"><br></div></div><div><br></div><blockquote class="m_2124695277728767332protonmail_quote" type="cite"><div>-------- Original Message -------- <br></div><div>Subject: Re: [NCSG-PC] [Draft] Letter to ICANN re: BC and IPC correspondence <br></div><div>Local Time: 10 October 2017 5:33 AM <br></div><div>UTC Time: 10 October 2017 04:33 <br></div><div>From: <a href="mailto:rafik.dammak@gmail.com">rafik.dammak@gmail.com</a> <br></div><div>To: Ayden Férdeline <<a href="mailto:icann@ferdeline.com">icann@ferdeline.com</a>> <br></div><div>ncsg-pc <<a href="mailto:ncsg-pc@lists.ncsg.is">ncsg-pc@lists.ncsg.is</a>> <br></div><div><br></div><div dir="ltr"><div class="gmail_extra">Hi Ayden, <br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Thanks for the draft, <br></div><div class="gmail_extra">it is important we make a point to voice our concerns and influence the process. as we discussed before here and on the last call we got 2 problems 1- our representatives in taskforce not being informed
2- the last Data protection conference (that is already passed) <br></div><div class="gmail_extra"><br></div><div class="gmail_extra">for the current letter, indeed we should tweak the language there ;) while we keep the substance. reading IPC letter, it seems they reject the use case matrix and I understood from previous comments you
think that doesn't include our perspective. I add few comments but I think we can add more, in particular, our concerns in general regarding the process and not just responding to BC and IPC requests. <br></div><div class="gmail_extra"><br></div><div class="gmail_extra">I ask other PC members to review the letter and share their thoughts. I put the GDPR as a discussion item for today call. We need a deadline to get this done and prior to Abud Dhabi meeting if we may want
to continue the discussion there and depending on how things go with the cross-community session. I propose that we reach a new version by this Friday. <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"><div><br></div><div class="gmail_quote"><div>2017-10-08 23:07 GMT+09:00 Ayden Férdeline <span dir="ltr"><<a href="mailto:icann@ferdeline.com">icann@ferdeline.com</a>></span>: <br></div><blockquote style="margin: 0px 0px 0px 0.8ex;" class="gmail_quote"><div>Hi, <br></div><div><br></div><div>I have drafted a letter to ICANN in response to the recent correspondence received from the BC and the IPC. <a rel="nofollow" title="You can read/edit it here." href="https://docs.google.com/document/d/13ujYOpJFL0eNvjQCiNmsduFFbiUPQC5Wmbe9wHC2K6Q/edit?usp=sharing">You can
read/edit it here.</a> I know the language is provocative (intentionally so), but this is a first draft -- and if you disapprove please provide alternative language. <br></div><div><br></div><div>Best, Ayden <br></div><div><br></div><div>______________________________ <wbr>_________________ <br></div><div>NCSG-PC mailing list <br></div><div><a href="mailto:NCSG-PC@lists.ncsg.is">NCSG-PC@lists.ncsg.is</a> <br></div><div><a rel="noreferrer" href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc">https://lists.ncsg.is/mailman/<wbr>listinfo/ncsg-pc</a> <br></div><div><br></div></blockquote></div></div></div></blockquote><div><br></div></div></div></blockquote><div><br></div></blockquote></div><div><br></div></div></div><div><br></div><div><br></div><pre wrap="">_______________________________________________
NCSG-PC mailing list
<a href="mailto:NCSG-PC@lists.ncsg.is" class="moz-txt-link-abbreviated">NCSG-PC@lists.ncsg.is</a>
<a href="https://lists.ncsg.is/mailman/listinfo/ncsg-pc" class="moz-txt-link-freetext">https://lists.ncsg.is/mailman/listinfo/ncsg-pc</a>
<br></pre></blockquote></blockquote></div></blockquote><div><br></div>