<div dir="ltr"><div class="gmail_default" style="font-family:verdana,sans-serif">There are a few points in this thread I would like to respond to.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">First, I volunteer for this subgroup.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Second, I agree with Keith's addition to the language, for the reasons stated above.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Third, I think the approach taken by the Co-Chairs is a good one, and I support that.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Fourth, there is one element in the newly proposed additional text which really must be changed. It is the list of "requirements," being presented as if these are agreed text:</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><font color="#0000ff"><span style="font-family:arial,sans-serif;font-size:12.8000001907349px">These discussions identified the following, non-exhaustive, list of accountability-related requirements :</span><br style="font-family:arial,sans-serif;font-size:12.8000001907349px"><span style="font-family:arial,sans-serif;font-size:12.8000001907349px">- the NTIA criteria to maintain the openness of the Internet, including free expression and the free flow of information</span><br style="font-family:arial,sans-serif;font-size:12.8000001907349px"><span style="font-family:arial,sans-serif;font-size:12.8000001907349px">- the need to avoid extending Icann's mission into content regulation</span><br style="font-family:arial,sans-serif;font-size:12.8000001907349px"><span style="font-family:arial,sans-serif;font-size:12.8000001907349px">- the importance of assessing the impact of Icann policies on Human rights</span></font><br></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">There was no agreement or consensus that these are "requirements." They are reasons offered during the discussions by those who wanted language (or particular language) included. I do not object to the first (because it's a statement of fact, and presented as such, and is not being used as an argument for particular text (to which I object)) or the third (because I agree with it, and it does not exclude other types of impact assessment). </div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">However, I have to object to the second "requirement." I've only seen this mentioned by one or two people and it has not even been seriously discussed on the list or on any call in relation to the Human Rights commitment. More to the point, I do not think that this point is a reason why we should have Human Rights language in the Bylaws and I object to the linkage being enshrined in this document. There are types of content control that clearly implicate Human Rights concerns and others that do not (indeed there are those that are consistent with and uphold fundamental Human Rights). ICANN's relationship to "content regulation" is not <i>per se</i> a Human Rights issue.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">If we had time, I might make a broad demand regarding this section, which would be followed by discussion and most likely a compromise. Since we don't have time, I will start with the compromise, which removes no text (even text I disagree with). It simply revises the introduction so there is no implication that this is an agreed list of "requirements":</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default"><font face="verdana, sans-serif" color="#0000ff">In these discussions, some participants raised the following as accountability-related reasons for including a commitment to fundamental Human Rights in the Bylaws: </font><span style="font-family:arial,sans-serif;font-size:12.8000001907349px">:</span><br style="font-family:arial,sans-serif;font-size:12.8000001907349px"></div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">I can live with this in the text without further comment. Please make this change. Thank you.</div><div class="gmail_default" style="font-family:verdana,sans-serif"><br></div><div class="gmail_default" style="font-family:verdana,sans-serif">Greg Shatan</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jul 31, 2015 at 1:22 PM, Carlos Raul Gutierrez <span dir="ltr"><<a href="mailto:crg@isoc-cr.org" target="_blank">crg@isoc-cr.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">++++++++++++1</div><div class="gmail_extra"><br clear="all"><div><div>Carlos Raúl Gutiérrez<br>ISOC Costa Rica Chapter<br>skype carlos.raulg<br><a href="tel:%2B506%208837%207176" value="+50688377176" target="_blank">+506 8837 7176</a> (New Phone number!!!!)<br>________<br>Apartado 1571-1000<br>COSTA RICA</div></div><div><div class="h5">
<br><div class="gmail_quote">On Fri, Jul 31, 2015 at 5:49 AM, Mathieu Weill <span dir="ltr"><<a href="mailto:mathieu.weill@afnic.fr" target="_blank">mathieu.weill@afnic.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Colleagues,<br>
<br>
As announced during our last call, the co-Chairs have reviewed where we are on this issue. Our group is tasked to work on the basis of consensus, and we have focused on assessing where this condition was met.<br>
<br>
It is our conclusion that :<br>
1) our group has achieved consensus on including a human rights related Commitment in Icann's Bylaws.<br>
2) no particular wording currently proposed achieved consensus.<br>
<br>
As a consequence, we propose to include into the public comment 2 report (in the Mission & Core value section, a draft is included below)<br>
- this assessment and a firm commitment to add a human rights related Commitment into Icann's Bylaws,<br>
- the underlying requirements expressed during the debate,<br>
- the concrete language proposals that were considered by our group so far, as examples<br>
<br>
Finally, given the strong momentum on the issue, both during the meeting and on list before and after, and taking into account the high level of complexity involved, we suggest to kick off ASAP a subgroup to further refine the requirements and assess potential options based on further studies of the current situation and "agreed-on" language.<br>
<br>
We thank you all for your understanding and commitment on this topic, as well as the extensive discussions both on list and during the calls about this.<br>
<br>
As a reminder, Minority statements filed until Saturday 12.00 UTC will be incorporated into the report to be published on Monday. Statements filed after this deadline will be published online but not incorporated into the report.<br>
<br>
Best regards,<br>
Leon, Thomas & Mathieu<br>
Co-chairs<br>
<br>
-----------------------------------------------<br>
NEW SUBSECTION IN 3A Mission, Commitmennts & Core Values<br>
<br>
Elaborating an Icann Commitment to Human Rights<br>
<br>
The CCWG-Accountability extensively discussed the opportunity to include into Icann Bylaws a Comittment related to Human Rights. The group commissioned a legal analysis of whether the termination of the IANA contract would induce changes into Icann's obligations with regards to Human Rights (LINK). While no significant issue was found to be directly linked to the termination of the IANA contract, the group acknowledged the recurring debates around the nature of Icann's accountability towards the respect of fundamental human rights.<br>
<br>
These discussions identified the following, non-exhaustive, list of accountability-related requirements :<br>
- the NTIA criteria to maintain the openness of the Internet, including free expression and the free flow of information<br>
- the need to avoid extending Icann's mission into content regulation<br>
- the importance of assessing the impact of Icann policies on Human rights<br>
<br>
Examples of language that could serve as a Commitment were as follows :<br>
- Within its mission and in its operations, ICANN will be committed to respect the fundamental human rights of the exercise of free expression and the free flow of information.<br>
- Within its mission and in it operations, ICANN will be committed to respect internationally recognized fundamental human rights.<br>
<br>
The group has achieved consensus on including a human rights related Commitment in Icann's Bylaws. However no particular wording currently proposed achieved consensus. Reiterating its commitment to elaborate concrete proposals as part of its mandate, the CCWG-Accountability is calling for comments on this approach and the underlying requirements.<br>
<br>
<br>
<br>
-- <br>
*****************************<br>
Mathieu WEILL<br>
AFNIC - directeur général<br>
Tél: <a href="tel:%2B33%201%2039%2030%2083%2006" value="+33139308306" target="_blank">+33 1 39 30 83 06</a><br>
<a href="mailto:mathieu.weill@afnic.fr" target="_blank">mathieu.weill@afnic.fr</a><br>
Twitter : @mathieuweill<br>
*****************************<br>
<br>
_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
</blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br></div></div>