<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Niels,</div><div id="AppleMailSignature">We trust it has been checked for risks, but since the Board has raised the issue and possible added new ideas to the discussion of risks, we should have this double-checked.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Best,</div><div id="AppleMailSignature">Thomas</div><div id="AppleMailSignature"><br><div><span style="font-size: 13pt;">---</span></div><div><a href="http://rickert.net">rickert.net</a></div><div><br></div></div><div><br>Am 06.01.2016 um 14:51 schrieb Niels ten Oever <<a href="mailto:lists@digitaldissidents.org">lists@digitaldissidents.org</a>>:<br><br></div><blockquote type="cite"><div><span>-----BEGIN PGP SIGNED MESSAGE-----</span><br><span>Hash: SHA256</span><br><span></span><br><span>If you would permit me, I have a small process question:</span><br><span></span><br><span>The proposed text on human rights in the CCWG report has already been</span><br><span>reviewed by lawyers (at the time it was prepared by WP4). Were these</span><br><span>the same lawyers that will answer the proposed question underneath? If</span><br><span>so, have they not checked for these risks the last time? If so, this</span><br><span>could save us some time.</span><br><span></span><br><span>Best,</span><br><span></span><br><span>Niels</span><br><span></span><br><span>On 01/06/2016 02:41 PM, Niels ten Oever wrote:</span><br><blockquote type="cite"><span>Hi all,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>I would like to thank the co-chairs for their suggestion at the end</span><br></blockquote><blockquote type="cite"><span>of yesterdays call. Please allow me to make some suggestions to the</span><br></blockquote><blockquote type="cite"><span>language:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>***</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>In their comment to the 3rd CCWG draft report the ICANN Board has </span><br></blockquote><blockquote type="cite"><span>raised concerns that the proposed inclusion of language in the</span><br></blockquote><blockquote type="cite"><span>bylaws with respect to human rights might lead to an increased risk</span><br></blockquote><blockquote type="cite"><span>of ICANN being exposed to legal claims or even law suits.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>We would appreciate if you could provide us with a brief</span><br></blockquote><blockquote type="cite"><span>assessment whether the inclusion of these bylaws would increase the</span><br></blockquote><blockquote type="cite"><span>risk of ICANN being exposed to legal claims or even law suits vis a</span><br></blockquote><blockquote type="cite"><span>vis the current situation (taking into account the existing</span><br></blockquote><blockquote type="cite"><span>obligations under article 4 of ICANNs articles of incorporation),</span><br></blockquote><blockquote type="cite"><span>and if so, how such risk could be mitigated.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>***</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Best,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Niels</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>On 01/06/2016 02:13 PM, Thomas Rickert wrote:</span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>All, as discussed during yesterday’s CCWG call, please find</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>below the draft certification language to be sent to the lawyers</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>with respect to the human rights recommendation and the Board’s</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>concerns about legal risks. I plan to certify at 14.00 UTC</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>tomorrow.</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>*** The ICANN Board has raised concerns that the proposed </span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>inclusion of language in the bylaws with respect to human rights </span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>might lead to an increased risk of ICANN being exposed to legal </span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>claims or even law suits.</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>We would appreciate if you could provide us with a brief </span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>assessment and suggestions on how such risk can be mitigated. It</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>is our understanding that human rights have been indirectly</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>referred to in ICANN's bylaws already, so please also indicate</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>whether (according to your assessment) the language that shall be</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>added to the bylaws according to our 3rd report is establishing a</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>new risk or an increased risk, if any. ***</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>Kind regards, Thomas Rickert</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>_______________________________________________ </span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Accountability-Cross-Community mailing list </span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a> </span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>_______________________________________________ </span><br></blockquote><blockquote type="cite"><span>Accountability-Cross-Community mailing list </span><br></blockquote><blockquote type="cite"><span><a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a> </span><br></blockquote><blockquote type="cite"><span><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><span>- -- </span><br><span>Niels ten Oever</span><br><span>Head of Digital</span><br><span></span><br><span>Article 19</span><br><span><a href="http://www.article19.org">www.article19.org</a></span><br><span></span><br><span>PGP fingerprint 8D9F C567 BEE4 A431 56C4</span><br><span> 678B 08B5 A0F2 636D 68E9</span><br><span>-----BEGIN PGP SIGNATURE-----</span><br><span>Version: GnuPG v2</span><br><span></span><br><span>iQEcBAEBCAAGBQJWjRvcAAoJEAi1oPJjbWjpiL4H/08f9uvS7Re/f6pxH06Hbjei</span><br><span>aWAXLigeqlsKdYJQGPRhe5hOYpvw48huNC6ed6wbfjHgqPbHyHzAjThsGu4z5GB5</span><br><span>5NQYufmBtjvgs2j2n6MiwJFQx1cQVv54gwe6tPTWG1G1qZGc9uat2eFY4G609lSi</span><br><span>DImT1FTnuGcTOuNdEX6sWJsx+IAcgKLYbs9yXUzAHeUIX0WeKFdbwxBMbvMHpfVX</span><br><span>0XZvfz9t8QPUD7hhaApWio34NV9h9nTw17/F4kg0oNlZLT4l7RTxSH4vgTI7RD5Y</span><br><span>yNa/RZriZAOhEyODuyjpsCbjetg/kReol9RGEHKt5LO079HwTZN4LO4TvTd/qKQ=</span><br><span>=vdV0</span><br><span>-----END PGP SIGNATURE-----</span><br><span>_______________________________________________</span><br><span>Accountability-Cross-Community mailing list</span><br><span><a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span><br></div></blockquote></body></html>