<?xml version="1.0" encoding="US-ASCII"?>
<!-- This template is for creating an Internet Draft using xml2rfc,
     which is available here: http://xml.resource.org. -->
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [

<!ENTITY RFC3777    PUBLIC '' 'http://xml.resource.org/public/rfc/bibxml/reference.RFC.3777.xml'>
]>

<?xml-stylesheet type='text/xsl' href='http://xml.resource.org/authoring/rfc2629.xslt' ?>
<?rfc toc="yes" ?>
<?rfc tocompact="no" ?>
<?rfc tocindent="no" ?>
<?rfc comments="yes" ?>
<?rfc inline="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?>
<?rfc compact="yes"?>
<?rfc subcompact="yes"?>

<rfc
  category="bcp"
  ipr="trust200902"
  updates="3777"
  docName="draft-leiba-3777upd-eligibility-00">

  <front>
    <title abbrev="NonCom Eligibility Update">
    Update to RFC 3777 to Clarify Nominating Committee Eligibility of IETF Leadership
    </title>

    <author initials='B.' surname='Leiba' fullname='Barry Leiba'>
      <organization>Huawei Technologies</organization>
      <address>
        <phone>+1 646 827 0648</phone>
        <email>barryleiba@computer.org</email>
        <uri>http://internetmessagingtechnology.org/</uri>
      </address>
    </author>

    <date/>
    <area>General</area>
    <workgroup></workgroup>

    <abstract>
      <t>
        RFC 3777 specifies that "sitting members" of
        the IAB and IESG "may not volunteer to serve on the nominating commitee".
        Since that document was written the IAOC was formed, and that body is not
        covered by RFC 3777.  There is also uncertainty about whether ex-officio members
        and liaisons are included as "sitting members".  This document clarifies those situations.
     </t>
    </abstract>

  </front>

  <middle>
    <section anchor="intro" title="Introduction">
      <t>
        RFC 3777 <xref target="RFC3777"/> defines the nominating committee process.
        One of the key points in the process and in the selection of the NomCom is
        that the IETF wants to avoid having its top leadership be self-selecting:
        the leaders should not be the ones who choose the leaders.
        The selection of the NomCom, therefore, excludes those individuals who are
        in top leadership positions currently.
      </t>
      <t>
        That said, it would be bad to eliminate too many people who are in good
        positions to understand well the IETF process -- those individuals will give
        important perspective to the NomCom and will help ensure that the people it
        selects for the leadership roles will be qualified to do those jobs.
        There's an advantage, then, to excluding only those necessary to achieve
        the "not self-selecting" goal, and no others.
      </t>
      <t>
        RFC 3777 specifies that "sitting members" of
        the IAB and IESG "may not volunteer to serve on the nominating committee".
        Since that document was written the IAOC was formed, and that body is not
        covered by RFC 3777.  There is also uncertainty about whether ex-officio members
        liaisons, and such are included as "sitting members".
        This document clarifies those situations, with the understanding that the intent
        of RFC 3777 was to exclude those currently in IETF leadership positions, or who
        would otherwise have a conflict of interest, from voting on the selection of
        the new leadership.
      </t>
      <t>
        This document also excludes individuals who are directly paid for their work with
        the IETF, and who, therefore, have a direct personal financial incentive in
        the selection of the leadership boards.  In practice, those people are unlikely
        to volunteer for the NomCom anyway, so this addition makes little practical change.
      </t>
      <t>
        In order to allow the largest reasonable list of potential NomCom members,
        we do not want to exclude those at lower levels of IETF leadership.
        In particular, this document does *not* exclude participation from working
        group chairs, IRTF research group chairs, members of directorates and special
        review teams, and members of other advisory bodies such as the RSOC.
      </t>
    </section>

    <section anchor="upd" title="Replacement of RFC 3777, Section 4, Paragraph 15">
      <t>
        The following two paragraphs replace RFC 3777, Section 4, paragraph 15 in its entirety.
      </t>
      <t>
        15.1  Members of the Internet Society Board of Trustees and sitting
        members of the IAB, the IESG, and the IAOC, including members
        in ex-officio positions, and not including liaisons, may not volunteer
        to serve as voting members of the nominating committee.
      </t>
      <t>
        15.2  People serving in the Secretariat and the RFC Editor may not volunteer to
        serve as voting members of the nominating committee.
      </t>
    </section>

    <section anchor="security" title="Security Considerations">
      <t>
        This is a procedural document, and is entirely unrelated to security.
      </t>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>
        No IANA actions are requested by this document, and the RFC Editor is asked to remove
        this section before publication.
      </t>
    </section>  
  </middle>

  <back>
    <references title="Normative References">
      &RFC3777;
    </references>
  </back>
</rfc>
