<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: 'Times New Roman', sans-serif;"><div><div><div><br></div><div><div><font face="Book Antiqua"><i>On behalf of ICANN Legal</i></font></div><div><font face="Book Antiqua"><i><br></i></font></div><div><font face="Book Antiqua"><i>Karen Mulberry</i></font></div><div><span style="font-family: 'Times New Roman'; font-size: medium;">Multistakeholder</span><span style="font-family: 'Times New Roman'; font-size: medium;"> Strategy and Strategic Initiatives</span></div><div><span style="font-family: 'Times New Roman'; font-size: medium;">ICANN</span></div><div style="font-family: Calibri, sans-serif;"> </div><div style="font-family: Calibri, sans-serif;"><br></div></div></div></div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Samantha Eisner <<a href="mailto:Samantha.Eisner@icann.org">Samantha.Eisner@icann.org</a>><br><span style="font-weight:bold">Date: </span> Tuesday, September 20, 2016 at 11:01 AM<br><span style="font-weight:bold">To: </span> Karen Mulberry <<a href="mailto:karen.mulberry@icann.org">karen.mulberry@icann.org</a>><br><span style="font-weight:bold">Subject: </span> FW: [Ws2-hr] Proposed Agenda Call Sept 6 19:00 UTC<br></div><div><br></div><div><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;"><div><div><div>Can you please provide this to the HR subgroup?</div></div></div><span id="OLK_SRC_BODY_SECTION"><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;"><div><div><br></div><div><font face="Consolas,monospace"><br></font></div><div><font face="Consolas,monospace">Dear HR-Subgroup members,</font></div><div><font face="Consolas,monospace"><br></font></div><div><font face="Consolas,monospace">I</font><font face="Consolas,monospace"> understand that the question posed was "</font>'What is the rationale for the addition of 'core values' to the ICANN bylaws, and what are its legal and non-legal implications in your
opinion, especially for the human rights bylaw?”</div><div><br></div><div>The Core Values have historically been part of the ICANN Bylaws, introduced after the ICANN evolution and reform effort in 2002, <a href="https://www.icann.org/en/about/governance/bylaws/bylaws-15dec02-en.htm">https://www.icann.org/en/about/governance/bylaws/bylaws-15dec02-en.htm</a>.
From 2002 through the Bylaws as they exist today, the Core Values remained unchanged, with the following as guidance for the application of Core Values: "These core values are deliberately expressed in very general terms, so that they may provide useful and
relevant guidance in the broadest possible range of circumstances. Because they are not narrowly prescriptive, the specific way in which they apply, individually and collectively, to each new situation will necessarily depend on many factors that cannot be
fully anticipated or enumerated; and because they are statements of principle rather than practice, situations will inevitably arise in which perfect fidelity to all eleven core values simultaneously is not possible. Any ICANN body making a recommendation
or decision shall exercise its judgment to determine which core values are most relevant and how they apply to the specific circumstances of the case at hand, and to determine, if necessary, an appropriate and defensible balance among competing values.”</div><div><br></div><div>With the Bylaws drafted to implement WS1, the CCWG recommended the development of both Commitments as well as Core Values, for which the balancing test has changed. Some of the items that were previously Core Values are now expressed as commitments. The
balancing test now requires that all of the commitments be met, while Core Values still are dependent upon situations and can be balanced amongst each other.</div><div><br></div><div>The inclusion of the Human Rights commitment as a Core Value, which was expressly required in Annex 6 of the WS1 report, assures that it is an item that is considered while ICANN is performing its Mission. The implication of this is strong, particularly
where the FOI considers how to guide the interpretation of this obligation. Of course, there are already legal obligations that are tethered to human rights obligations (for example, observing laws against human trafficking) that ICANN is already following. </div><div><br></div><div>Given the long-standing nature of the Core Values section of the ICANN Bylaws, this is a key tool in guiding ICANN’s operations. They are part of a near 15-year history of ICANN acting within its Mission.</div><div><br></div><div>If there are more specific questions that you have on this topic, please let us know. </div><div><br></div><div><br></div><div> </div><div><font face="Consolas,monospace">— </font></div><div><font face="Consolas,monospace">Samantha Eisner</font></div><div><font face="Consolas,monospace">Deputy General Counsel, ICANN</font></div><div><font face="Consolas,monospace">12025 Waterfront Drive, Suite 300</font></div><div><font face="Consolas,monospace">Los Angeles, California 90094</font></div><div><font face="Consolas,monospace">USA</font></div><div><font face="Consolas,monospace">Direct Dial: +1 310 578 8631</font></div><div><font face="Consolas,monospace"><br></font></div><div><font face="Consolas,monospace"><br></font></div><div style="font-family: Consolas, monospace; font-size: 12px;"><br></div></div><div style="font-family: Consolas, monospace; font-size: 12px;"><br></div><div style="font-family: Consolas, monospace; font-size: 12px;">On 9/6/16, 11:47 AM, "<a href="mailto:ws2-hr-bounces@icann.org">ws2-hr-bounces@icann.org</a> on behalf of Niels ten Oever" <<a href="mailto:ws2-hr-bounces@icann.org">ws2-hr-bounces@icann.org</a>
on behalf of <a href="mailto:lists@nielstenoever.net">lists@nielstenoever.net</a>> wrote:</div><div style="font-family: Consolas, monospace; font-size: 12px;"><br></div><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="font-family: Consolas, monospace; font-size: 12px; border-left-color: rgb(181, 196, 223); border-left-width: 5px; border-left-style: solid; padding: 0px 0px 0px 5px; margin: 0px 0px 0px 5px;"><div>Dear Jorge,</div><div><br></div><div>The question has been forwarded to ICANN legal and we are awaiting a</div><div>response.</div><div><br></div><div>Best,</div><div><br></div><div>Niels</div><div><br></div><div>On 09/07/2016 03:22 AM, <a href="mailto:Jorge.Cancio@bakom.admin.ch">Jorge.Cancio@bakom.admin.ch</a> wrote:</div><blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;"><div>Dear Niels</div><div></div><div> </div><div></div><div>May I kindly request clarification on the status of our inquiry into the</div><div>(legal) effects that the HR commitment we are talking about is a "core</div><div>value"?</div><div></div><div> </div><div></div><div>According to the new Bylaws "core values" are “guidance” (“should also</div><div>guide the decisions and actions of ICANN…”) and are subject to a</div><div>specific balancing and interpretation clause:</div><div></div><div> </div><div></div><div>"(c) The Commitments and Core Values are intended to apply in the broadest</div><div></div><div>possible range of circumstances. The Commitments reflect ICANN’s</div><div></div><div>fundamental compact with the global Internet community and are intended to</div><div></div><div>apply consistently and comprehensively to ICANN’s activities. The specific</div><div></div><div>way in which Core Values are applied, individually and collectively, to any</div><div></div><div>given situation may depend on many factors that cannot be fully anticipated</div><div></div><div>or enumerated. Situations may arise in which perfect fidelity to all Core</div><div></div><div>Values simultaneously is not possible. Accordingly, in any situation where</div><div></div><div>one Core Value must be balanced with another, potentially competing Core</div><div></div><div>Value, the result of the balancing must serve a policy developed through the</div><div></div><div>bottom-up multistakeholder process or otherwise best serve ICANN’s Mission."</div><div></div><div> </div><div></div><div>I feel this is quite relevant for our discussions, as it sets the frame</div><div>of the effect of the new HR "core value".</div><div></div><div> </div><div></div><div>Best and looking forward to your guidance and apologies if I have missed</div><div>any relevant message on this issue</div><div></div><div> </div><div></div><div>Jorge</div><div></div><div> </div><div></div><div>-----Ursprüngliche Nachricht-----</div><div>Von: <a href="mailto:ws2-hr-bounces@icann.org">ws2-hr-bounces@icann.org</a> [<a href="mailto:ws2-hr-bounces@icann.org">mailto:ws2-hr-bounces@icann.org</a>] Im</div><div>Auftrag von Niels ten Oever</div><div>Gesendet: Dienstag, 6. September 2016 00:19</div><div>An: <a href="mailto:ws2-hr@icann.org">ws2-hr@icann.org</a></div><div>Betreff: [Ws2-hr] Proposed Agenda Call Sept 6 19:00 UTC</div><div></div><div> </div><div></div><div>Dear all,</div><div></div><div> </div><div></div><div>Please find underneath and attached the proposed agenda for our call of</div><div>Sept 6 19:00 UTC.</div><div></div><div> </div><div></div><div>Also please find attached a rather advanced version of the document</div><div>mentioned under agenda point 2, the summary of the Human Rights work</div><div>under Workstream 1.</div><div></div><div> </div><div></div><div>1. Administrivia</div><div></div><div>Roll call, absentees, SoIs, etc</div><div></div><div>2. Discussion on: the Summary on what was agreed and discussed on human</div><div>rights during WS1</div><div><a href="https://docs.google.com/document/d/1rwpw9aSAqboRO2_rNkjMVJPOmYwmdr5B1_M_aNMoZb4/edit?usp=sharing">https://docs.google.com/document/d/1rwpw9aSAqboRO2_rNkjMVJPOmYwmdr5B1_M_aNMoZb4/edit?usp=sharing</a></div><div></div><div>3. Discussion on: Concerns on possible impacts of Human Rights bylaw and</div><div>FoI</div><div><a href="https://docs.google.com/document/d/1KcKGRJjuhKEzCh2AZ8PPR_MofOQFBN8CMuJqTG_h9h4/edit?usp=sharing">https://docs.google.com/document/d/1KcKGRJjuhKEzCh2AZ8PPR_MofOQFBN8CMuJqTG_h9h4/edit?usp=sharing</a></div><div></div><div>4. Discussion on FoI draft document</div><div></div><div><a href="https://docs.google.com/document/d/1emqmzyB9_0vm6oKxhIWZ47L7lxcFKUBHVnkBYUOsA2Q/edit">https://docs.google.com/document/d/1emqmzyB9_0vm6oKxhIWZ47L7lxcFKUBHVnkBYUOsA2Q/edit</a></div><div></div><div>5. AOB</div><div></div><div> </div><div></div><div>ICANN staff informed me that they are working on providing more real</div><div>time collaboration methods, but currently they do not offer such</div><div>services. So until that time I am afraid we are stuck with Google Docs.</div><div></div><div> </div><div></div><div>As always feel free to suggest addition or changes to the points above.</div><div></div><div> </div><div></div><div> </div><div></div><div>Best,</div><div></div><div> </div><div></div><div>Niels</div><div></div><div>--</div><div></div><div>Niels ten Oever</div><div></div><div>Head of Digital</div><div></div><div> </div><div></div><div>Article 19</div><div></div><div>www.article19.org <<a href="http://www.article19.org">http://www.article19.org</a>></div><div></div><div> </div><div></div><div>PGP fingerprint 8D9F C567 BEE4 A431 56C4</div><div></div><div> 678B 08B5 A0F2 636D 68E9</div><div></div></blockquote><div><br></div><div>-- </div><div>Niels ten Oever</div><div>Head of Digital</div><div><br></div><div>Article 19</div><div>www.article19.org</div><div><br></div><div>PGP fingerprint 8D9F C567 BEE4 A431 56C4</div><div> 678B 08B5 A0F2 636D 68E9</div><div>_______________________________________________</div><div>Ws2-hr mailing list</div><div><a href="mailto:Ws2-hr@icann.org">Ws2-hr@icann.org</a></div><div><a href="https://mm.icann.org/mailman/listinfo/ws2-hr">https://mm.icann.org/mailman/listinfo/ws2-hr</a></div><div><br></div></blockquote></div></div></span></div></div></span></body></html>