<div dir="auto"><div>1) Has the BC provided of case scenarios in which maintaining the secrecy of a represented party was paramount for their security? </div><div dir="auto"><br></div><div dir="auto">2) Privacy is not to be conflated with anonymity when the stakes affect, in essence, the whole Internet.</div><div dir="auto"><br></div><div dir="auto">3) Is the position of the BC that the lack of transparency is a tool that will protect ICANN processes from conflicts of interest or abuse? </div><div dir="auto"><br></div><div dir="auto">Jean</div><div dir="auto"><br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Fri, Apr 7, 2023, 22:47 Johan Helsingius <<a href="mailto:julf@julf.com">julf@julf.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The BC is arguing that lawyers/lobbyists/consultants who are<br>
participating in PDPs and WG:s shouldn't have to disclose who<br>
they are working for.<br>
<br>
Their comment about us is "Interesting that the NCSG – which is a<br>
vociferous proponent of privacy – is beating the drum for revealing<br>
representation. They can’t have it both ways – protect identities when<br>
they want and don’t when they find it convenient."<br>
<br>
Julf<br>
<br>
On 07/04/2023 15:52, Akinremi Peter Taiwo wrote:<br>
> Is the BC arguing for personal data in SOI be redacted or SOI should not <br>
> be disclosed.<br>
> <br>
> I don't really get why BC would be pushing for SOI not to be <br>
> publicly available as that can have a negative impact in policy making <br>
> considering the ICANN mission and its community nature.<br>
> <br>
> Privacy is not to hinder free flow of information but to ensure adequate <br>
> processing, accountability and security. Should not be traded when there <br>
> is possibility of influence in a community driven process or institution.<br>
> <br>
> We need to constantly put forward the purpose of SOI and its lawfulness.<br>
> <br>
> regards<br>
> <br>
> <br>
> On Fri, Apr 7, 2023 at 2:05 AM Jean F. Quéralt <br>
> <<a href="mailto:000016bf26350d73-dmarc-request@listserv.syr.edu" target="_blank" rel="noreferrer">000016bf26350d73-dmarc-request@listserv.syr.edu</a> <br>
> <mailto:<a href="mailto:000016bf26350d73-dmarc-request@listserv.syr.edu" target="_blank" rel="noreferrer">000016bf26350d73-dmarc-request@listserv.syr.edu</a>>> wrote:<br>
> <br>
> Hi Julf.<br>
> <br>
> "and initiatives around the world that protects it."<br>
> <br>
> "laughable" >> disingenuous<br>
> <br>
> " and this is only possible when we know who is at the table<br>
> influencing policy decisions."<br>
> >> <br>
> <br>
> and this is only possible when we know, which no shadow of a<br>
> doubt, which parties are sitting at the table influencing policy<br>
> decisions.<br>
> <br>
> <br>
> "they work together to"<br>
> >><br>
> "they work hand in hand to"<br>
> <br>
> <br>
> My 2 cents.<br>
> <br>
> Jean F. Queralt<br>
> Founder & CEO - The IO Foundation <<a href="http://www.TheIOFoundation.org" rel="noreferrer noreferrer" target="_blank">http://www.TheIOFoundation.org</a>><br>
> Book a meeting <<a href="http://TIOF.Click/BookJFQ" rel="noreferrer noreferrer" target="_blank">http://TIOF.Click/BookJFQ</a>> (30 minutes)<br>
> <br>
> <br>
> On Thu, 6 Apr 2023 at 13:48, Johan Helsingius <<a href="mailto:julf@julf.com" target="_blank" rel="noreferrer">julf@julf.com</a><br>
> <mailto:<a href="mailto:julf@julf.com" target="_blank" rel="noreferrer">julf@julf.com</a>>> wrote:<br>
> <br>
> We have put together a draft response on the GNSO<br>
> Statement of Interest Task Force (SOI-TF). We need<br>
> to submit our response by tomorrow (Friday 7 April).<br>
> Please feel free to comment or add.<br>
> <br>
> <a href="https://docs.google.com/document/d/1rmJPMhoTWEh37Ewh-ticj7WMgwcQQ7VMZkzIHLlbCVs/edit" rel="noreferrer noreferrer" target="_blank">https://docs.google.com/document/d/1rmJPMhoTWEh37Ewh-ticj7WMgwcQQ7VMZkzIHLlbCVs/edit</a> <<a href="https://docs.google.com/document/d/1rmJPMhoTWEh37Ewh-ticj7WMgwcQQ7VMZkzIHLlbCVs/edit" rel="noreferrer noreferrer" target="_blank">https://docs.google.com/document/d/1rmJPMhoTWEh37Ewh-ticj7WMgwcQQ7VMZkzIHLlbCVs/edit</a>><br>
> <br>
> Please note that the BC has specifically mentioned us in<br>
> their response, so we feel the need to address that.<br>
> <br>
> Julf<br>
> <br>
> <br>
> /*DISCLAIMER*/<br>
> /The content of this message, which may contain personal or<br>
> sensitive data, is confidential. If you have received it by mistake,<br>
> please inform the sender by replying to the email and then<br>
> permanently delete the message, including any attachments. It is<br>
> forbidden to copy, forward or in any way reveal the content of this<br>
> message to anyone. The integrity and security of this email cannot<br>
> be guaranteed over the Internet and, therefore, the sender will not<br>
> be held liable for any damage caused by the message./<br>
> <br>
> <br>
> <br>
> -- <br>
> Best regards<br>
> <br>
> *Taiwo Peter Akinremi*<br>
> ------ ------ ------- ------ ------ ------- ------ ------ ------- ------ <br>
> ------ ------- ------ ------<br>
> *Policy Advisory | Data Governance and Privacy Consultant | Information <br>
> Security & Cybersecurity | Certified Salesforce Administrator*<br>
> *Phone*; +2348117714345, +2347063830177 *Skype*: akinremi.taiwo<br>
> *Email:* <a href="mailto:compsoftnet@gmail.com" target="_blank" rel="noreferrer">compsoftnet@gmail.com</a> <mailto:<a href="mailto:compsoftnet@gmail.com" target="_blank" rel="noreferrer">compsoftnet@gmail.com</a>>, <br>
> <a href="mailto:peterexecute@gmail.com" target="_blank" rel="noreferrer">peterexecute@gmail.com</a> <mailto:<a href="mailto:peterexecute@gmail.com" target="_blank" rel="noreferrer">peterexecute@gmail.com</a>><br>
> ___________________________________________<br>
</blockquote></div></div></div>
<br>
<div><i><font size="2" color="#808080"><b>DISCLAIMER</b></font></i></div><div><i><font size="2" color="#808080">The content of this message, which may contain personal or sensitive data, is confidential. If you have received it by mistake, please inform the sender by replying to the email and then permanently delete the message, including any attachments. It is forbidden to copy, forward or in any way reveal the content of this message to anyone. The integrity and security of this email cannot be guaranteed over the Internet and, therefore, the sender will not be held liable for any damage caused by the message.</font></i></div>