<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: Calibri, sans-serif;"><div>Dear all, </div><div><br></div><div>Here attached is the updated Stress Tests document for the freeze. </div><div><br></div><div>Best, </div><div>Grace</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> <<a href="mailto:acct-staff-bounces@icann.org">acct-staff-bounces@icann.org</a>> on behalf of Steve DelBianco <<a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a>><br><span style="font-weight:bold">Date: </span> Thursday, July 30, 2015 at 4:58 PM<br><span style="font-weight:bold">To: </span> Accountability Cross Community <<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>><br><span style="font-weight:bold">Cc: </span> ACCT-Staff <<a href="mailto:acct-staff@icann.org">acct-staff@icann.org</a>><br><span style="font-weight:bold">Subject: </span> [Acct-Staff] Revised draft for Stress Test 18 and bylaws change (after our second call today)<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;"><div><p class="MsoNormal" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 11pt; margin: 6pt 0in 12pt; text-indent: 0in;"><span id="OLK_SRC_BODY_SECTION" style="font-family: Calibri, sans-serif; font-size: 16px;"></span><span style="font-family: Calibri, sans-serif; font-size: 16px;"></span></p><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-family: Calibri, sans-serif;"><div><div><div>This is updated per discussion we just had on the CCWG call, and in subsequent emails and chats revealing confusion about the text. </div><div><br></div><div>I also reviewed existing GAC <a href="https://gacweb.icann.org/display/gacweb/GAC+Operating+Principles">
Operating Principles</a>, and the GAC does not actually define “consensus”. Instead, they describe a process for providing advice to ICANN. </div></div></div><div><br></div><div>New text is below and attached (yellow text shows the 2 changes from our 3-May draft proposal): </div><div><br></div></div></div><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="MsoNormal" style="margin: 6pt 0in 12pt; text-indent: 0in;"><font face="Helvetica"><span style="font-size: 15px;">The CCWG-Accountability proposes a response to Stress Test 18 to amend the ICANN Bylaws such that only consensus advice would trigger
the obligation to try to find a mutually acceptable solution. The proposal is to amend ICANN Bylaws, Article XI Section 2 clause j as seen below. (Addition is
<b><u>bold and underlined</u></b>) Clause k is also shown for completeness but is not being amended.</span></font></p><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><p class="MsoNormal" style="margin: 6pt 0in 12pt; text-indent: 0in;"><font face="Helvetica"><span style="font-size: 15px;">j: The advice of the Governmental Advisory Committee on public policy matters shall be duly taken into account, both in the formulation
and adoption of policies. In the event that the ICANN Board determines to take an action that is not consistent with the Governmental Advisory Committee advice, it shall so inform the Committee and state the reasons why it decided not to follow that advice.
<u>With respect to Governmental Advisory Committee advice that is supported by consensus,</u> the Governmental Advisory Committee and the ICANN Board will then try, in good faith and in a timely and efficient manner, to find a mutually acceptable solution.
</span></font></p><p class="MsoNormal" style="margin: 6pt 0in 12pt; text-indent: 0in;"><font face="Helvetica"><span style="text-indent: 0in; font-size: 15px;"></span></font></p><p class="MsoNormal" style="margin: 6pt 0in 12pt; text-indent: 0in;"><font face="Helvetica"><span style="font-size: 15px;">k: If no such solution can be found, the ICANN Board will state in its final decision the reasons why the Governmental Advisory Committee
advice was not followed, and such statement will be without prejudice to the rights or obligations of Governmental Advisory Committee members with regard to public policy issues falling within their responsibilities.</span></font></p></blockquote><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;"><span style="font-size: 11pt; text-indent: 0in; font-family: Helvetica;">Note that the proposed Bylaws change for Stress Test 18 does not interfere with the GAC’s method of decision-making. If the GAC decided to adopt advice by majority voting or methods other
than today’s consensus process, ICANN would still be obligated to give GAC advice due consideration: “advice shall be duly taken into account, both in the formulation and adoption of policies.” </span></div><p class="MsoNormal" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 11pt; margin: 6pt 0in 12pt; text-indent: 0in;"><o:p></o:p></p><p class="MsoNormal" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 11pt; margin: 6pt 0in 12pt; text-indent: 0in;">
Moreover, ICANN would still have to explain why GAC advice was not followed: “In the event that the ICANN Board determines to take an action that is not consistent with the Governmental Advisory Committee advice, it shall so inform the Committee and state
the reasons why it decided not to follow that advice.”<o:p></o:p></p><p class="MsoNormal" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 11pt; margin: 6pt 0in 12pt; text-indent: 0in;">
The only effect of this Bylaws change is to limit the kind of advice where ICANN is obligated to “try, in good faith and in a timely and efficient manner, to find a mutually acceptable solution”. That delicate and sometimes difficult consultation requirement
would only apply for GAC advice that was approved by consensus<span style="background-color: yellow;">. <o:p></o:p></span></p><p class="MsoNormal" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 11pt; margin: 6pt 0in 12pt; text-indent: 0in;"><span style="background-color: yellow;">The GAC currently uses the following consensus rule for its decisions: “<i>consensus is understood to mean the practice of adopting decisions by general agreement in the absence of any formal objection</i>.” The proposed
bylaws change above recognizes that GAC may at its discretion amend its Operating Principle 47 regarding "Provision of Advice to the ICANN Board". </span><o:p></o:p></p><p class="MsoNormal" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 11pt; margin: 6pt 0in 12pt; text-indent: 0in;">
NTIA gave specific requirements for this transition, including advice that Stress Test 18 is a direct test of the requirement to avoid significant expansion of the role of governments in ICANN decision-making. The proposed Bylaws change is therefore an important
part of the community’s proposal.<o:p></o:p></p><p class="MsoNormal" style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 11pt; margin: 6pt 0in 12pt; text-indent: 0in;"><span style="background-color: yellow;">It is noted that GAC Representatives are continuing to discuss the proposal.</span><i><o:p></o:p></i></p></blockquote></div><blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;"><span style="background-color: yellow;"><br></span></div></blockquote><div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;"><div id="MAC_OUTLOOK_SIGNATURE"></div></div></div></div></span></body></html>