<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>To: members of the CCWG sub team for SO/AC Accountability in Work Stream 2 (<a href="https://community.icann.org/pages/viewpage.action?pageId=59643284">wiki</a>)</div>
<div><br>
</div>
<div>On Sunday in Johannesburg, we discussed with the CCWG plenary the results of the
<a href="https://www.icann.org/public-comments/soac-accountability-2017-04-14-en">
public comment period</a> on our <a href="https://www.icann.org/en/system/files/files/ccwg-acct-ws2-draft-recs-improve-soac-accountability-29mar17-en.pdf">
first draft report</a>.</div>
<div><br>
</div>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">
<span id="OLK_SRC_BODY_SECTION">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">
<div>
<div>
<div style="font-size: 16px;">Cheryl and I used the attached slides and speaking notes to present. (Thanks to Bernie for starting the slide draft)</div>
</div>
</div>
</div>
</span></div>
</span>
<div><br>
</div>
<div>Discussion lasted about an hour. Chat transcript is at bottom of this email. </div>
<div><br>
</div>
<div>Some notes from the discussion and presentation and next steps:</div>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div><br>
</div>
<div><b>Track 1 and “Best Practices”</b></div>
<div>Some prefer a label other than “best practices”. One alternative is “Good Practices”</div>
<div>Not much support for having ATRT examine implementation of best practices.</div>
<div>Found support for assessing best practice implementation in the Organizational Reviews.</div>
<div><br>
</div>
<div><b>Track 1 and SOAC Accountability to the “broader community”</b></div>
<div>Not much support for Board’s comment seeking accountability of the collective SOACs, when acting as the Empowered Community.</div>
<div> "EC Decisional Participants should be accountable to the community as a whole, not just their respective SO/AC"</div>
<div>No board or staff took my invitation to provide suggestions for how to do this.</div>
A Co-chair said we need ICANN-wide conversations, not just decisions within each SOAC.
<div>One speaker noted that each AC/SOs will consider broader community when they are deciding on escalation of EC powers.</div>
<div>We should address Board comment with an explanation in our report. </div>
<div>
<div>One speaker suggested Organizational Review also look at cross-accountability.</div>
</div>
<div><br>
</div>
<div><b>Track 2 and [Mutual] Accountability Roundtable</b></div>
<div>
<div>Several said don’t do Accountability Round Table – revert to our original draft recommendation.</div>
<div>Note that SOACs can share best practices in their leadership emails and calls.</div>
<div>Idea to start with the optional Accountability Roundtable, and if it works we could make it an annual requirement.</div>
<div><br>
</div>
</div>
<div><b>Next Steps:</b></div>
<div>Public comments and our discussions today will be taken on-board by CCWG Accountability WS2 to consider amending our recommendations and then publish a report on results of the public consultation.</div>
<div>CCWG will also need to determine if any changes to our report are significant or not.</div>
<div>If significant changes are recommended, CCWG-Accountability WS2 may have a second public consultation.</div>
<div>If changes are not significant, CCWG-Accountability WS2 can forward final recommendations to Chartering Organizations for approval, and then to the ICANN Board for consideration and adoption.</div>
<div>On Sunday, nobody suggested we need another round of public comments.</div>
<div><br>
</div>
</blockquote>
<blockquote style="margin:0 0 0 40px; border:none; padding:0px;">
<div><span style="background-color: rgb(255, 255, 0);">We will re-convene our sub team for a few conference calls to discuss next steps. Schedule invitation to follow.</span></div>
</blockquote>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">
<span id="OLK_SRC_BODY_SECTION">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">
<div>
<div>
<div style="font-size: 16px;">Regards,</div>
<div style="font-size: 16px;">Steve DelBianco, Cheryl Langdon-Orr, and Farzaneh Badii</div>
<span id="OLK_SRC_BODY_SECTION" style="font-size: 16px;">
<div dir="ltr">Co-Rapporteurs, SOAC Accountability Group, CCWG WS2<br clear="all">
</div>
<div><br>
</div>
</span></div>
<div style="font-size: 16px;">
<div id=""></div>
</div>
</div>
</div>
</span></div>
</span>
<div><br>
</div>
<div>Chat transcript:</div>
<div><br>
</div>
<div>
<div>Sivasubramanian M @ 59: (11:03) "Good Practices" sound better, sounds more sincere</div>
<div><br>
</div>
<div>Steve DelBianco [GNSO-CSG]: (11:03) Sec 4.4 on Organizational Reviews: The goal of the review, to be undertaken pursuant to such criteria and standards as the Board shall direct, shall be to determine (i) whether that organization, council or committee
has a continuing purpose in the ICANN structure, (ii) if so, whether any change in structure or operations is desirable to improve its effectiveness and (iii) whether that organization, council or committee is accountable to its constituencies, stakeholder
groups, organizations and other stakeholders.</div>
<div><br>
</div>
<div>Kavouss Arasteh 6: (11:08) I also recommand to endeavour to meet the concerns expressed by the Board</div>
<div><br>
</div>
<div>Jordan Carter (.nz): (11:08) You can find the Board comment on these SO/AC accountability recommendations here:
<a href="https://mm.icann.org/pipermail/comments-soac-accountability-">https://mm.icann.org/pipermail/comments-soac-accountability-</a> 14apr17/2017-May/000007.html</div>
<div><br>
</div>
<div>Kavouss Arasteh: (11:12) In reply to Alan, I would say that is is a well known practice to say, " Best Practice " is understood and thden define that</div>
<div><br>
</div>
<div>Steve DelBianco [GNSO-CSG]: (11:14) that ICANN meeting planning staff take the following steps prior to each Annual General Meeting (AGM): (p. 9) ICANN staff should ask the chairs of all SO/ACs whether they want to hold an Accountability Roundtable to
discuss SO/AC accountability. If a majority of SO/AC chairs agree, ICANN staff would schedule a 90-minute public session at the next AGM, open to all SO/AC/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>
<div>Christopher Wilkinson (CW): (11:14) Agree with Malcolm. Against MART for those reasons. CW</div>
<div><br>
</div>
<div>Kavouss Arasteh: (11:14) As for mutual accountability; let us make it optional first, if it works well and at thenext review we could decide diffrently such as a need to do that</div>
<div><br>
</div>
<div>matthew shears: (11:16) there may be occassion when sharing practices may be a useful exercise then we might consider that the ART (not MART) be an optional measure subject to the approval of the SO/AC Chairs, for example.</div>
<div><br>
</div>
<div>Christopher Wilkinson (CW): (11:16) In an earlier posting (a long time ago) I suggested Mutual Transparency Round Table. CW</div>
<div><br>
</div>
<div>Kavouss Arasteh: (11:17) Perhaps the issue of doing it pin public comment to be separated from the main issue</div>
<div><br>
</div>
<div>Malcolm Hutty: (11:18) "Roundtable discussion on cross-cutting issues" would be more what I had in mind. We need to get away from any sense that this is a body that SOAC leaders report to or need to satisfy</div>
<div><br>
</div>
<div>Sivasubramanian M @ 59: (11:19) This conflict concerning mutual accountability could become unimportant, if on the whole the Community processes gradually move away from SILOs to Cross Community processes</div>
<div> </div>
<div>Jordan Carter (.nz): (11:21) We have done that for the use of the Community Powers, Steve - agreed. It's the broader picture of the organisation as a whole that we need to build into the process somewhere, and that I thought the MAR might be able to help
with.</div>
<div><br>
</div>
<div>Sivasubramanian M @ 59: (11:22) For e.g. if we work towards making a 4 day meeting with one and a half days of independant AC/SO schedules and two and a half days of Cross Community meetings.</div>
<div><br>
</div>
<div>Steve DelBianco [GNSO-CSG]: (11:23) Thanks for that clarification, Jordan</div>
<div><br>
</div>
<div>Jordan Carter (.nz): (11:23) Siva - yes the new meeting approach is helpful in breaking people out of the silos</div>
<div><br>
</div>
<div>Sivasubramanian M @ 59: (11:24) Such an overall shift would postively reflect on the independant AC/SO accountability process, as each AC / SO bring their independant work invariably to the Cross Communitty table.</div>
<div><br>
</div>
<div>Sivasubramanian M @ 59: (11:24) or a Cross Community House</div>
<div><br>
</div>
<div>Kavouss Arasteh: (11:27) Doing Mutual accountability on optional basis certainly would help but whether do it publicly or non publicly is another issue as I explained</div>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">
<span id="OLK_SRC_BODY_SECTION">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-family: Calibri, sans-serif;">
<div style="font-size: 16px;"><br>
</div>
<span id="OLK_SRC_BODY_SECTION" style="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><!--EndFragment--></div>
</div>
</div>
</span><link rel="File-List" href="file://localhost/private/var/folders/zt/8tqf9pdn0m59kdx7dq_d80040000gn/T/TemporaryItems/msoclip/0/clip_filelist.xml"><link rel="themeData" href="file://localhost/private/var/folders/zt/8tqf9pdn0m59kdx7dq_d80040000gn/T/TemporaryItems/msoclip/0/clip_themedata.xml"><style>
<!--
/* Font Definitions */
@font-face
{font-family:Arial;
panose-1:2 11 6 4 2 2 2 2 2 4;
mso-font-charset:0;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:-536859905 -1073711037 9 0 511 0;}
@font-face
{font-family:"ＭＳ 明朝";
mso-font-charset:78;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:-536870145 1791491579 18 0 131231 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;
mso-font-charset:0;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:-536870145 1107305727 0 0 415 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;
mso-font-charset:0;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:-520092929 1073786111 9 0 415 0;}
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;
mso-font-charset:0;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:-536870145 1073743103 0 0 415 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-unhide:no;
mso-style-qformat:yes;
mso-style-parent:"";
margin:0in;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:Cambria;
mso-ascii-font-family:Cambria;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"ＭＳ 明朝";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Cambria;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:Arial;
mso-bidi-theme-font:minor-bidi;}
.MsoChpDefault
{mso-style-type:export-only;
mso-default-props:yes;
font-family:Cambria;
mso-ascii-font-family:Cambria;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"ＭＳ 明朝";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Cambria;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:Arial;
mso-bidi-theme-font:minor-bidi;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;
mso-header-margin:.5in;
mso-footer-margin:.5in;
mso-paper-source:0;}
div.WordSection1
{page:WordSection1;}
-->
</style></div>
</span></div>
</span>
</body>
</html>