<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <font face="Times New Roman, Times, serif">Dear Leon<br>
      <br>
      Thanks for these thought starters.<br>
      <br>
      May I suggest as we start this work perhaps it would be useful to
      have staff to compile a list of items under various accountability
      headings (e.g transparency, financial accountability, accountable
      behaiviour to community members, and other items you have included
      in the thought starters etc) from the existing documents and
      reviews that ICANN has undertaken over the last 7 years or more to
      define the accountability of staff, SO/ACs etc.   In particular
      the documents for review should include:<br>
      <br>
    </font>
    <ul>
      <li><font face="Times New Roman, Times, serif">The Affirmation of
          Accountabilities in 2010 (and follow on recommendations)</font></li>
      <li><font face="Times New Roman, Times, serif">The ICANN
          Accountability and Transparency Frameworks and Principles in
          2008 (attached, as it is hard to find on the present ICANN
          website), and </font></li>
      <li><font face="Times New Roman, Times, serif">The various One
          World Trust Reports on ICANN Accountability Benchmarks and
          Metrics
          (eg.https://www.icann.org/news/announcement-2014-03-04-en )</font></li>
    </ul>
    <font face="Times New Roman, Times, serif"><br>
      If we have this list of relevant paragraphs under various heads of
      responsibilities, we will have a first document of existing
      commitments which we can review and then suggest amendment or
      augmentation.<br>
      <br>
      I suggest that this will speed up our considerations.<br>
      <br>
      For instance the relevant sections of the 2008 principles could
      be:<br>
    </font>
    <ul>
      <li><font face="Times New Roman, Times, serif"> Commitments to
          Transparency in the ICANN Bylaws</font></li>
      <li><font face="Times New Roman, Times, serif">Documentary
          Information Disclosure Policy</font></li>
      <li><font face="Times New Roman, Times, serif">Responding to
          Information Requests</font></li>
      <li><font face="Times New Roman, Times, serif"><span
            style="font-size: 11pt;">The consultative planning process
            by the ICANN community sets strategic direction and
            determines operational priorities and budgets;</span><span
            style="font-size: 11pt;"></span></font></li>
      <li><font face="Times New Roman, Times, serif"><span
            style="font-size: 11pt;">The schedule of reviews of ICANN’s
            structure according to Article IV, Section 4 of
            the ICANN bylaws; </span> <span style="font-size: 11pt;"></span><span
            style="font-size: 11pt;"></span></font></li>
      <li><font face="Times New Roman, Times, serif"><span
            style="font-size: 11pt;">Translation Principles that guide
            the translation of documents within the ICANN community;</span><span
            style="font-size: 11pt;"></span></font></li>
      <li><font face="Times New Roman, Times, serif"><span
            style="font-size: 11pt;">Consultation Principles that guide
            the consultation processes that are used to generate
            community input on ICANN issues; </span> <span
            style="font-size: 11pt;"></span><span style="font-size:
            11pt;"></span></font></li>
      <li><font face="Times New Roman, Times, serif"><span
            style="font-size: 11pt;">A statement of expected standards
            of behavior which outlines the standards of behavior
            expected of those who participate in the ICANN process. </span></font>
        <font face="Times New Roman, Times, serif"> </font></li>
    </ul>
    <div class="moz-forward-container"><small>This of course is not
        complete, but it will give us a start.<br>
        <br>
        Best<br>
        <br>
        Paul</small><br>
    </div>
    <br>
    <pre class="moz-signature" cols="72">-- 
Dr Paul Twomey
Managing Director
Argo P@cific 

US Cell: +1 310 279 2366
Aust M: +61 416 238 501

<a class="moz-txt-link-abbreviated" href="http://www.argopacific.com">www.argopacific.com</a></pre>
    <br>
    <div class="moz-cite-prefix">On 7/2/15 10:21 AM, León Felipe Sánchez
      Ambía wrote:<br>
    </div>
    <blockquote
      cite="mid:78C86593-ACF5-47C5-96BE-AF053446B2CD@sanchez.mx"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      Dear all,
      <div class=""><br class="">
      </div>
      <div class="">Thanks to all of you who have volunteered to join
        this new WP. Staff has circulated a doodle poll to schedule our
        first call and an email list has been created as well.</div>
      <div class=""><br class="">
      </div>
      <div class="">We have a lot of work to do in very little time. I
        suggest we begin work already by dividing it into sub-groups
        that can have deeper looks into these emerging issues:</div>
      <div class=""><br class="">
      </div>
      <div class="">- Staff &amp; management accountability</div>
      <div class="">- SO(AC accountability</div>
      <div class="">- Enhancement of diversity</div>
      <div class="">- Board rules</div>
      <div class=""><br class="">
      </div>
      <div class="">For this work I encourage everyone to review the
        discussion starter documents that have been circulated by
        Mathieu and that are attached in PDF to this email.</div>
      <div class=""><br class="">
      </div>
      <div class="">These documents will help us start our work and
        provide us initial suggestions as to how we can structure our
        output.</div>
      <div class=""><br class="">
      </div>
      <div class="">We should, ideally, have a draft document for each
        issue by July 14 so it can be sent to the wider group and
        reviewed in our meeting in Paris.</div>
      <div class=""><br class="">
      </div>
      <div class="">An optimal initial output could be to, at least,
        have a list of actions that should be included in both WS1 and
        WS2 so we can then work in more detail in those catalogued as
        WS1 either before or in our meeting in Paris.</div>
      <div class=""><br class="">
      </div>
      <div class=""><br class="">
        <div apple-content-edited="true" class="">
          <div class="">Best regards,</div>
          <div class=""><br class="">
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div class="">
        <div apple-content-edited="true" class="">
          <div class="">León</div>
        </div>
        <br class="">
        <div>
          <blockquote type="cite" class="">
            <div class="">El 01/07/2015, a las 5:31, Alice Jansen &lt;<a
                moz-do-not-send="true"
                href="mailto:alice.jansen@icann.org" class="">alice.jansen@icann.org</a>&gt;
              escribió:</div>
            <br class="Apple-interchange-newline">
            <div class="">
              <meta http-equiv="Content-Type" content="text/html;
                charset=windows-1252" class="">
              <div style="word-wrap: break-word; -webkit-nbsp-mode:
                space; -webkit-line-break: after-white-space; font-size:
                14px; font-family: Calibri, sans-serif;" class="">
                <div class="">Dear all,</div>
                <div class=""><br class="">
                </div>
                <div class="">A Work Party 3 (WP3) was created on 30
                  June to address emerging issues i.e. staff and
                  management accountability, SO/AC accountability,
                  enhancement of diversity and Board duties. The
                  detailed mission and scope document can be found in
                  the attached for more information. </div>
                <div class=""><br class="">
                </div>
                <div class=""><b class="">You are invited to volunteer
                    for this effort. </b>If interested, please send an
                  email to ACCT-Staff &lt;<a moz-do-not-send="true"
                    href="mailto:acct-staff@icann.org" class="">acct-staff@icann.org</a>&gt;.</div>
                <div class="">The current list of volunteers includes: </div>
                <div class="">
                  <ul class="">
                    <li class="">León Sánchez (coordinator)</li>
                    <li class="">Avri Doria</li>
                    <li class="">Giovanni Seppia</li>
                    <li class="">Malcolm Hutty</li>
                    <li class="">Keith Drazek </li>
                    <li class="">Alan Greenberg</li>
                    <li class="">Greg Shatan</li>
                    <li class="">Izumi Okutani</li>
                    <li class="">Athina Fragkouli</li>
                  </ul>
                  <div class="">A call will be scheduled in the upcoming
                    days to kick off activities.</div>
                </div>
                <div class="">Activities of this group can be followed
                  on the dedicated wiki page <a moz-do-not-send="true"
href="https://community.icann.org/display/acctcrosscomm/WP3+-+Emerging+Issues"
                    class="">https://community.icann.org/display/acctcrosscomm/WP3+-+Emerging+Issues</a>.
                  Email exchanges can be read at:<span style="color:
                    rgb(51, 51, 51); font-family: Arial, Helvetica,
                    sans-serif; font-size: 13.3333330154419px;
                    line-height: 19.0476188659668px; widows: 1;
                    background-color: rgb(255, 255, 255); " class=""> </span><a
                    moz-do-not-send="true"
                    href="http://mm.icann.org/pipermail/wp3/" class="">http://mm.icann.org/pipermail/wp3/</a></div>
                <div class=""><br class="">
                </div>
                <div class="">Thanks</div>
                <div class=""><br class="">
                </div>
                <div class="">Best regards</div>
                <div class=""><br class="">
                </div>
                <div class="">Alice </div>
              </div>
              <span
                id="cid:45F4B17F1D3C0C4A9E615F5511C0BB8F@pexch112.icann.org">&lt;WP3.pdf&gt;</span><span
id="cid:5E91502B90C6434EAF34F6649D11DB61@pexch112.icann.org">&lt;WP3.docx&gt;</span>_______________________________________________<br
                class="">
              Accountability-Cross-Community mailing list<br class="">
              <a moz-do-not-send="true"
                href="mailto:Accountability-Cross-Community@icann.org"
                class="">Accountability-Cross-Community@icann.org</a><br
                class="">
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br
                class="">
            </div>
          </blockquote>
        </div>
        <br class="">
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Accountability-Cross-Community mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a>
<a class="moz-txt-link-freetext" href="https://mm.icann.org/mailman/listinfo/accountability-cross-community">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">
</pre>
  </body>
</html>