<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Do you have a blueprint of the new ICANN(s) in mind, or just more and larger committees meeting more often? </div><div><br></div><div>What about a structural and/or organizational separation between policy, compliance and straight business operations as some US senators have already suggested?<br><br>Any roadmap in mind? After the IANA transition? Splitting the board in the meantime between indirect (NomCom) and direct representatives for some of functional roles as per above?</div><div><br></div><div>Just discussing for the sake of it is a nice exercise. But we need a new vision of the whole setup if we want to change it so thoroughly.</div><div><br></div><div>Happy new year</div><div><br>Carlos Raúl Gutiérrez<div>+506 8837 7176 (New Number)</div><div>Enviado desde mi iPhone</div></div><div><br>El ene 4, 2015, a las 8:30 AM, Kieren McCarthy <<a href="mailto:kierenmccarthy@gmail.com">kierenmccarthy@gmail.com</a>> escribió:<br><br></div><blockquote type="cite"><div>
<span id="mailbox-conversation">Hello all,<div><br></div>
<div>Could I just throw an observation about the current setup in here, having watched ICANN both externally and internally (both community and corporation) for more than a decade.</div>
<div><br></div>
<div>We are taking the presumption that the Board is not only the group that ultimately makes the decisions but also the group that keeps the corporation in check on more everyday, operational matters.</div>
<div><br></div>
<div>I would argue that this approach consistently fails because the Board cannot be expected to see and follow everything. It is also ends up concentrating too much power and reliance on that power in too few hands.</div>
<div><br></div>
<div>It also provides opportunities for the Board to make bad decisions (like a 10-year lease on an unused building, or a investment strategy tied too closely to a failing stock market, or wage packages that are far too high, or expense accounts with no apparent limits, or an internet governance strategy that upsets the entire technical community, and so on).</div>
<div><br></div>
<div>Rather than focus solely on how to get the Board to listen more closely before making a decision (which is of course vital), we should also consider how to allow the community to assist in the running of ICANN. Rather than rely on the Board of a Corporation to do everything.</div>
<div><br></div>
<div>We should try to break down some of the Them vs Us attitude that exists within the corporation, which is behind many of the problems.</div>
<div><br></div>
<div>One of many ways to do this would be an improved information release policy with a staff-and-community committee in charge.</div>
<div><br></div>
<div>In fact, pulling staff more into the community by having joint committees (rather than have staff as secretaries) to solve corporate-specific issues should help break down barriers and build trust.</div>
<div><br></div>
<div>Opening up the current Board committees to community members would also help enormously. There is no real reason why it should only be staff and Board on these committees (I have sat on or in many of them and community members would have been useful many times).</div>
<div><br></div>
<div>There are lots of other possibilities but you get my general point. Let's open things up, ICANN is no longer under existential threat. It's time to reflect that and help it grow into what it should be.</div>
<div><br></div>
<div><br></div>
<div>Kieren</div></span><div class="mailbox_signature">
<br>-<br>[sent through phone]</div>
<br><br><div class="gmail_quote"><p>On Wed, Dec 31, 2014 at 10:36 AM, Jonathan Zuck <span dir="ltr"><<a href="mailto:JZuck@actonline.org" target="_blank">JZuck@actonline.org</a>></span> wrote:<br></p><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I think the primary problem with this approach is that accountability issues
<i>currently</i>, not to mention in the hypothetical future have to do with more than scope creep. Everyone is up in arms about that issue in particular because of recent events but we need to think more broadly about what might happen in the future and come
up with a true accountability mechanism, in WS1, and I content it will be DIFFICULT to get through the board but necessary. This isn’t about what the board will accept, it’s about what the community NEEDS for an accountable ICANN going forward.</span></p><p></p><p></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"></span></p><p> </p><p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> <a href="mailto:accountability-cross-community-bounces@icann.org">accountability-cross-community-bounces@icann.org</a> [<a href="mailto:accountability-cross-community-bounces@icann.org">mailto:accountability-cross-community-bounces@icann.org</a>]
<b>On Behalf Of </b>Robin Gross<br><b>Sent:</b> Wednesday, December 31, 2014 12:23 PM<br><b>To:</b> Paul Rosenzweig<br><b>Cc:</b> 'Brenda Brewer'; 'Accountability Cross Community'<br><b>Subject:</b> Re: [CCWG-Accountability] Agenda for CCWG-Accountability on 30 December at 19:00 UTC</span></p><p></p><p></p>
</div>
</div>
<p class="MsoNormal"></p>
<p> </p>
<p class="MsoNormal">I support this proposal and believe having this dialogue with the board upfront will help us to know where to focus our work going forward. </p>
<p></p>
<div>
<p class="MsoNormal"></p>
<p> </p>
</div>
<div>
<p class="MsoNormal">We can debate where to draw the line, but I think many would find the current wording the Articles of Incorporation to be so vague and broad that it hasn't provided any form of backstop in the past to mission-creep and so must be narrowed
and clarified.</p>
<p></p>
</div>
<div>
<p class="MsoNormal"></p>
<p> </p>
</div>
<div>
<p class="MsoNormal">Thanks,</p>
<p></p>
</div>
<div>
<p class="MsoNormal">Robin</p>
<p></p>
</div>
<div>
<p class="MsoNormal"></p>
<p> </p>
<div>
<div>
<p class="MsoNormal">On Dec 30, 2014, at 2:39 PM, Paul Rosenzweig wrote:</p>
<p></p>
</div>
<p class="MsoNormal"><br><br></p>
<p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">All</span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">As a follow up to our discussion on today’s call and in reference to my point that OUR work on accountability is highly dependent on what the Board/ICANN will
or will not agree to, may I propose that our Chairs send to the Board and the ICANN CEO a communication roughly along the following lines:</span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">The Cross-Community Working Group on accountability measures has been considering many accountability mechanisms to recommend concerning the prospective governance
of ICANN. Many members and participants in the CCWG have tentatively concluded that the nature and scope of the CCWG’s recommendations is dependent upon knowing whether or not the Board and ICANN will agree to certain fundamental limitations on Board authority.
Accordingly, the CCWG requests direct input from the Board and/or CEO on the following question:</span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">“Will the Board agree, in principle, to accept accountability recommendations that a) restrict (either through Bylaw amendment or contract) the scope of ICANN
activity exclusively to management and operation of the IANA function; and b) that provides an independent mechanism (whether through outside arbiter or internal review by a standing community group) by which alleged attempts by the Board/ICANN to exceed that
narrow scope of authority may be adjudicated and, if necessary, restrained?</span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">If the Board is fundamentally willing to accept such limitations then remaining accountability mechanisms may be reasonably limited to proposals that relate to
the successful implementation of the IANA function itself. If the Board and ICANN are, however, not willing to accept such limitations on their own authority then many members of the CCWG believe that accountability mechanisms proposed by the CCWG will need
to be commensurately broadened.”</span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I do not, of course, care terribly much about the specific language we use. My goal, however, is to find a way to get Board input into our decision making at
a point where it can significantly narrow (or substantially broadened) our field of consideration.</span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Perhaps more to the point, simply asking the question creates information – if the Board is unable or unwilling to answer at all (or if it answers in the negative)
that would, in and of itself, justify the community in seeking a broader accountability package. By contrast, if the Board answers affirmatively, then our task is much simpler – we need to reach consensus on the critical WS0 board control mechanisms and then
add only the IANA function-related mechanisms we deem necessary.</span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">So … my proposal is simply that the Chairs of our WG find some way of both asking this question formally and getting a formal answer for us at the earliest practicable
opportunity.</span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I wish everyone a very healthy and happy new year.</span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Warm regards</span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Paul</span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></p>
<p></p>
</div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#C00000">**NOTE: OUR NEW ADDRESS -- EFFECTIVE 12/15/14 ***</span></b></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">509 C St. NE</span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Washington, DC 20002</span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Paul Rosenzweig</span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><a href="mailto:paul.rosenzweigesq@redbranchconsulting.com"><span style="color:#0563C1">paul.rosenzweig@redbranchconsulting.com</span></a></span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">O: +1 (202) 547-0660</span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">M: +1 (202) 329-9650</span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Skype: +1 (202) 738-1739 or paul.rosenzweig1066</span></p>
<p></p>
</div>
<p class="MsoNormal" style="text-align:justify"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"><a href="http://www.redbranchconsulting.com/index.php?option=com_content&view=article&id=19&Itemid=9"><span style="color:#0563C1">Link
to my PGP Key</span></a></span></p>
<p></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span></p>
<p></p>
</div>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in;border-width:initial;border-color:initial">
<div>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span class="apple-converted-space"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> </span></span><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Grace
Abuhamad [<a href="mailto:grace.abuhamad@icann.org">mailto:grace.abuhamad@icann.org</a>]<span class="apple-converted-space"> </span><br><b>Sent:</b><span class="apple-converted-space"> </span>Monday, December 29, 2014 8:16 AM<br><b>To:</b><span class="apple-converted-space"> </span>Accountability Cross Community<br><b>Cc:</b><span class="apple-converted-space"> </span>Brenda Brewer<br><b>Subject:</b><span class="apple-converted-space"> </span>[CCWG-Accountability] Agenda for CCWG-Accountability on 30 December at 19:00 UTC</span></p>
<p></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal"> </p>
<p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Dear all, </span></p>
<p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"> </span></p>
<p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black">Please find below the proposed agenda for the CCWG-Accountability call on 30 December at 19:00 UTC. I will send to call details to the Notify list. </span></p>
<p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Calibri",sans-serif;color:black"> </span></p>
<p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><b><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black">Proposed Agenda</span></b><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black">:</span></p>
<p></p>
</div>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black">1. Welcome & Roll Call & Statements of Interest</span></p>
<p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black">2. Membership Updates </span></p>
<p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black">3. Work Area Updates</span></p>
<p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black">WA1 – David Maher / Samantha Eisner</span></p>
<p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black">WA2 – Steve DelBianco</span></p>
<p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black">WA3 – Avri Doria</span></p>
<p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black">WA4 – Eric Brunner-Williams</span></p>
<p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black">4. Coordination between CWG and ICG</span></p>
<p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black">5. Expectations for the F2F</span></p>
<p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black">6. AOB</span></p>
<p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.5pt;font-family:"Helvetica",sans-serif;color:black">7. Closing Remarks</span></p>
<p></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><span style="font-size:13.5pt;font-family:"Helvetica",sans-serif">_______________________________________________<br>
Accountability-Cross-Community mailing list<br><a href="mailto:Accountability-Cross-Community@icann.org"><span style="color:#0563C1">Accountability-Cross-Community@icann.org</span></a><br><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community"><span style="color:#0563C1">https://mm.icann.org/mailman/listinfo/accountability-cross-community</span></a></span></p><p></p><p></p>
</div>
</blockquote>
</div>
<p class="MsoNormal"></p>
<p> </p>
</div>
</div></blockquote></div><br></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Accountability-Cross-Community mailing list</span><br><span><a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a></span><br><span><a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span><br></div></blockquote></body></html>