<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body 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><font face="-webkit-standard" style="font-family: Calibri, sans-serif;">Greg </font><font face="Calibri,sans-serif">—</font><font face="Calibri,sans-serif" style="font-family: -webkit-standard;"> here is what </font>I<font face="-webkit-standard" style="font-family: Calibri, sans-serif;"> proposed
on first </font><font face="Calibri,sans-serif">reading</font><font face="-webkit-standard"><font face="Calibri,sans-serif"> for Rec 11 (Stress Test 18) on today</font>’<font face="Calibri,sans-serif">s call.</font></font></div>
<div><font face="-webkit-standard"><font face="Calibri,sans-serif"><br>
</font></font></div>
<div><font face="-webkit-standard"><font face="Calibri,sans-serif">1. To address concerns that AC advice should </font></font><u style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">require</u><font face="Calibri,sans-serif" style="color: rgb(0, 0, 0); font-family: -webkit-standard; font-size: 16px;"> accompanying
rationale. </font><span style="font-family: Calibri, sans-serif; font-size: 16px;">Add this to supplemental draft, Rec 11 and Annex 11:</span></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<blockquote style="color: rgb(0, 0, 0); font-family: -webkit-standard; font-size: 16px; margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div style="font-family: Calibri, sans-serif;">Insert a requirement in ICANN Bylaws Article XI, Section 1 (regarding all Advisory Committees), such that Formal advice of Advisory Committees must be accompanied by rationale for such advice.</div>
</blockquote>
<blockquote style="color: rgb(0, 0, 0); font-family: -webkit-standard; font-size: 16px; margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div style="font-family: Calibri, sans-serif;"><br>
</div>
</blockquote>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
2. To address IPC concern that Rec 11 might have the unintended consequences of: “requiring a mandatory vote and creating the impression that any GAC advice that is not rejected by the Board is binding on ICANN.” Add this to supplemental draft, Rec 11 and
Annex 11:</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<blockquote style="color: rgb(0, 0, 0); font-family: -webkit-standard; font-size: 16px; margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div style="font-family: Calibri, sans-serif;">This recommendation is intended to limit the conditions under which the ICANN board must enter a try to find a mutually acceptable solution. This recommendation does not create any new obligations for ICANN board
to consider and/or vote on GAC advice, relative to the bylaws in effect prior to the IANA transition. This recommendation does not create any new assumption that ICANN is bound to implement any advice that is not rejected by the board, relative to the bylaws
in effect prior to the IANA transition.</div>
<div style="font-family: Calibri, sans-serif;"><br>
</div>
<div style="font-family: Calibri, sans-serif;"><br>
</div>
</blockquote>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
3. To address registry concern about consistent with ICANN bylaws. Add this to supplemental draft, Rec 11 and Annex 11:</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<blockquote style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px; margin: 0px 0px 0px 40px; border: none; padding: 0px;">
While the GAC is not restricted as to the advice it can offer to ICANN, it is clear that ICANN may not take action that is inconsistent with its Bylaws. The empowered community will have standing to bring an IRP to challenge whether a board action or inaction
that is inconsistent with its bylaws, even if the board acted on GAC advice.</blockquote>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
Also, when we display Rec 11 in Adobe and in our supplemental draft, we should always highlight the new text being proposed:</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<blockquote style="color: rgb(0, 0, 0); font-family: -webkit-standard; font-size: 16px; margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div style="font-family: Calibri, sans-serif;">ICANN Bylaws Article XI, Section 2: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><b>Any Governmental Advisory Committee
advice approved by a full Governmental Advisory Committee consensus, understood to mean the practice of adopting decisions by general agreement in the absence of any formal objection, may only be rejected by a vote of 2/3of the Board, and</b></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.</div>
</blockquote>
</body>
</html>