<div dir="ltr"><div>Mathieu</div><div>Sorry </div><div>I am not in favour of interpretation.</div><div>What one interprete in one direction could be differently interpreted by other in other direction</div><div>Pls retrain the Charter text as it is</div><div>If that was vague , pls redress the charter but not interpret it in the way that suits certain area or certain persons</div><div>Kavouss </div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-01-15 12:41 GMT+01:00 Mathieu Weill <span dir="ltr">&lt;<a href="mailto:mathieu.weill@afnic.fr" target="_blank">mathieu.weill@afnic.fr</a>&gt;</span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    Dear Tijani,<br>
    <br>
    The &quot;new&quot; proposal is in no way meant to be a substitute to the
    charter definition. The Charter definition, intentionally, left room
    for interpretation. Therefore the proposal we are now considering
    intends to provide the CCWG&#39;s interpretation and orientation. <br>
    <br>
    Indeed, we are delivering on one of the areas of work mentioned in
    our Charter, which read (section III, deliverables) : <br>
    <blockquote type="cite">
      
      <p style="line-height:normal;margin-bottom:0pt"><span lang="EN-US" style="font-family:Symbol"><span>·<span style="font:7pt/normal &quot;Times New Roman&quot;;font-size-adjust:none;font-stretch:normal">        
            </span></span></span><span lang="EN-US">A
          definition/description of
          what differentiates a Work Stream 1 issue from a Work Stream 2
          issue<u></u><u></u></span></p>
      
      
      
      
      
      
      
      
      </blockquote>
    Thus, the question is whether the proposed version is found
    appropriate to the group in order to qualify what is necessary
    before the transition happens. <br>
    <br>
    I hope this clarifies. <br>
    <br>
    Best<br>
    Mathieu<br>
    <br>
    <div>Le 15/01/2015 10:52, Tijani BEN JEMAA a
      écrit :<br>
    </div><div><div class="h5">
    <blockquote type="cite">
      
      
      
      <div>
        <p class="MsoNormal" style="line-height:115%"><span style="color:rgb(31,73,125)">Dear
            all,<u></u><u></u></span></p>
        <p class="MsoNormal" style="line-height:115%"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
        <p class="MsoNormal" style="line-height:115%"><span lang="EN-US" style="color:rgb(31,73,125)">I
            read again the new proposed definition of the Work Streams,
            and I found it too
            different from the one in our charter:<u></u><u></u></span></p>
        <p class="MsoNormal" style="line-height:115%"><span lang="EN-US" style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
        <p class="MsoNormal" style="line-height:115%"><span lang="EN-US" style="color:rgb(31,73,125)">In
            the charter:<u></u><u></u></span></p>
        <p style="margin-bottom:0pt"><span lang="EN-US" style="color:rgb(1,1,1);font-family:Symbol"><span>·<span style="font:7pt/normal &quot;Times New Roman&quot;;font-size-adjust:none;font-stretch:normal">        
              </span></span></span><span dir="LTR"></span><b><span lang="EN-US">Work
              Stream 1</span></b><span lang="EN-US">: focused on
            mechanisms enhancing ICANN
            accountability that must be in place or committed to within
            the time frame of
            the IANA Stewardship Transition;</span><span lang="EN-US" style="background:white;color:rgb(1,1,1);font-family:&quot;Cambria&quot;,&quot;serif&quot;"><u></u><u></u></span></p>
        <p style="margin-bottom:0pt"><span lang="EN-US" style="color:rgb(1,1,1);font-family:Symbol"><span>·<span style="font:7pt/normal &quot;Times New Roman&quot;;font-size-adjust:none;font-stretch:normal">        
              </span></span></span><span dir="LTR"></span><b><span lang="EN-US">Work
              Stream 2</span></b><span lang="EN-US">: focused on
            addressing accountability
            topics </span><span lang="EN-US">for which a timeline for
            developing solutions
            and full implementation may extend beyond the IANA
            Stewardship Transition</span><span lang="EN-US" style="color:rgb(31,73,125)"> </span><span lang="EN-US" style="background:white;color:rgb(1,1,1);font-family:&quot;Cambria&quot;,&quot;serif&quot;"><u></u><u></u></span></p>
        <p class="MsoNormal" style="line-height:115%"><span lang="EN-US" style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
        <p class="MsoNormal" style="line-height:115%"><span lang="EN-US" style="color:rgb(31,73,125)">The
            new proposal:<u></u><u></u></span></p>
        <p style="background:white;margin-right:0cm;margin-bottom:0pt;margin-left:35.45pt"><span lang="EN-US" style="font-family:Symbol"><span>·<span style="font:7pt/normal &quot;Times New Roman&quot;;font-size-adjust:none;font-stretch:normal">        
              </span></span></span><span dir="LTR"></span><b><span lang="EN-US">Work Stream
              1</span></b><span lang="EN-US"> mechanisms are those that,
            when in place or
            committed to, would provide the community with confidence
            that any
            accountability  mechanism that would further enhance ICANN&#39;s
            accountability would be implemented if it had consensus
            support from the
            community, even if it were to encounter ICANN management
            resistance or if it
            were against the interest of ICANN as a corporate entity. <u></u><u></u></span></p>
        <p style="background:white;margin-right:0cm;margin-bottom:0pt;margin-left:35.45pt"><span lang="EN-US" style="font-family:Symbol"><span>·<span style="font:7pt/normal &quot;Times New Roman&quot;;font-size-adjust:none;font-stretch:normal">        
              </span></span></span><span dir="LTR"></span><span lang="EN-US">All other
            consensus items could be in <b>Work Stream 2</b>, provided
            there are mechanisms
            in WS1 adequate to force implementation of WS2 items despite
            resistance from
            ICANN management and board.<u></u><u></u></span></p>
        <p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
        <p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125)">I
            don’t believe
            that we are allowed to change any part of the charter
            without going back to the
            chartering organizations and ask for their approval.<u></u><u></u></span></p>
        <p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
        <p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125)">On
            the other hand, the
            separation of WS 1 and WS 2 was for the purpose of having
            the accountability mechanisms
            necessary before the transition done in time, and the new
            definition doesn’t
            satisfy this requirement <u></u><u></u></span></p>
        <p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
        <p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125)">I
            would prefer stay
            with the charter definition for all those reasons<u></u><u></u></span></p>
        <p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
        <p class="MsoNormal"><span lang="EN-US" style="color:rgb(23,54,93)">--------------------------------------------------------------------------------<u></u><u></u></span></p>
        <p class="MsoNormal"><b><span lang="EN-US" style="color:rgb(23,54,93)">Tijani
              BEN JEMAA<u></u><u></u></span></b></p>
        <p class="MsoNormal"><span lang="EN-US" style="color:rgb(23,54,93)">Executive
            Director<u></u><u></u></span></p>
        <p class="MsoNormal"><span lang="EN-US" style="color:rgb(23,54,93)">Mediterranean
Federation
            of Internet Associations </span><span lang="EN-US" style="color:rgb(23,54,93);font-size:12pt">(<b>FMAI</b>)</span><span lang="EN-US" style="color:rgb(23,54,93);font-size:13pt"><u></u><u></u></span></p>
        <p class="MsoNormal"><span style="color:rgb(23,54,93)">Phone:  + 216
            41 649 605<u></u><u></u></span></p>
        <p class="MsoNormal"><span style="color:rgb(23,54,93)">Mobile: + 216
            98 330 114<u></u><u></u></span></p>
        <p class="MsoNormal"><span style="color:rgb(23,54,93)">Fax:      
            <a href="tel:%2B%20216%2070%20853%C2%A0376" target="_blank" value="+21670853376">+ 216 70 853 376</a><u></u><u></u></span></p>
        <p class="MsoNormal"><span lang="EN-US" style="color:rgb(23,54,93)">--------------------------------------------------------------------------------<u></u><u></u></span></p>
        <p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125)"> </span><span style="color:rgb(31,73,125)"><u></u><u></u></span></p>
        <p class="MsoNormal"><span style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
        <p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
        <p class="MsoNormal"><span lang="EN-US" style="color:rgb(31,73,125)"><u></u> <u></u></span></p>
      </div>
      <br>
      <br>
      <hr style="border:currentColor;width:99%;color:rgb(144,144,144);min-height:1px;background-color:rgb(176,176,176)">
      <table style="border:currentColor;border-collapse:collapse">
        <tbody>
          <tr>
            <td style="padding:0px 15px 0px 8px;border:currentColor"> <a href="http://www.avast.com/" target="_blank"> <img src="http://static.avast.com/emails/avast-mail-stamp.png" border="0"> </a> </td>
            <td>
              <p style="color:rgb(61,77,90);font-family:&quot;Calibri&quot;,&quot;Verdana&quot;,&quot;Arial&quot;,&quot;Helvetica&quot;;font-size:12pt"> Ce courrier électronique ne contient
                aucun virus ou logiciel malveillant parce que la
                protection <a href="http://www.avast.com/" target="_blank">Antivirus avast!</a> est
                active. </p>
            </td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
Accountability-Cross-Community mailing list
<a href="mailto:Accountability-Cross-Community@icann.org" target="_blank">Accountability-Cross-Community@icann.org</a>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a>
</pre>
    </blockquote>
    <br>
    </div></div><span class="HOEnZb"><font color="#888888"><pre cols="72">-- 
*****************************
Mathieu WEILL
AFNIC - directeur général
Tél: <a href="tel:%2B33%201%2039%2030%2083%2006" target="_blank" value="+33139308306">+33 1 39 30 83 06</a>
<a href="mailto:mathieu.weill@afnic.fr" target="_blank">mathieu.weill@afnic.fr</a>
Twitter : @mathieuweill
*****************************
</pre>
  </font></span></div>

<br>_______________________________________________<br>
Accountability-Cross-Community mailing list<br>
<a href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
<a href="https://mm.icann.org/mailman/listinfo/accountability-cross-community" target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a><br>
<br></blockquote></div><br></div>