-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear Rudolph, On 09/11/2015 07:45 PM, Rudolph Daniel wrote:
Hi Greg
---------- Forwarded message ---------- From: "Rudolph Daniel" <rudi.daniel@gmail.com <mailto:rudi.daniel@gmail.com>> Date: Sep 11, 2015 1:42 PM Subject: WP4..first meet. To: "NPC SVG" <npcsvg@gmail.com <mailto:npcsvg@gmail.com>> Cc:
Hi Greg General scoping questions/ thoughts.
1) In light of today's WG4 meet, I am wondering how "up to date" the attached opinion (attachef pdf) is...as it relates to the task in hand.
Quote: "Currently, international human rights standards do not create binding legal obligations on U.S. corporations and state law fiduciary duty standards do not compel corporate Boards of Directors to act in furtherance of international human rights" end quote
ICANN however has made an commitment to respect international law in Article 4 of its Articles of Incorporation.
2) When I look at Ruggie, for example, I am asking myself, just what are we hoping to achieve?
At the ICANN bylaws level, are we to look towards some kind of due diligence or report process, ( annual review, which could be included in annual report) by which to monitor or access human rights impact of the corp. it's practices...on an ongoing basis..maybe functioning at the office of Ombudsman?
In the CCWP on ICANNs Corporate and Social Responsibility to Respect Human Rights (CCWP) we're currently working on two approaches: a human rights impact assessment at the beginning of a PDP and a CSR report which would also include a human rights impact assessment of ICANNs operations and practices. We hope to present a concrete proposal for this in Dublin. Best, Niels
Or some word set which holds the corp. to a set of (values)? And how are they to be monitored by whom?
RD
_______________________________________________ Wp4 mailing list Wp4@icann.org https://mm.icann.org/mailman/listinfo/wp4
- -- 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 iQEcBAEBCAAGBQJV+EyLAAoJEAi1oPJjbWjpKRgH+gKdxCWD9f6wgCuT1dDY27f+ MkWMHWsDHsi13e52NS6a2c+g3AN4Puq+xbQnr4y76T5VhzF4jM5+myyoQvDBKWki vyUVbdxa/Z8LWPgRnN/VNaqNMvW2+aXujr+rs91JkJ2pUmtVnJ0PtAdBPNFttv7K Jg5QuPsm1lzxyARZvaKKYYM9H5k5/hkblNi2mgdv6fXcWlD27r23zGZeu9CYrQrn 9JXcBNZz9mzJmYPraT6j/bnoEdGjO6LtcZ/ngBRrH/AvMaCUZ7oiQNwx/WdWgfy1 fsZpCk4zaLn9WIfmuYcrNrfB0GP66PU4S1AGWGcGjPNIZSo1yVZRjoJ2bhgjorQ= =wezI -----END PGP SIGNATURE-----