<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Keith,<div class="">let me confirm that I heard no one suggesting ICANN’s mission should be broadened, while I have heard multiple statements confirming exactly what your understanding is, i.e. that the question of HR is related to ICANNs mission. </div><div class=""><br class=""></div><div class="">I have no reason to believe that the sub team will deviate from that understanding, but it is good of you ask for a clarification on the record.</div><div class=""><br class=""></div><div class="">Thomas </div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">Am 31.07.2015 um 17:24 schrieb Drazek, Keith <<a href="mailto:kdrazek@verisign.com" class="">kdrazek@verisign.com</a>>:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" class="">
<div dir="auto" class="">
<div class="">Thanks to the Co-Chairs. </div>
<div class=""><br class="">
</div>
<div class="">I support this approach with one caveat. I expect this is already understood but needs confirmation.</div>
<div class=""><br class="">
</div>
<div class="">Consistent with the CCWG discussions on the issue, when we present the issue to the public, it must be made clear that any such bylaw amendment is limited to ICANN's mission. It cannot be used as a tool to expand ICANN's mission, now or in the future.
Without this, we do NOT have consensus to include the reference. I assume this would fit under the proposed section:</div>
<div class=""><br class="">
</div>
<div class="">
<blockquote type="cite" class=""><font class=""><span style="background-color: rgba(255, 255, 255, 0);" class="">- the underlying requirements expressed during the debate,</span></font></blockquote>
<br class="">
</div>
<div class="">It could also be added here:</div>
<div class=""><br class="">
</div>
<div class="">
<blockquote type="cite" class=""><font class=""><span style="background-color: rgba(255, 255, 255, 0);" class="">- this assessment and a firm commitment to add a human rights related Commitment into Icann's Bylaws WITHIN ITS DEFINED MISSION</span></font></blockquote>
</div>
<div class=""><br class="">
</div>
<div class="">Thanks and regards,</div>
<div class="">Keith <br class="">
<br class="">
</div>
<div class=""><br class="">
On Jul 31, 2015, at 7:51 AM, Mathieu Weill <<a href="mailto:mathieu.weill@afnic.fr" class="">mathieu.weill@afnic.fr</a>> wrote:<br class="">
<br class="">
</div>
<blockquote type="cite" class="">
<div class=""><span class="">Dear Colleagues,</span><br class="">
<span class=""></span><br class="">
<span class="">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.</span><br class="">
<span class=""></span><br class="">
<span class="">It is our conclusion that :</span><br class="">
<span class="">1) our group has achieved consensus on including a human rights related Commitment in Icann's Bylaws.</span><br class="">
<span class="">2) no particular wording currently proposed achieved consensus.</span><br class="">
<span class=""></span><br class="">
<span class="">As a consequence, we propose to include into the public comment 2 report (in the Mission & Core value section, a draft is included below)</span><br class="">
<span class="">- this assessment and a firm commitment to add a human rights related Commitment into Icann's Bylaws,</span><br class="">
<span class="">- the underlying requirements expressed during the debate,</span><br class="">
<span class="">- the concrete language proposals that were considered by our group so far, as examples</span><br class="">
<span class=""></span><br class="">
<span class="">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.</span><br class="">
<span class=""></span><br class="">
<span class="">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.</span><br class="">
<span class=""></span><br class="">
<span class="">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.</span><br class="">
<span class=""></span><br class="">
<span class="">Best regards,</span><br class="">
<span class="">Leon, Thomas & Mathieu</span><br class="">
<span class="">Co-chairs</span><br class="">
<span class=""></span><br class="">
<span class="">-----------------------------------------------</span><br class="">
<span class="">NEW SUBSECTION IN 3A Mission, Commitmennts & Core Values</span><br class="">
<span class=""></span><br class="">
<span class="">Elaborating an Icann Commitment to Human Rights</span><br class="">
<span class=""></span><br class="">
<span class="">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.</span><br class="">
<span class=""></span><br class="">
<span class="">These discussions identified the following, non-exhaustive, list of accountability-related requirements :</span><br class="">
<span class="">- the NTIA criteria to maintain the openness of the Internet, including free expression and the free flow of information</span><br class="">
<span class="">- the need to avoid extending Icann's mission into content regulation</span><br class="">
<span class="">- the importance of assessing the impact of Icann policies on Human rights</span><br class="">
<span class=""></span><br class="">
<span class="">Examples of language that could serve as a Commitment were as follows :</span><br class="">
<span class="">- 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.</span><br class="">
<span class="">- Within its mission and in it operations, ICANN will be committed to respect internationally recognized fundamental human rights.</span><br class="">
<span class=""></span><br class="">
<span class="">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.</span><br class="">
<span class=""></span><br class="">
<span class=""></span><br class="">
<span class=""></span><br class="">
<span class="">-- </span><br class="">
<span class="">*****************************</span><br class="">
<span class="">Mathieu WEILL</span><br class="">
<span class="">AFNIC - directeur général</span><br class="">
<span class="">Tél: +33 1 39 30 83 06</span><br class="">
<span class=""><a href="mailto:mathieu.weill@afnic.fr" class="">mathieu.weill@afnic.fr</a></span><br class="">
<span class="">Twitter : @mathieuweill</span><br class="">
<span class="">*****************************</span><br class="">
<span class=""></span><br class="">
<span class="">_______________________________________________</span><br class="">
<span class="">Accountability-Cross-Community mailing list</span><br class="">
<span class=""><a href="mailto:Accountability-Cross-Community@icann.org" class="">Accountability-Cross-Community@icann.org</a></span><br class="">
<span class=""><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span><br class="">
</div>
</blockquote>
</div>
_______________________________________________<br class="">Accountability-Cross-Community mailing list<br class=""><a href="mailto:Accountability-Cross-Community@icann.org" class="">Accountability-Cross-Community@icann.org</a><br class="">https://mm.icann.org/mailman/listinfo/accountability-cross-community<br class=""></div></blockquote></div><br class=""></div></body></html>