[CCWG-ACCT] draft language for certification to lawyers on HR question

[Seun Ojedeji]

+1 on both counts, with minor modification. Would suggest inclusion of the
words in bold in the second paragraph ".... the inclusion *of the language
as proposed in the 3rd draft* in the bylaws would...".

Regards

On Wed, Jan 6, 2016 at 2:41 PM, Niels ten Oever <lists at digitaldissidents.org
> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Hi all,
>
> I would like to thank the co-chairs for their suggestion at the end of
> yesterdays call. Please allow me to make some suggestions to the languag
> e:
>
> ***
>
> In their comment to the 3rd CCWG draft report the ICANN Board has
> raised concerns that the proposed inclusion of language in the bylaws
> with respect to human rights might lead to an increased risk of ICANN
> being exposed to legal claims or even law suits.
>
> We would appreciate if you could provide us with a brief assessment
> whether the inclusion of these bylaws would increase the risk of ICANN
> being exposed to legal claims or even law suits vis a vis the current
> situation (taking into account the existing obligations under article
> 4 of ICANNs articles of incorporation), and if so, how such risk could
> be mitigated.
>
> ***
>
> Best,
>
> Niels
>
>
>
> On 01/06/2016 02:13 PM, Thomas Rickert wrote:
> > All, as discussed during yesterday’s CCWG call, please find below
> > the draft certification language to be sent to the lawyers with
> > respect to the human rights recommendation and the Board’s concerns
> > about legal risks. I plan to certify at 14.00 UTC tomorrow.
> >
> > *** The ICANN Board has raised concerns that the proposed
> > inclusion of language in the bylaws with respect to human rights
> > might lead to an increased risk of ICANN being exposed to legal
> > claims or even law suits.
> >
> > We would appreciate if you could provide us with a brief
> > assessment and suggestions on how such risk can be mitigated. It is
> > our understanding that human rights have been indirectly referred
> > to in ICANN's bylaws already, so please also indicate whether
> > (according to your assessment) the language that shall be added to
> > the bylaws according to our 3rd report is establishing a new risk
> > or an increased risk, if any. ***
> >
> > Kind regards, Thomas Rickert
> >
> >
> >
> > _______________________________________________
> > Accountability-Cross-Community mailing list
> > Accountability-Cross-Community at icann.org
> > https://mm.icann.org/mailman/listinfo/accountability-cross-community
> >
> >
> - --
> Niels ten Oever
> Head of Digital
>
> Article 19
> www.article19.org
>
> PGP fingerprint    8D9F C567 BEE4 A431 56C4
>                    678B 08B5 A0F2 636D 68E9
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQEcBAEBCAAGBQJWjRmQAAoJEAi1oPJjbWjpKukH/R8EhC2tCyF4qGYNzS7L4Qn3
> Oloj8IoIpinFRIGnB3aGLUgGJSI9NykuLNTJ0/BIcG4Gfy8qUIKpL8M/USpoasgd
> 4S3p+jQRrR2SgU9TTSY0LfWvQpY5EZVJ0qSqkREEeBSAhjeiO/A9QS1B54goamOP
> ur9BToZwKeeNUdesznkcQeM+jLnxvG418EERjIf/p7luMO0WGEYlfM7X05tS6tHp
> 3cJcV22cVqPj5PkpHP6WxsOBMCVARWEa6x6221yYH7uVM+SfYRHH+KYzKKOTffe1
> medmWat4kAtqKpYcGY9IrYhmjaq/VZn/4SJZiDq6CGzWIDsFD8ThrCg411vbXLc=
> =i0fO
> -----END PGP SIGNATURE-----
> _______________________________________________
> Accountability-Cross-Community mailing list
> Accountability-Cross-Community at icann.org
> https://mm.icann.org/mailman/listinfo/accountability-cross-community
>



-- 
------------------------------------------------------------------------





*Seun Ojedeji,Federal University Oye-Ekitiweb:      http://www.fuoye.edu.ng
<http://www.fuoye.edu.ng> Mobile: +2348035233535**alt email:
<http://goog_1872880453>seun.ojedeji at fuoye.edu.ng
<seun.ojedeji at fuoye.edu.ng>*

Bringing another down does not take you up - think about your action!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/accountability-cross-community/attachments/20160106/a263ca9b/attachment.html>