<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;">
<div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
Per Brett’s request for a recap:</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;">
GAC’s Dublin Communique included this txt on ST 18. ( The only surprise here was the highlighted text)</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;">
<div><i style="font-family: Calibri; font-size: 12pt;">"The discussions on Stress Test 18 have helped the GAC to have a better understanding of the different views on the issue. In assessing the different rationales presented so far related to Stress Test 18,
the GAC considered: </i></div>
</blockquote>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<ul style="font-family: 'Segoe UI', Helvetica, Arial, sans-serif;">
<ul style="font-family: 'Segoe UI', Helvetica, Arial, sans-serif;">
<li style="font-size: 12pt; font-family: Symbol;">
<p><span style="font-size: 12pt; font-family: Calibri;"><i>The need that each and every Advisory Committee ensures that the advice provided is clear and reflects the consensus view of the Committee;</i></span></p>
</li><li style="font-size: 12pt; font-family: Symbol;">
<p><span style="font-size: 12pt; font-family: Calibri;"><i>The need that each and every Advisory Committee should preserve its own autonomy in its definition of consensus;</i></span></p>
</li><li style="font-size: 12pt; font-family: Symbol;">
<p><span style="font-size: 12pt; font-family: Calibri;"><i>The value the Board attributes to receiving consensus advice;</i></span></p>
</li><li style="font-size: 12pt; font-family: Symbol;">
<p><span style="background-color: rgb(255, 255, 0);"><span style="font-size: 12pt; font-family: Calibri;"><i>The recommendation of the BGRI WG, as reiterated by the ATRT2, to set the threshold </i></span><i style="font-family: Calibri; font-size: 12pt;">for
the ICANN Board to reject GAC advice to a 2/3 majority voting, consistent with the threshold established for rejection of ccNSO and GNSO PDP recommendations.</i></span></p>
</li></ul>
</ul>
</div>
<div><font face="Calibri,sans-serif">Pedro</font><span style="color: rgb(0, 0, 0); font-family: Calibri; font-size: 16px;"> Ivo Ferraz da Silva (Brazil GAC) suggested text to address points 1-3 in the communique, with a new </span><font face="Calibri">general
section that applies to all ACs:</font></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<span style="font-family: Calibri;"><br>
</span></div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><span id="OLK_SRC_BODY_SECTION">Where the ICANN Board is obliged to pay due deference to advice from Advisory Committees and where that advice, if not followed, requires finding mutually agreed
solutions for implementation of that advice, the Advisory Committee will make every effort to ensure that the advice provided is clear and reflects the consensus view of the committee. In this context, each Advisory Committee has the right to determine its
particular definition of consensus.</span>
<div><br>
</div>
</blockquote>
<div>I offered an alternative to avoid use of the term “due deference” since that term is not defined, and might imply this obligation extends to all ACs. And my alternative does not explicitly state that an AC can define its own consensus rule, since that
is implied already. </div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div> </div>
<span id="OLK_SRC_BODY_SECTION">
<div>For any Advisory Committee where the Board is required to seek a mutually acceptable solution if the Board does not follow that Committee’s advice, the Board should not be required to arbitrate among divergent views within that Committee. Therefore, the
Board shall have no obligation to seek a mutually acceptable solution for Advisory Committee advice that was not supported by consensus among Committee members.</div>
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div><br>
</div>
</blockquote>
</span></blockquote>
<div>I feel we are very close, and could merge these two alternatives into one. </div>
<div><br>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<div>Second, Pedro added the GAC request to require "more than 2/3 board vote” to reject GAC advice. That has not been previously discussed in the CCWG, and could be regarded as a bid to enhance the weight of GAC’s advice. </div>
<div><br>
</div>
<div>As noted above, GAC could change its consensus rule to a much lower threshold than it uses today, “the absence of any formal objection”. Yet, a board rejection would trigger the requirement to seek a mutually acceptable solution, even if a significant
minority of sovereign governments did not support the GAC advice.</div>
<div><br>
</div>
<div>I believe that a new 2/3 rule would have to be balanced — by a requirement that any such GAC advice was adopted in the absence of any formal objection. As you know, this is the GAC’s present rule for decision-making, so this does not impose any change
on the GAC.</div>
<div><br>
</div>
<div>Finally, we’re interested to know the GAC’s reaction to the rationale we provided for Stress Test 18 in Dublin. I’ve attached revised text for ST 18 that reflects the updated rationale, as approved by Stress Test working party (before Dublin) This text
makes no mention of government ‘capture’ and removes the offending language (with my apologies, once again). </div>
<div><br>
</div>
<div>The attached text is what would go into our 3rd report, pending new text that would be supported by CCWG, GAC, the ICANN Board, and NTIA— which has repeatedly said that the bylaws change for ST18 is a requirement for the transition.</div>
<div><br>
</div>
<div>—Steve</div>
<div><br>
</div>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<div id="MAC_OUTLOOK_SIGNATURE"></div>
</div>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<div style="font-family:Calibri; font-size:12pt; 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:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a>> on behalf of "Schaefer, Brett" <<a href="mailto:Brett.Schaefer@heritage.org">Brett.Schaefer@heritage.org</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, November 12, 2015 at 6:09 PM<br>
<span style="font-weight:bold">To: </span>Paul Rosenzweig <<a href="mailto:paul.rosenzweig@redbranchconsulting.com">paul.rosenzweig@redbranchconsulting.com</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>" <<a href="mailto:accountability-cross-community@icann.org">accountability-cross-community@icann.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [CCWG-ACCT] Stress Test 18: bylaw amendment suggestion<br>
</div>
<div><br>
</div>
<div>
<div>
<div>Would be useful to see the suggested changes laid out again, we've had a hundred emails in the past two days.</div>
<div><br>
</div>
<div><br>
</div>
</div>
</div>
</span>
</body>
</html>