<div dir="ltr">Hi all<div><br></div><div>On this topic of the MAR, just a couple of thoughts.</div><div><br></div><div>I don't really have a view about the forum etc - using existing groups of people makes sense where possible.</div><div><br></div><div>What I am interested in tho is the conversation, and who can participate.</div><div><br></div><div>- a conversation where different SOs and ACs, the ICANN Board and the ICANN Organisation can ask each other questions about performance, success etc isn't quite sharing best practice, because the purpose is different. Sharing best practice is about sharing ideas and lessons. A performance or accountability discussion leads to different questions - it's about the various parts of the ICANN family supporting each other's development by e.g. asking questions that are too hard to ask internally, or those that come from a different perspective. If that isn't explicit, then people don't have "permission" to ask that sort of question. And my experience of ICANN generally is that the various silos aren't that interested in hearing what others think of them (just my experience - yours may differ). </div><div><br></div><div>- the proposal was for a public discussion. The SO/AC leadership is anything but that, and to do its function needs to not be a public forum.</div><div><br></div><div><br></div><div>So to me a viable way to meet those needs would be an occasional open SO/AC discussion online with that specific agenda item.</div><div><br></div><div>Otherwise I think the possibility and promise of the MAR will be lost.</div><div><br></div><div><br>Thanks for your consideration.</div><div><br></div><div>Jordan</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 12 December 2016 at 15:50, Steve DelBianco <span dir="ltr"><<a href="mailto:sdelbianco@netchoice.org" target="_blank">sdelbianco@netchoice.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:16px;font-family:Calibri,sans-serif">
<div>
<div>
<div>For our next SOAC Accountability call, please review the latest from Sub Team 2, who are drafting our Report to the CCWG.</div>
</div>
</div>
<span id="m_-3927387268578349104OLK_SRC_BODY_SECTION">
<div style="word-wrap:break-word">
<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">
The attached draft report draws from our previous documents and discussions, and narrows our work to 3 tracks:</div>
</div>
</span>
<div><br>
</div>
<span id="m_-3927387268578349104OLK_SRC_BODY_SECTION">
<div style="word-wrap:break-word">
<div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><font face="Calibri,sans-serif">Track 1. Review and develop recommendations to improve SO and AC processes for accountability, transparency, and participation that are helpful to prevent capture. [yet to be drafted, since we are awaiting SOAC responses
to our questionnaire]</font></div>
</blockquote>
</div>
</div>
</span>
<div><br>
</div>
<span id="m_-3927387268578349104OLK_SRC_BODY_SECTION">
<div style="word-wrap:break-word">
<div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><font face="Calibri,sans-serif">Track 2. Evaluate the proposed “Mutual Accountability Roundtable” to assess its viability and, if viable, undertake the necessary actions to implement it. The preliminary conclusion in the attached doc is on page 4:</font></div>
</blockquote>
</div>
</div>
</span>
<div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><br>
</div>
<div><span style="background-color:rgb(255,255,0)">We conclude that the Mutual Accountability Roundtable as originally described is more of a transparency exercise where best practices may be shared. While this exercise is viable, we do not recommend it
for formal implementation. </span></div>
<div><span style="background-color:rgb(255,255,0)"><br>
</span></div>
<div><span style="background-color:rgb(255,255,0)">SO and AC chairs have a standing email list and may convene calls and meetings at any time. That creates an appropriate and adequate forum for sharing of experiences and best practices on accountability
to their respective stakeholders.</span></div>
</blockquote>
</blockquote>
</div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><br>
</div>
</blockquote>
</blockquote>
<div><br>
</div>
<span id="m_-3927387268578349104OLK_SRC_BODY_SECTION">
<div style="word-wrap:break-word">
<div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><font face="Calibri,sans-serif">Track 3. Assess whether the Independent Review Process (IRP) should be applied to SO & AC activities. </font></div>
<span id="m_-3927387268578349104OLK_SRC_BODY_SECTION">The preliminary conclusion in the attached doc is on page 5:</span></blockquote>
</div>
</div>
</span>
<div><br>
</div>
<span id="m_-3927387268578349104OLK_SRC_BODY_SECTION">
<div style="word-wrap:break-word">
<div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div>
<blockquote style="margin:0 0 0 40px;border:none;padding:0px">
<div><span style="background-color:rgb(255,255,0)">The IRP would not be applicable to SO & AC activities, as the IRP is currently described in Bylaws.</span></div>
<div><span style="background-color:rgb(255,255,0)">While the IRP could be made applicable by amending bylaws significantly, </span><span style="background-color:rgb(255,255,0)">the IRP should not be made applicable to SO & AC activities, because it
is complex and expensive, and there are easier alternative ways to challenge an AC or SO action or inaction</span></div>
</blockquote>
</div>
<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">
<br>
</div>
</div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:16px">
Before our next call, please suggest edits to tracks 2 and 3 in the Google Doc, at </div>
</div>
</span>
<div><a href="https://docs.google.com/document/d/14XrP2QiGv04qNtn_EuOR3nEc6uAN2ySlpQM5f69PNI8/edit?usp=sharing" target="_blank">https://docs.google.com/<wbr>document/d/14XrP2QiGv04qNtn_<wbr>EuOR3nEc6uAN2ySlpQM5f69PNI8/<wbr>edit?usp=sharing</a> </div><span class="HOEnZb"><font color="#888888">
<div><br>
</div>
<span id="m_-3927387268578349104OLK_SRC_BODY_SECTION">
<div style="word-wrap:break-word">
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:16px">
—Steve</div>
<div style="color:rgb(0,0,0);font-family:Calibri,sans-serif;font-size:16px">
<br>
</div>
</div>
</span>
</font></span></div>
<br>______________________________<wbr>_________________<br>
Ws2-so_ac mailing list<br>
<a href="mailto:Ws2-so_ac@icann.org">Ws2-so_ac@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/ws2-so_ac" rel="noreferrer" target="_blank">https://mm.icann.org/mailman/<wbr>listinfo/ws2-so_ac</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr" style="font-size:small">Jordan Carter<br><br>Chief Executive <br><b>InternetNZ </b></div><div dir="ltr" style="font-size:small"><b><br></b></div><div dir="ltr" style="font-size:small">+64-4-495-2118 (office) | +64-21-442-649 (mob) | Skype: jordancarter <br><a href="mailto:jordan@InternetNZ.net.nz" target="_blank">jordan@InternetNZ.net.nz</a> | <a href="http://www.InternetNZ.nz" target="_blank">www.InternetNZ.nz</a></div><div style="font-size:small"><i><br></i></div><div style="font-size:small"><i>A better world through a better Internet</i></div><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
</div>