<div dir="auto">Hello,<div dir="auto"><br></div><div dir="auto">I agree on the process point in Avri's mail as i think it will have been good for the SO/AC accountability leads to get back to the sub-group on this. I personally have not been consistent with subgroups meetings lately hence i may not have full glimpse of what gave the leads the confidence to update subgroup documents on the fly, i guess it could be that they've checked the temperature of the subgroup on such hypothesis in the past. Nevertheless, the leads sure will be in the best position to do the needful (i note though that the subgroup was copied in Steve's mail).</div><div dir="auto"><br></div><div dir="auto">That said, I for one would have loved to see the "mutual" maintained but owning to realities on ground at it concerns SO/AC relationships i have my doubts. Recent events especially those related to the Atlarge review and considering how some SO/AC members/leaders reacted to it, further confirms my doubt on whether this community is matured enough to have such level of cross accountability. Besides, it's "somewhat" impractical for some groups like the ASO whose accountability is largely to/from the RIR community. The extent of checking SSAC's accountability who largely operates closed (for good reasons) is also one of the reasons why mutual may be ineffective or at best become one sided.</div><div dir="auto"><br></div><div dir="auto">Regards</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 29 Mar 2017 4:01 p.m., "avri doria" <<a href="mailto:avri@acm.org" target="_blank">avri@acm.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I find this way of explaining it unfortunately.<br>
<br>
The subgroup sent a paper with the word 'Mutual' in. For the subgroup<br>
leaders to now indicate that this was just the whimsy of a minority of<br>
the plenary when that had been the recommendation of the subgroup seems<br>
backwards.<br>
<br>
I believe that the plenary group chairs played fast and loose with the<br>
process by changing the work of the subteam on the fly instead of<br>
sending it back to the subteam. It should have either approved the<br>
second reading or sent it back for further work.<br>
<br>
<br>
avri<br>
<br>
I'm late / I'm late / For a very important date. / No time to say<br>
"Hello, Goodbye". / I'm late, I'm late, I'm late.<br>
<br>
<br>
On 29-Mar-17 10:40, Steve DelBianco wrote:<br>
> Per the decision reached on today’s plenary call, here is the SOAC<br>
> Accountability Report as approved for Public Comment.<br>
><br>
> The 2 minor edits to the previous draft are:<br>
><br>
> remove the word “ranks” on page 7.<br>
> remove the word “mutual” on page 32.<br>
><br>
><br>
> The call for Public Comment could indicate this explanation and seek<br>
> community input:<br>
><br>
><br>
> A minority of CCWG members prefer that the optional annual<br>
> Accountability Roundtable discussion described on page 32 be<br>
> expanded to include “mutual” accountability, where each SO/AC is<br>
> held accountable to the other SO/ACs.<br>
><br>
> From: Steve DelBianco <<a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.org</a><br>
> <mailto:<a href="mailto:sdelbianco@netchoice.org">sdelbianco@netchoice.<wbr>org</a>>><br>
> Date: Thursday, March 23, 2017 at 3:01 PM<br>
> To: Accountability Cross Community<br>
> <<a href="mailto:accountability-cross-community@icann.org">accountability-cross-<wbr>community@icann.org</a><br>
> <mailto:<a href="mailto:accountability-cross-community@icann.org">accountability-cross-<wbr>community@icann.org</a>>><br>
> Cc: Cheryl Langdon-Orr <<a href="mailto:langdonorr@gmail.com">langdonorr@gmail.com</a><br>
> <mailto:<a href="mailto:langdonorr@gmail.com">langdonorr@gmail.com</a>>><wbr>, farzaneh badii<br>
> <<a href="mailto:farzaneh.badii@gmail.com">farzaneh.badii@gmail.com</a> <mailto:<a href="mailto:farzaneh.badii@gmail.com">farzaneh.badii@gmail.<wbr>com</a>>>,<br>
> "<a href="mailto:ws2-so_ac@icann.org">ws2-so_ac@icann.org</a> <mailto:<a href="mailto:ws2-so_ac@icann.org">ws2-so_ac@icann.org</a>>"<br>
> <<a href="mailto:ws2-so_ac@icann.org">ws2-so_ac@icann.org</a> <mailto:<a href="mailto:ws2-so_ac@icann.org">ws2-so_ac@icann.org</a>>>, ACCT-Staff<br>
> <<a href="mailto:acct-staff@icann.org">acct-staff@icann.org</a> <mailto:<a href="mailto:acct-staff@icann.org">acct-staff@icann.org</a>>><wbr>, Bernard Turcotte<br>
> <<a href="mailto:turcotte.bernard@gmail.com">turcotte.bernard@gmail.com</a> <mailto:<a href="mailto:turcotte.bernard@gmail.com">turcotte.bernard@<wbr>gmail.com</a>>><br>
> Subject: SOAC Accountability group in CCWG WS2 - report for plenary<br>
> 2nd reading, on 29-Mar-2017<br>
><br>
> To our CCWG colleagues:<br>
><br>
> Attached, for your consideration, is the report of the SOAC<br>
> Accountability group of Work Stream 2, revised per comments at our<br>
> first reading at the 10-Mar plenary in Copenhagen. Including:<br>
><br>
><br>
> Clarify we are looking only at activities within ICANN, so we are<br>
> not looking at NRO and IETF outside of ICANN.<br>
><br>
> For best practices instead of saying”should consider”, we say<br>
> "should implement, to the extent these practices are applicable<br>
> and an improvement…”<br>
><br>
> Suggest that future ATRTs may examine the extent to which best<br>
> practices have been implemented.<br>
><br>
> Recommend an optional mutual accountability roundtable at annual<br>
> general meetings, at the option of SO/AC chairs.<br>
><br>
> Add 5 examples of reasons to close a meeting to public observation<br>
><br>
> Make best practices more consistent regarding meeting notes and<br>
> minutes<br>
><br>
> Add the dimension of diversity to outreach best practices.<br>
><br>
> We have also attached a redline from version 1.0 to version 1.1<br>
><br>
> Our group looks forward to your questions and comments during 2nd<br>
> reading on 29-Mar.<br>
><br>
> Regards,<br>
> Steve DelBianco, Cheryl Langdon-Orr, and Farzaneh Badii<br>
> Co-Rapporteurs, SOAC Accountability Group, CCWG WS2<br>
><br>
><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> Accountability-Cross-Community mailing list<br>
> <a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-<wbr>Community@icann.org</a><br>
> <a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/accountability-cross-<wbr>community</a><br>
<br>
<br>
<br>
---<br>
This email has been checked for viruses by Avast antivirus software.<br>
<a href="https://www.avast.com/antivirus" rel="noreferrer" target="_blank">https://www.avast.com/<wbr>antivirus</a><br>
<br>
______________________________<wbr>_________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-<wbr>Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/accountability-cross-<wbr>community</a><br>
</blockquote></div></div>