<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">All the more reason that we need to be clear about what "applicable law" means and how it applies in this context.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 19, 2016 at 2:48 PM, Nigel Roberts <span dir="ltr"><<a href="mailto:nigel@channelisles.net" target="_blank">nigel@channelisles.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Paul<br>
<br>
This is where you and I part company.<br>
<br>
On a strict construction, there is no applicable law which says ICANN has to respect any of the human rights. The law just says "ICANN has to follow the law" (e.g of California).<br>
<br>
Of course this may include obligations that the the State (i.e the United States) and the state (i.e. California) place on private parties as a result of its own obligation to respect human rights, but this does not engage ICANN with fundamental rights PER SE, but with the domestic implementation thereof.<br>
<br>
Avri had it right.<br>
<br>
She said that 'all this ACTUALLY means is that ICANN must follow the law', if I am not misquoting.<br>
<br>
<br>
<br>
HOWEVER, as I have repeatedly reminded everyone, and I am beginning to feel that the lack of dealing with it is intentional . . .<br>
<br>
whilst true, (and the reason I argued strongly against that formulation in WS1) that is not /necessarily/ the end of the story.<br>
<br>
'Applicable law' can include international law (which does not normally bind domestically) that ICANN voluntarily agrees to be bound by.<br>
<br>
And ICANN has, it appears, done so.<br>
<br>
The analysis I prefer, which engages ICANN squarely in fundamental rights obligations is that of the learned Panellist, Judge Schwbel in ICM Registry Inc -v-ICANN (ICDR Case No. 50 117 T 00224 08) in paragraphs 57-58.<br>
<br>
>From which it is clear that ICANN's founders have bound ICANN in law (i.e. California law) to respect international law.<br>
<br>
Unless someone wishes to advance a different legal authority for "applicable law".<br>
<br>
<br>
<br>
On 19/10/16 19:13, Paul McGrady wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks Niels. By saying the group has reached some sort of consensus that<div><div class="h5"><br>
certain Ruggie principals may apply, you are already including overviews of<br>
the various views of the members of the group. I, for one, still have no<br>
idea if any of the Ruggie principals would apply since I do not know whether<br>
or not they are already subsumed by or preempted by California State law. I<br>
hope your summary will be complete enough to include that at least one<br>
person in the group believes we out to start with what applicable law is<br>
already in place before we begin opining on whether or not third party<br>
sources should govern ICANN behavior, since the bylaw makes it clear that<br>
all of our work should end up with a product that is within applicable law.<br>
We simply have no hope at hitting the target if we insist on having blinders<br>
on. Not telling the Plenary CCWG that we have decided to put on blinders is<br>
an important thing for them to know so that they can either tell us to take<br>
off the blinders and look first at what human rights requirements already<br>
exist under applicable law or they can consent to us trying to put the<br>
puzzle together in the dark.<br>
<br>
As far as my suggestions for next steps, they remain the same as the first<br>
(among many) times I have brought up this subject. Ask ICANN Legal what<br>
Human Rights laws already apply to the organization. They have been<br>
operating in California for some time now and they already know the answer<br>
to this question.<br>
<br>
Best,<br>
Paul<br>
<br>
<br>
Paul D. McGrady, Jr.<br>
<a href="mailto:policy@paulmcgrady.com" target="_blank">policy@paulmcgrady.com</a><br>
<br>
<br>
<br>
-----Original Message-----<br>
From: Niels ten Oever [mailto:<a href="mailto:lists@nielstenoever.net" target="_blank">lists@nielstenoever.ne<wbr>t</a>]<br>
Sent: Wednesday, October 19, 2016 11:24 AM<br>
To: Paul McGrady <<a href="mailto:policy@paulmcgrady.com" target="_blank">policy@paulmcgrady.com</a>>; <a href="mailto:ws2-hr@icann.org" target="_blank">ws2-hr@icann.org</a><br>
Cc: <a href="mailto:thomas@rickert.net" target="_blank">thomas@rickert.net</a><br>
Subject: Re: [Ws2-hr] Report to CCWG<br>
<br>
Hi Paul,<br>
<br>
I am a bit hesitant to add an overview of different views of members of the<br>
group, but I will try.<br>
<br>
In the meantime I would still be very interested to hear from you how you<br>
think we could approach this, with the limited resources of our group and in<br>
conjunction with the current understanding of applicable law we're working<br>
on.<br>
<br>
Best,<br>
<br>
Niels<br>
<br>
On 10/19/2016 05:31 PM, Paul McGrady wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks Niels. I would like for your summary to include notice that I<br>
have consistently called for us to evaluate what human rights<br>
principles already apply to ICANN as a result of applicable California<br>
law in order to get a baseline to begin a gap analysis, but that the<br>
request has not been acted upon by the group. Thanks.<br>
<br>
Best,<br>
Paul<br>
<br>
<br>
Paul D. McGrady, Jr.<br>
<a href="mailto:policy@paulmcgrady.com" target="_blank">policy@paulmcgrady.com</a><br>
<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:ws2-hr-bounces@icann.org" target="_blank">ws2-hr-bounces@icann.org</a> [mailto:<a href="mailto:ws2-hr-bounces@icann.org" target="_blank">ws2-hr-bounces@icann.o<wbr>rg</a>] On<br>
Behalf Of Niels ten Oever<br>
Sent: Tuesday, October 18, 2016 11:24 AM<br>
To: <a href="mailto:ws2-hr@icann.org" target="_blank">ws2-hr@icann.org</a><br>
Subject: [Ws2-hr] Report to CCWG<br>
<br>
Dear all,<br>
<br>
I hope this email finds you well. Coming Friday is the deadline for me<br>
to report to the CCWG Plenary on the progress of our Subgroup. I<br>
drafted the text underneath. Your input is more than welcome before<br>
Friday, when I will submit it to the CCWG co-chairs.<br>
<br>
All your input is of course very much appreciated.<br>
<br>
Best,<br>
<br>
Niels<br>
<br>
1. Executive Summary<br>
The CCWG WS2 Human Rights Subgroup has documented the historical<br>
context of the discussions on ICANNs human rights bylaw, which<br>
together with the CCWG report (especially Annex 6 and 12) form it's<br>
scope of discussion, with a Framework of Interpretation of the Human<br>
</blockquote>
Rights Bylaw as intended output.<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The subgroup is currently preparing a Framework of Interpretation<br>
which in due time will be presented to the CCWG plenary for discussion.<br>
<br>
2. Description of the Issue<br>
2.1 Current State of Play<br>
The CCWG WS2 Human Rights Subgroup started of with providing an<br>
overview of the discussions and agreements as they were made during<br>
CCWG Workstream 1 [0]. Subsequently the Subgroup has analyzed the UN<br>
Guiding Principles on Business and Human Rights (UNGPs), and their<br>
relevance and applicability for ICANN. While there was consensus that<br>
some principles were relevant for the development for a Framework of<br>
Interpretation (such as 13a and 15a), it was also recognized that the<br>
UNGPs have not been designed with an organization like ICANN in mind.<br>
Therefore a drafting team is currently iteratively designing a draft<br>
Framework of Interpretation which is being discussed in weekly calls.<br>
It is expected, that at this rate, the subgroup will be able to achieve<br>
</blockquote>
the set milestones.<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
2.2 Supplemental Report<br>
See [0]<br>
<br>
3 Recommendation<br>
3.1 Requirements for Recommendation<br>
We haven't reached consensus on a recommendation yet.<br>
<br>
3.2 Rationale for Recommendation<br>
We haven't reached consensus on a recommendation yet.<br>
<br>
[0]<br>
<a href="https://docs.google.com/document/d/1rwpw9aSAqboRO2_rNkjMVJPOmYwmdr5B1_" rel="noreferrer" target="_blank">https://docs.google.com/docume<wbr>nt/d/1rwpw9aSAqboRO2_rNkjMVJPO<wbr>mYwmdr5B1_</a><br>
M_aNMo<br>
Zb4/edit?usp=sharing<br>
<br>
--<br>
Niels ten Oever<br>
Head of Digital<br>
<br>
Article 19<br>
<a href="http://www.article19.org" rel="noreferrer" target="_blank">www.article19.org</a><br>
<br>
PGP fingerprint 8D9F C567 BEE4 A431 56C4<br>
678B 08B5 A0F2 636D 68E9<br>
______________________________<wbr>_________________<br>
Ws2-hr mailing list<br>
<a href="mailto:Ws2-hr@icann.org" target="_blank">Ws2-hr@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ws2-hr" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/ws2-hr</a><br>
<br>
</blockquote>
<br>
--<br>
Niels ten Oever<br>
Head of Digital<br>
<br>
Article 19<br>
<a href="http://www.article19.org" rel="noreferrer" target="_blank">www.article19.org</a><br>
<br>
PGP fingerprint 8D9F C567 BEE4 A431 56C4<br>
678B 08B5 A0F2 636D 68E9<br>
<br>
______________________________<wbr>_________________<br>
Ws2-hr mailing list<br>
<a href="mailto:Ws2-hr@icann.org" target="_blank">Ws2-hr@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ws2-hr" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/ws2-hr</a><br>
<br>
</div></div></blockquote><div class="HOEnZb"><div class="h5">
______________________________<wbr>_________________<br>
Ws2-hr mailing list<br>
<a href="mailto:Ws2-hr@icann.org" target="_blank">Ws2-hr@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ws2-hr" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/l<wbr>istinfo/ws2-hr</a><br>
</div></div></blockquote></div><br></div>