<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>Placing this on top of your inboxes so you can review before Helsinki meetings on Sunday 26-Jun.</div>
<div><br>
</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: 16px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>Below is the note I circulated to the CCWG-Accountability on 26-May, after which 2 responses were given:</div>
</div>
</div>
</div>
</div>
</span>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div>1. Carlos Raúl Gutiérrez replied by suggesting we ask ICANN to do a progress report on implementation of ATRT2 recommendations. (my reply: yes)</div>
<div><br>
</div>
<div>2. Sivasubramanian asked if ATRT3 could be constituted now and have oversight over WS2 deliberations. (my reply: That is not the way WS2 was proposed in the CCWG report and is not how we designed the new bylaws, so this could not easily become a formal
arrangement. Sure, ATRT3 members could participate in WS2 accountability projects, but the real question is whether ATRT3 would allow WS2 to complete its work before the review team began theirs) </div>
<div><br>
</div>
</blockquote>
<div>Again, the Work Stream 2 bylaws give the community more leverage than ATRT would, when it comes to adopting accountability enhancements that might be resisted by ICANN board and legal. So the question is whether to allow WS2 to proceed on its accountability
tasks, or defer to ATRT3 to address them.</div>
<div><br>
</div>
<div>--Steve</div>
<div><br>
</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: 16px; font-family: Calibri, sans-serif;">
<div>
<div>
<div>
<div id=""></div>
</div>
</div>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<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>Steve DelBianco <<a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a>><br>
<span style="font-weight:bold">Date: </span>Thursday, May 26, 2016 at 10:24 AM<br>
<span style="font-weight:bold">To: </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>Synchronizing WS2 accountability projects with upcoming Accountability & Transparency Review (ATRT3)<br>
</div>
<div><br>
</div>
<div>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
Just wanted to start a new thread on something CCWG should discuss as we begin Work Stream 2 (WS2). The attached document has all the background, and is summarized below.</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
<div>
<div><font face="Calibri,sans-serif">Several of our approved WS2 accountability tasks are within the scope of the next Accountability and Transparency Review Team (ATRT3), which is currently scheduled to begin Jan-2017. The CCWG may wish to consider whether
to recommend delaying the start of ATRT3 in order to allow WS2 accountability items to be completed first.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">Currently ICANN is obligated to the 2009 Affirmation of Commitments with NTIA (AoC). ICANN’s Board made a commitment to NTIA to begin ATRT3 in January 2017. </font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">Regarding timing of ATRT3, note that the draft new bylaws require this review “be conducted no less frequently than every five years measured from the date the previous Accountability and Transparency Review Team was convened.”
Since the last ATRT was convened in Feb-2013, ATRT3 could begin as late as Feb-2018.</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">Below is a summary of WS2 items, CCWG discussions of WS2, and comparison of proposed bylaws for WS2 and ATRT recommendations. This document is intended to help CCWG determine whether and how to integrate and/or sequence
WS2 activities with the third Accountability and Transparency Review. </font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
<div><font face="Calibri,sans-serif">This document provides necessary background to address three questions:</font></div>
<ol>
<li><font face="Calibri,sans-serif">How does the scope of ATRT compare with WS2 accountability items?</font></li><li><font face="Calibri,sans-serif">What do the proposed bylaws require for implementation of WS2? </font></li><li><font face="Calibri,sans-serif">What do draft new bylaws require for the AoC review of Accountability and Transparency (ATRT)?</font></li></ol>
<div><font face="Calibri,sans-serif">My own view is that WS2 gives the community more leverage than ATRT to achieve adoption of accountability enhancements that might be resisted by ICANN board and legal. </font></div>
</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<div id=""></div>
</div>
</div>
</div>
</span></div>
</div>
</span>
</body>
</html>