wdiff rfc8788xml2.original.xml rfc8788.xml

<?xml version="1.0" encoding="US-ASCII"?> version='1.0' encoding='UTF-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?xml-stylesheet type='text/xsl' href='http://xml2rfc.ietf.org/authoring/rfc2629.xslt' ?>

<?rfc comments="yes" ?>
<?rfc inline="yes" ?>
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?>
<?rfc toc="no" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc compact="no"?>
<?rfc subcompact="no"?> "rfc2629-xhtml.ent">
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="bcp" consensus="true"
submissionType="IETF" ipr="trust200902"
  docName="draft-iesg-nomcom-eligibility-2020-03"> number="8788"
docName="draft-iesg-nomcom-eligibility-2020-03" obsoletes="" updates=""
xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 2.44.0 -->
  <front>
    <title abbrev="2020-2021 NomCom Eligibility">
    Eligibility for the 2020-2021 Nominating Committee
    </title>
   <seriesInfo name="RFC" value="8788"/>
   <seriesInfo name="BCP" value="10"/>
    <author initials='B.' initials="B." surname="Leiba" fullname='Barry Leiba'> fullname="Barry Leiba">
      <organization>FutureWei Technologies</organization>
      <address>
        <phone>+1 914 433 2749</phone>
        <email>barryleiba@computer.org</email>
        <uri>http://internetmessagingtechnology.org/</uri>
      </address>
    </author>

    <date/>
    <date month="May" year="2020"/>
    <area>General</area>
    <workgroup></workgroup>
    <workgroup/>

<keyword>nomcom</keyword>

    <abstract>
      <t>
The 2020-2021 Nominating Committee (NomCom) is to be formed between
the IETF 107 and IETF 108, 108 meetings, and the issue of eligibility of
who can serve on that NomCom needs clarification. This document
provides a one-time interpretation of the eligibility rules that is
required for the exceptional situation of the cancellation of the
in-person IETF 107 meeting.  This document only affects the seating of
the 2020-2021 NomCom and any rules or processes that relate to NomCom
eligibility before IETF 108, and 108; it does not set a precedent for to be applied
in the future.
      </t>
    </abstract>
  </front>
  <middle>
    <section anchor="intro" title="Introduction"> numbered="true" toc="default">
      <name>Introduction</name>
      <t>
The COVID-19 outbreak, which at the time of this writing has been was
declared a global pandemic <xref target="PANDEMIC"/>, target="PANDEMIC" format="default"/>,
has resulted in the cancellation of the in-person IETF 107 meeting
<xref target="CANCEL107"/>, resulting target="CANCEL107" format="default"/>. This resulted in its
conversion to a limited-agenda virtual meeting, meeting with a limited agenda and remote
participation only <xref target="VIRTUAL107"/>. target="VIRTUAL107" format="default"/>.
      </t>
      <t>
The 2020-2021 Nominating Committee (NomCom) is to be formed between the IETF 107
and IETF 108, 108 meetings, and the issue of eligibility of who can serve on that NomCom
needs clarification: a one-time interpretation of the eligibility rules is
required for this particular exceptional situation. That interpretation will
apply to the seating of that NomCom and to any rules or processes that relate
to NomCom eligibility before the scheduled time for IETF 108.
      </t>
      <t>
<cref>RFC Editor: Please remove this paragraph.</cref>
This document will be part of BCP 10 when it is published.
      </t>
    </section>
    <section anchor="background" title="Background"> numbered="true" toc="default">
      <name>Background</name>
      <t>
Section 4.14 of BCP 10
<xref target="RFC8713"/> target="RFC8713" sectionFormat="of"
section="4.14"></xref> (BCP 10) includes these requirements for eligibility:
        <list style="none">
        <t>
   Members
      </t>
     <blockquote>

   <t>Members of the IETF community must have attended at least three of
   the last five IETF meetings in order to volunteer.
        </t>
        <t>
   The volunteer.</t>

   <t>The five meetings are the five most recent meetings that ended prior
   to the date on which the solicitation for NomCom volunteers was
   submitted for distribution to the IETF community.
        </t>
        </list>
      </t> community.</t>

     </blockquote>
      <t>
On 13 March 2020, a message was posted to the IETF discussion list
<xref target="SOLICITINPUT"/>, target="SOLICITINPUT" format="default"/> suggesting two possible
interpretations and asking for community input that might include
suggesting other interpretations.  Discussion over the subsequent two
weeks centered around three:
        <list style="numbers">
        <t>
      </t>
      <ol spacing="normal" type="1">
        <li>
Do not count IETF 107 at all, for the purpose of NomCom eligibility, as BCP 10 clearly refers to in-person meetings only.  NomCom eligibility would, therefore, be based on attendance at IETFs 102 through 106.
        </t>
        <t>
        </li>
        <li>
Do not have anyone lose eligibility because of IETF 107, but do count someone as having attended 107, for the purpose of NomCom eligibility, if that person attended the IETF 107 virtual meeting (signed the electronic blue sheet).  People could thus gain eligibility from IETF 107, but could not lose eligibility from it, and eligibility would be based on attendance at IETFs 102 through 107.
        </t>
        <t>
        </li>
        <li>
Count virtual attendance at IETF 107 and consider IETF 107 as one of the last five meetings, so that NomCom eligibility would be based on attendance at IETFs 103 through 107.
        </t>
        </list>
      </t>
        </li>
      </ol>
      <t>
In judging rough consensus consensus, the IESG has considered the arguments and
levels of support in favor of for and against each option. The arguments largely involved issues of fairness to newer participants, acceptance of more participants in the volunteer pool, and greatest adherence to the spirit of the rules defined in BCP 10, which is the community-consensus basis we are working from.
      </t>
      <t>
On 25 March 2020, a message was posted to the IETF discussion list
<xref target="COMMENTDEADLINE"/>, target="COMMENTDEADLINE" format="default"/> asking for final
comments by 30 April. April 2020.  This documents the outcome of that discussion with the choice of interpretation 1, above.
      </t>
    </section>
    <section anchor="eligibility" title="Eligibility numbered="true" toc="default">
      <name>Eligibility for the 2020-2021 Nominating Committee"> Committee</name>
      <t>
The following text modifies, for the 2020-2021 NomCom cycle only, the first two paragraphs (quoted above) of Section 4.14 of BCP 10 <xref target="RFC8713"/>:
        <list style="none">
        <t> target="RFC8713" sectionFormat="of"
section="4.14"></xref> (BCP 10) as follows:
      </t>
      <ul spacing="normal" empty="true">
        <li>
   Members of the IETF community must have attended at least three of
   the last five in-person IETF meetings in order to volunteer.
        </t>
        <t>
        </li>
        <li>
   The five meetings are the five most recent in-person meetings that
   ended prior to the date on which the solicitation for NomCom
   volunteers was submitted for distribution to the IETF community.
   Because no IETF 107 in-person meeting was held, for the 2020-2021
   Nominating Committee Committee, those five meetings are
   IETFs 102, 103, 104, 105, and 106.
        </t>
        </list>
      </t>
        </li>
      </ul>
      <t>
This update is an emergency interpretation of the intent of BCP 10 for
this current exceptional situation only, and only.  It applies only to the
2020-2021 NomCom, which is expected to be seated prior to IETF 108,
and to any rules or processes that relate to NomCom eligibility before
IETF 108.  It will explicitly not apply to any future NomCom and does
not set precedent: an update to BCP 10 will be necessary to address
future eligibility, as there will be time for proper community work on
such an update (see <xref target="ELIGIBILITYDISCUSS"/>). target="ELIGIBILITYDISCUSS"
format="default"/>).  That update could change any part of the BCP 10
process, including anything specified in this document.
      </t>
    </section>
    <section title="IANA Considerations"> numbered="true" toc="default">
      <name>IANA Considerations</name>
      <t>
        There are
       This document has no IANA considerations for this document. actions.
      </t>
    </section>
    <section title="Security Considerations"> numbered="true" toc="default">
      <name>Security Considerations</name>
      <t>
        This document is purely procedural, and procedural; there are no related
        security considerations.
      </t>
    </section>
  </middle>
  <back>
    <references title="Normative References">
      <?rfc include="reference.RFC.8713" ?>
    <references>
      <name>References</name>
      <references>
        <name>Normative References</name>
        <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8713.xml"/>
      </references>

    <references title="Informative References">
      <references>

        <name>Informative References</name>
        <reference anchor="CANCEL107"> anchor="CANCEL107" target="https://mailarchive.ietf.org/arch/msg/ietf-announce/XenAlx4Nw6Jmg69QpXRUOwbzsXY">
          <front>
          <title>IETF
            <title>Subject: IETF 107 Vancouver In-Person Meeting Cancelled</title>
            <author initials="" surname="The IESG and the IRTF Chair" fullname="The IESG and the IRTF Chair">
              <organization>IETF</organization>
            </author>
            <date day="10" month="March" year="2020" /> year="2020"/>
          </front>
        <annotation>
          Email
         <refcontent>message to the IETF announcement list:
          https://mailarchive.ietf.org/arch/msg/ietf-announce/XenAlx4Nw6Jmg69QpXRUOwbzsXY/
        </annotation> list</refcontent>
        </reference>

        <reference anchor="COMMENTDEADLINE"> anchor="COMMENTDEADLINE" target="https://mailarchive.ietf.org/arch/msg/ietf/cc3rdjSTz8Vrzps8Ci6fi-VIDq8/">
          <front>
          <title>NomCom
            <title>Subject: Re: NomCom eligibility &amp; IETF 107</title>
            <author initials="" surname="The IESG" fullname="The IESG">
              <organization>IETF</organization>
            </author>
            <date day="13" month="March" year="2020" /> year="2020"/>
          </front>
        <annotation>
          Email
	    <refcontent>message to the IETF discussion list:
          https://mailarchive.ietf.org/arch/msg/ietf/cc3rdjSTz8Vrzps8Ci6fi-VIDq8/
        </annotation> list</refcontent>
        </reference>

        <reference anchor="ELIGIBILITYDISCUSS"> anchor="ELIGIBILITYDISCUSS" target="https://www.ietf.org/mailman/listinfo/eligibility-discuss">
          <front>
            <title>Mailing list to discuss revision to IETF eligibility procedures</title>
            <author initials="" surname="IETF" fullname="IETF">
              <organization>IETF</organization>
            </author>
          <date month="April" year="2020" />
            <date/>
          </front>
        <annotation>
          Mailing list:
          https://www.ietf.org/mailman/listinfo/eligibility-discuss
        </annotation>
        </reference>

        <reference anchor="PANDEMIC"> anchor="PANDEMIC" target="https://www.who.int/dg/speeches/detail/who-director-general-s-opening-remarks-at-the-media-briefing-on-covid-19---11-march-2020">
          <front>
            <title>WHO Director-General's opening remarks at the media briefing on COVID-19</title>
            <author initials="T" surname="Adhanom Ghebreyesus" fullname="Tedros Adhanom Ghebreyesus">
              <organization>World Health Organization</organization>
            </author>
            <date month="March" year="2020" /> year="2020"/>
          </front>
        <annotation>
https://www.who.int/dg/speeches/detail/who-director-general-s-opening-remarks-at-the-media-briefing-on-covid-19---11-march-2020
        </annotation>

        </reference>
        <reference anchor="SOLICITINPUT"> anchor="SOLICITINPUT" target="https://mailarchive.ietf.org/arch/msg/ietf/uBt8FeKeN4CRl7YTDMoy6m8leS0/">
          <front>
            <title>NomCom eligibility &amp; IETF 107</title>
            <author initials="" surname="The IESG" fullname="The IESG">
              <organization>IETF</organization>
            </author>
            <date month="March" year="2020" /> year="2020"/>
          </front>
        <annotation>
          Email
	    <refcontent>message to the IETF discussion list:
          https://mailarchive.ietf.org/arch/msg/ietf/uBt8FeKeN4CRl7YTDMoy6m8leS0/
        </annotation> list</refcontent>
        </reference>

        <reference anchor="VIRTUAL107"> anchor="VIRTUAL107" target="https://mailarchive.ietf.org/arch/msg/ietf-announce/cVDlJ4fVJIkfakBysTfsFchERCs/">
          <front>
            <title>Important Information for IETF 107 Virtual</title>
            <author initials="" surname="IETF Secretariat" fullname="IETF Secretariat">
              <organization>IETF</organization>
            </author>
            <date month="March" year="2020" /> year="2020"/>
          </front>
        <annotation>
          Email
	    <refcontent>message to the IETF announcement list:
          https://mailarchive.ietf.org/arch/msg/ietf-announce/cVDlJ4fVJIkfakBysTfsFchERCs/

        </annotation> list</refcontent>
        </reference>
      </references>
    </references>
  </back>
</rfc>