<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#330033">
    Hi,<br>
    <br>
    Maybe we should refer to the AC/SO entities that would gain the
    member attribute as Statutory Members.  If we get into the habit of
    refereing to them that way, it might be easier to keep the
    difference in mind.<br>
    <br>
    Or even use a standard explanatory phrase, instead of the simple
    noun, until it becomes a bingo term: The AC/SO acting as statutory
    members ...<br>
    <br>
    avri<br>
    <br>
    <div class="moz-cite-prefix">On 13-Apr-15 19:15, Greg Shatan wrote:<br>
    </div>
    <blockquote
cite="mid:CA+aOHURHZWVLodzpc8_1KkZu5Np9kfeexXejOJfe2h=Th4smvQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_default"
          style="font-family:verdana,sans-serif">James, </div>
        <div class="gmail_default"
          style="font-family:verdana,sans-serif"><br>
        </div>
        <div class="gmail_default"
          style="font-family:verdana,sans-serif">Unfortunately, members
          are members, and they are substantively different from
          delegates or designators.  </div>
        <div class="gmail_default"
          style="font-family:verdana,sans-serif"><br>
        </div>
        <div class="gmail_default"
          style="font-family:verdana,sans-serif">Sometimes, non-profits
          call people "members" who really aren't (e.g., I am not really
          a statutory "member" of the Metropolitan Museum of Art, even
          though I have a membership card in my wallet).  This is
          typically allowed by statute.  Unfortunately, it doesn't work
          the other way around -- there's nothing else to call members,
          as far as I know.</div>
        <div class="gmail_default"
          style="font-family:verdana,sans-serif"><br>
        </div>
        <div class="gmail_default"
          style="font-family:verdana,sans-serif">So, I think we just
          need to be clear that we are contemplating nothing more than
          taking the current organizations that participate in ICANN
          governance, and making them into the "members."  It should be
          thought of as a conversion of the current structure (merely
          rearranging the current elements) in this instance.  New
          classes of actors are not being created.</div>
        <div class="gmail_default"
          style="font-family:verdana,sans-serif"><br>
        </div>
        <div class="gmail_default"
          style="font-family:verdana,sans-serif">Greg</div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Mon, Apr 13, 2015 at 7:05 PM, James
          M. Bladel <span dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:jbladel@godaddy.com" target="_blank">jbladel@godaddy.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div dir="auto">
              <div>Jordan:</div>
              <div><br>
              </div>
              <div>Good clarification, but it is concerning that this
                (mis)conception is being heard outside the ccwg. Could
                we do a better job in terms of messaging?  Are there
                legally and functionally equivalent terms ("delegate")
                that are less prone to creating confusion?</div>
              <div><br>
                Thank you,
                <div><br>
                </div>
                <div>J.</div>
                <div>____________</div>
                <div>James Bladel</div>
                <div>GoDaddy</div>
              </div>
              <div>
                <div class="h5">
                  <div><br>
                    On Apr 13, 2015, at 15:15, Jordan Carter &lt;<a
                      moz-do-not-send="true"
                      href="mailto:jordan@internetnz.net.nz"
                      target="_blank">jordan@internetnz.net.nz</a>&gt;
                    wrote:<br>
                    <br>
                  </div>
                  <blockquote type="cite">
                    <div>dear all
                      <div><br>
                      </div>
                      <div>I just wanted to make a comment as rapporteur
                        for the community empowerment working party.</div>
                      <div><br>
                      </div>
                      <div>There is some discussion outside our ccwg and
                        outside our working party that the discussion of
                        membership as an option to empower the community
                        could lead to an Individualised membership
                        system, where interested members of the public
                        would join ICANN.</div>
                      <div><br>
                      </div>
                      <div>That is not right.</div>
                      <div><br>
                      </div>
                      <div>That is not what is on the table.</div>
                      <div><br>
                      </div>
                      <div>Membership might be a vehicle to give ICANN's
                        multi stakeholder community more power within
                        ICANN. It would do that through structures that
                        relate to ICANN as it is today, a collection of
                        constituencies organised through SOs and ACs.</div>
                      <div><br>
                      </div>
                      <div>The organisation will remain a bottom up,
                        multistakeholder one. The work through SOs and
                        ACs will continue.</div>
                      <div><br>
                      </div>
                      <div>Nobody has proposed sweeping this away and
                        replacing it with individual membership,
                        recruitment drives, and so on.</div>
                      <div><br>
                      </div>
                      <div>Trust this helps.</div>
                      <div><br>
                      </div>
                      <div>Cheers</div>
                      <div>Jordan </div>
                      <div><br>
                      </div>
                      <div><br>
                      </div>
                      <div>Jordan Carter </div>
                      <div>Rapporteur, WP1<span></span></div>
                      <div><br>
                      </div>
                      <br>
                      <br>
                      -- <br>
                      Jordan Carter<br>
                      Chief Executive, InternetNZ
                      <p><a moz-do-not-send="true"
                          href="tel:%2B64-21-442-649"
                          value="+6421442649" target="_blank">+64-21-442-649</a>
                        | <a moz-do-not-send="true"
                          href="mailto:jordan@internetnz.net.nz"
                          target="_blank">jordan@internetnz.net.nz</a></p>
                      <p>Sent on the run, apologies for brevity<br>
                      </p>
                    </div>
                  </blockquote>
                </div>
              </div>
              <blockquote type="cite">
                <div><span>_______________________________________________</span><br>
                  <span>Accountability-Cross-Community mailing list</span><br>
                  <span><a moz-do-not-send="true"
                      href="mailto:Accountability-Cross-Community@icann.org"
                      target="_blank">Accountability-Cross-Community@icann.org</a></span><br>
                  <span><a moz-do-not-send="true"
href="https://mm.icann.org/mailman/listinfo/accountability-cross-community"
                      target="_blank">https://mm.icann.org/mailman/listinfo/accountability-cross-community</a></span><br>
                </div>
              </blockquote>
            </div>
            <br>
            _______________________________________________<br>
            Accountability-Cross-Community mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:Accountability-Cross-Community@icann.org">Accountability-Cross-Community@icann.org</a><br>
            <a moz-do-not-send="true"
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>
      <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>
  
<br /><br />
<hr style='border:none; color:#909090; background-color:#B0B0B0; height: 1px; width: 99%;' />
<table style='border-collapse:collapse;border:none;'>
        <tr>
                <td style='border:none;padding:0px 15px 0px 8px'>
                        <a href="http://www.avast.com/">
                                <img border=0 src="http://static.avast.com/emails/avast-mail-stamp.png" alt="Avast logo" />
                        </a>
                </td>
                <td>
                        <p style='color:#3d4d5a; font-family:"Calibri","Verdana","Arial","Helvetica"; font-size:12pt;'>
                                This email has been checked for viruses by Avast antivirus software.
                                <br><a href="http://www.avast.com/">www.avast.com</a>
                        </p>
                </td>
        </tr>
</table>
<br />
</body>
</html>