<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>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
We had a 1-hour discussion with the CCWG plenary today in Copenhagen. Here’s our summary of feedback received during first reading of our draft report:</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;">
<b>Track 1: Best Practices</b></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<div>First reading revealed no objections to our recommendations, but some possible changes:</div>
</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><br>
</div>
<div>Our draft Exec Summary says we “recommend best practices that should be considered …”. Speakers offered alternatives such as “we urge adoption of these best practices..” or “we encourage implementation of …”</div>
<div>--</div>
<div>ASO reminded us to clarify we are only talking about AC/SO accountability "within the scope of ICANN activities”, since NRO and IETF exist outside of ICANN, too.</div>
<div>--</div>
<div>Outreach and Participation: consider adding diversity dimension to best practices. Perhaps we suggest incorporating recommendations anticipated from the Diversity group of WS2.</div>
<div>
<div>
<div>
<div>--</div>
<div>Transparency Recc #4: add appropriate reasons for an AC/SO meeting to be “closed” to members:</div>
<div>(list provided by Michael Karanicolas)</div>
</div>
<div>
<ul style="font-family: -webkit-standard;">
<li>discussion of trade secrets or sensitive commercial information whose disclosure would cause harm to a person or organization's legitimate commercial or financial interests or competitive position.<br>
</li><li>discussion of internal strategic planning whose disclosure would likely compromise the efficacy of the the chosen course.<br>
</li><li>discussion of information whose disclosure would constitute an invasion of personal privacy, such as medical records.<br>
</li><li>discussion of information whose disclosure has the potential to harm the security and stability of the Internet.</li><li>discussion of information that, if disclosed, would be likely to endanger the life, health, or safety of any individual or materially prejudice the administration of justice.</li></ul>
</div>
<div>
<div id=""></div>
</div>
</div>
</div>
</blockquote>
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<font face="Calibri,sans-serif">—</font></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<font face="Calibri,sans-serif">Finn Peterson noted that Transparency Recc 5 and Participation Recc 4 both address minutes of member meetings, and should be more consistent. </font></div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><span style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">Transparency Recc 5: </span><font face="Calibri,sans-serif">Minutes for all membership meetings should be
published.</font></blockquote>
</blockquote>
<blockquote style="margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;"><span style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">Participation Recc 4: </span><font face="Calibri,sans-serif">For any meetings, be they closed to members
only or open to anyone, the members have to be able to access minutes and/or recordings, subject to exceptions for confidential matters.</font>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<font face="Calibri,sans-serif"> </font></div>
</blockquote>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<font face="Calibri,sans-serif">—</font></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<font face="Calibri,sans-serif">Jan Sholte and several others noted that we could recommend something stronger than just to "consider” these best practices. We answered that our group was not likely to recommend these best practices be placed into ICANN bylaws.
Moreover, our 2017 list of best practices would become outdated before long. No decision on what to do here.</font></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<span style="font-family: Calibri, sans-serif;">—</span></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<font face="Calibri,sans-serif">Some commenters want to see a continued focus on SOAC Accountability after the CCWG concludes. </font></div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<font face="Calibri,sans-serif">Indeed, o</font><font face="Calibri,sans-serif">n page 2 of our draft report we noted Recommendation 10 of the CCWG Final Proposal (<a href="https://community.icann.org/pages/viewpage.action?pageId=58723827&preview=/58723827/58726376/Annex%2010%20-%20FINAL-Revised.pdf ">link</a>):
</font></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><font face="Calibri,sans-serif">In Work Stream 2: Include the subject of SO and AC accountability as part of the work on the Accountability and Transparency Review process</font></div>
<div><font face="Calibri,sans-serif"><br>
</font></div>
</blockquote>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<font face="Calibri,sans-serif">We could amend our report to recommend that future ATRTs examine SO/AC accountability, transparency, participation, and outreach. This could be a new item in the
<a href="https://www.icann.org/resources/pages/governance/bylaws-en">Bylaws</a>, at Sec 4.6 b, where potential ATRT issues are listed. Or, we could recommend that ICANN staff add this item to the procedures for ATRT, which would not require a bylaws change.
Note that we would not refer future ATRTs back to our 2017 list of best practices. Instead, we’d expect that future ATRTs would undertake a review and develop recommendations similar to what our group did in 2016-17. </font>
<div><font face="Calibri,sans-serif"><br>
</font></div>
</div>
</blockquote>
<blockquote style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px; margin: 0px 0px 0px 40px; border: none; padding: 0px;">
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div><br>
</div>
</blockquote>
</blockquote>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<b>Track 2: Mutual Accountability Roundtable </b>(page 31)</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
First reading revealed significant objection to our recommendation on MARs. </div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
Several speakers prefer a formal discussion of SOAC accountability, at least once each year. </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;">
We could amend our report to recommend something like this:</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>Prior to each Annual General Meeting (AGM), ICANN staff should ask the chairs of all AC/SOs whether they want to hold a Mutual Accountability Roundtable to discuss SO/AC accountability with respect to activities within ICANN’s scope.</div>
<div>If a majority of AC/SO chairs agree to hold the Mutual Accountability Roundtable: </div>
<div>ICANN staff would schedule a 90-minute open session at the next AGM, open to all AC/SO/Group chairs, and joined by ICANN CEO and Board Chair. The ICANN board chair would designate a moderator for the session. </div>
<div><br>
</div>
</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;">
<b>Track 3: IRP </b>(page 32)</div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
First reading revealed no objections or changes to Track 3 recommendations.</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;">
Avri agrees we should mention the Ombudsman as an alternative, but says we should not recommend that the new ICANN Complaints Officer is an alternative to IRP. </div>
<div style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<br>
</div>
</div>
<span id="OLK_SRC_BODY_SECTION" style="color: rgb(0, 0, 0); font-family: Calibri, sans-serif; font-size: 16px;">
<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>
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">
<div><br>
</div>
<div>Regards,</div>
<div>Steve DelBianco, Cheryl Langdon-Orr, and Farzaneh Badii</div>
<span id="OLK_SRC_BODY_SECTION">
<div dir="ltr">Co-Rapporteurs, SOAC Accountability Group, CCWG WS2<br clear="all">
</div>
<div><br>
</div>
</span></div>
</div>
</div>
<div>
<div id=""></div>
</div>
</div>
</div>
</div>
</div>
</span>
</body>
</html>