rfc8788xml2.original.xml   rfc8788.xml 
<?xml version="1.0" encoding="US-ASCII"?> <?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd"> <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?xml-stylesheet type='text/xsl' href='http://xml2rfc.ietf.org/authoring/rfc2629 <rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="bcp" consensus="true"
.xslt' ?> submissionType="IETF" ipr="trust200902" number="8788"
docName="draft-iesg-nomcom-eligibility-2020-03" obsoletes="" updates=""
<?rfc comments="yes" ?> xml:lang="en" tocInclude="true" symRefs="true" sortRefs="true" version="3">
<?rfc inline="yes" ?> <!-- xml2rfc v2v3 conversion 2.44.0 -->
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?>
<?rfc toc="no" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc compact="no"?>
<?rfc subcompact="no"?>
<rfc
category="bcp"
submissionType="IETF"
ipr="trust200902"
docName="draft-iesg-nomcom-eligibility-2020-03">
<front> <front>
<title abbrev="2020-2021 NomCom Eligibility"> <title abbrev="2020-2021 NomCom Eligibility">
Eligibility for the 2020-2021 Nominating Committee Eligibility for the 2020-2021 Nominating Committee
</title> </title>
<seriesInfo name="RFC" value="8788"/>
<author initials='B.' surname="Leiba" fullname='Barry Leiba'> <seriesInfo name="BCP" value="10"/>
<author initials="B." surname="Leiba" fullname="Barry Leiba">
<organization>FutureWei Technologies</organization> <organization>FutureWei Technologies</organization>
<address> <address>
<phone>+1 914 433 2749</phone> <phone>+1 914 433 2749</phone>
<email>barryleiba@computer.org</email> <email>barryleiba@computer.org</email>
<uri>http://internetmessagingtechnology.org/</uri> <uri>http://internetmessagingtechnology.org/</uri>
</address> </address>
</author> </author>
<date month="May" year="2020"/>
<date/>
<area>General</area> <area>General</area>
<workgroup></workgroup> <workgroup/>
<keyword>nomcom</keyword>
<abstract> <abstract>
<t> <t>
The 2020-2021 Nominating Committee (NomCom) is to be formed between IETF 107 and The 2020-2021 Nominating Committee (NomCom) is to be formed between
IETF 108, and the issue of eligibility of who can serve on that NomCom needs cl the IETF 107 and IETF 108 meetings, and the issue of eligibility of
arification. This document provides a one-time interpretation of the eligibility who can serve on that NomCom needs clarification. This document
rules that is required for the exceptional situation of the cancellation of the provides a one-time interpretation of the eligibility rules that is
in-person IETF 107 meeting. This document only affects the seating of the 2020 required for the exceptional situation of the cancellation of the
-2021 NomCom and any rules or processes that relate to NomCom eligibility before in-person IETF 107 meeting. This document only affects the seating of
IETF 108, and does not set a precedent for the future. the 2020-2021 NomCom and any rules or processes that relate to NomCom
eligibility before IETF 108; it does not set a precedent to be applied
in the future.
</t> </t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section anchor="intro" title="Introduction"> <section anchor="intro" numbered="true" toc="default">
<name>Introduction</name>
<t> <t>
The COVID-19 outbreak, which at the time of this writing has been declared a glo The COVID-19 outbreak, which at the time of this writing was
bal pandemic <xref target="PANDEMIC"/>, has resulted in the cancellation of the declared a global pandemic <xref target="PANDEMIC" format="default"/>,
in-person IETF 107 meeting <xref target="CANCEL107"/>, resulting in its conversi has resulted in the cancellation of the in-person IETF 107 meeting
on to a limited-agenda virtual meeting, with remote participation only <xref tar <xref target="CANCEL107" format="default"/>. This resulted in its
get="VIRTUAL107"/>. conversion to a virtual meeting with a limited agenda and remote
participation only <xref target="VIRTUAL107" format="default"/>.
</t> </t>
<t> <t>
The 2020-2021 Nominating Committee (NomCom) is to be formed between IETF 107 and The 2020-2021 Nominating Committee (NomCom) is to be formed between the IETF 107
IETF 108, and the issue of eligibility of who can serve on that NomCom needs cl and IETF 108 meetings, and the issue of eligibility of who can serve on that Nom
arification: a one-time interpretation of the eligibility rules is required for Com
this particular exceptional situation. That interpretation will apply to the sea needs clarification: a one-time interpretation of the eligibility rules is
ting of that NomCom and to any rules or processes that relate to NomCom eligibil required for this particular exceptional situation. That interpretation will
ity before the scheduled time for IETF 108. 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>
</section>
<section anchor="background" numbered="true" toc="default">
<name>Background</name>
<t> <t>
<cref>RFC Editor: Please remove this paragraph.</cref> <xref target="RFC8713" sectionFormat="of"
This document will be part of BCP 10 when it is published. section="4.14"></xref> (BCP 10) includes these requirements for eligibility:
</t> </t>
</section> <blockquote>
<section anchor="background" title="Background"> <t>Members of the IETF community must have attended at least three of
<t> the last five IETF meetings in order to volunteer.</t>
Section 4.14 of BCP 10 <xref target="RFC8713"/> includes these requirements for
eligibility: <t>The five meetings are the five most recent meetings that ended prior
<list style="none">
<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 five meetings are the five most recent meetings that ended prior
to the date on which the solicitation for NomCom volunteers was to the date on which the solicitation for NomCom volunteers was
submitted for distribution to the IETF community. submitted for distribution to the IETF community.</t>
</t>
</list> </blockquote>
</t>
<t> <t>
On 13 March a message was posted to the IETF discussion list <xref target="SOLIC On 13 March 2020, a message was posted to the IETF discussion list
ITINPUT"/>, suggesting two possible interpretations and asking for community inp <xref target="SOLICITINPUT" format="default"/> suggesting two possible
ut that might include suggesting other interpretations. Discussion over the sub interpretations and asking for community input that might include
sequent two weeks centered around three: suggesting other interpretations. Discussion over the subsequent two
<list style="numbers"> weeks centered around three:
<t> </t>
<ol spacing="normal" type="1">
<li>
Do not count IETF 107 at all, for the purpose of NomCom eligibility, as BCP 10 c learly refers to in-person meetings only. NomCom eligibility would, therefore, be based on attendance at IETFs 102 through 106. Do not count IETF 107 at all, for the purpose of NomCom eligibility, as BCP 10 c learly refers to in-person meetings only. NomCom eligibility would, therefore, be based on attendance at IETFs 102 through 106.
</t> </li>
<t> <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 atte nded the IETF 107 virtual meeting (signed the electronic blue sheet). People co uld 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. 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 atte nded the IETF 107 virtual meeting (signed the electronic blue sheet). People co uld 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> </li>
<t> <li>
Count virtual attendance at IETF 107 and consider IETF 107 as one of the last fi ve meetings, so that NomCom eligibility would be based on attendance at IETFs 10 3 through 107. Count virtual attendance at IETF 107 and consider IETF 107 as one of the last fi ve meetings, so that NomCom eligibility would be based on attendance at IETFs 10 3 through 107.
</t> </li>
</list> </ol>
</t>
<t> <t>
In judging rough consensus the IESG has considered the arguments and levels of s In judging rough consensus, the IESG has considered the arguments and
upport in favor of and against each option. The arguments largely involved issue levels of support for and against each option. The arguments largely involved is
s of fairness to newer participants, acceptance of more participants in the volu sues of fairness to newer participants, acceptance of more participants in the v
nteer pool, and greatest adherence to the spirit of the rules defined in BCP 10, olunteer pool, and greatest adherence to the spirit of the rules defined in BCP
which is the community-consensus basis we are working from. 10, which is the community-consensus basis we are working from.
</t> </t>
<t> <t>
On 25 March a message was posted to the IETF discussion list <xref target="COMME On 25 March 2020, a message was posted to the IETF discussion list
NTDEADLINE"/>, asking for final comments by 30 April. This documents the outcom <xref target="COMMENTDEADLINE" format="default"/> asking for final
e of that discussion with the choice of interpretation 1, above. comments by 30 April 2020. This documents the outcome of that discussion with t
he choice of interpretation 1, above.
</t> </t>
</section> </section>
<section anchor="eligibility" numbered="true" toc="default">
<section anchor="eligibility" title="Eligibility for the 2020-2021 Nominatin <name>Eligibility for the 2020-2021 Nominating Committee</name>
g Committee">
<t> <t>
The following text modifies, for the 2020-2021 NomCom cycle only, the first two 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"/>: paragraphs (quoted above) of <xref target="RFC8713" sectionFormat="of"
<list style="none"> section="4.14"></xref> (BCP 10) as follows:
<t> </t>
<ul spacing="normal" empty="true">
<li>
Members of the IETF community must have attended at least three of Members of the IETF community must have attended at least three of
the last five in-person IETF meetings in order to volunteer. the last five in-person IETF meetings in order to volunteer.
</t> </li>
<t> <li>
The five meetings are the five most recent in-person meetings that The five meetings are the five most recent in-person meetings that
ended prior to the date on which the solicitation for NomCom ended prior to the date on which the solicitation for NomCom
volunteers was submitted for distribution to the IETF community. volunteers was submitted for distribution to the IETF community.
Because no IETF 107 in-person meeting was held, for the 2020-2021 Because no IETF 107 in-person meeting was held, for the 2020-2021
Nominating Committee those five meetings are Nominating Committee, those five meetings are
IETFs 102, 103, 104, 105, and 106. IETFs 102, 103, 104, 105, and 106.
</t> </li>
</list> </ul>
</t>
<t> <t>
This update is an emergency interpretation of the intent of BCP 10 for this curr This update is an emergency interpretation of the intent of BCP 10 for
ent exceptional situation only, and applies only to the 2020-2021 NomCom, which this current exceptional situation only. It applies only to the
is expected to be seated prior to IETF 108, and to any rules or processes that r 2020-2021 NomCom, which is expected to be seated prior to IETF 108,
elate to NomCom eligibility before IETF 108. It will explicitly not apply to an and to any rules or processes that relate to NomCom eligibility before
y future NomCom and does not set precedent: an update to BCP 10 will be necessar IETF 108. It will explicitly not apply to any future NomCom and does
y to address future eligibility, as there will be time for proper community work not set precedent: an update to BCP 10 will be necessary to address
on such an update (see <xref target="ELIGIBILITYDISCUSS"/>). That update could future eligibility, as there will be time for proper community work on
change any part of the BCP 10 process, including anything specified in this doc such an update (see <xref target="ELIGIBILITYDISCUSS"
ument. format="default"/>). That update could change any part of the BCP 10
process, including anything specified in this document.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="IANA Considerations"> <name>IANA Considerations</name>
<t> <t>
There are no IANA considerations for this document. This document has no IANA actions.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="Security Considerations"> <name>Security Considerations</name>
<t> <t>
This document is purely procedural, and there are no related security co This document is purely procedural; there are no related
nsiderations. security considerations.
</t> </t>
</section> </section>
</middle> </middle>
<back> <back>
<references title="Normative References"> <references>
<?rfc include="reference.RFC.8713" ?> <name>References</name>
</references> <references>
<name>Normative References</name>
<references title="Informative References"> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="https://xml
2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8713.xml"/>
<reference anchor="CANCEL107"> </references>
<front> <references>
<title>IETF 107 Vancouver In-Person Meeting Cancelled</title>
<author initials="" surname="The IESG and the IRTF Chair" fullname="Th
e IESG and the IRTF Chair">
<organization>IETF</organization>
</author>
<date month="March" year="2020" />
</front>
<annotation>
Email to the IETF announcement list:
https://mailarchive.ietf.org/arch/msg/ietf-announce/XenAlx4Nw6Jmg69QpX
RUOwbzsXY/
</annotation>
</reference>
<reference anchor="COMMENTDEADLINE"> <name>Informative References</name>
<front> <reference anchor="CANCEL107" target="https://mailarchive.ietf.org/arch/
<title>NomCom eligibility &amp; IETF 107</title> msg/ietf-announce/XenAlx4Nw6Jmg69QpXRUOwbzsXY">
<author initials="" surname="The IESG" fullname="The IESG"> <front>
<organization>IETF</organization> <title>Subject: IETF 107 Vancouver In-Person Meeting Cancelled</titl
</author> e>
<date month="March" year="2020" /> <author initials="" surname="The IESG and the IRTF Chair" fullname="
</front> The IESG and the IRTF Chair">
<annotation> <organization>IETF</organization>
Email to the IETF discussion list: </author>
https://mailarchive.ietf.org/arch/msg/ietf/cc3rdjSTz8Vrzps8Ci6fi-VIDq8 <date day="10" month="March" year="2020"/>
/ </front>
</annotation> <refcontent>message to the IETF announcement list</refcontent>
</reference> </reference>
<reference anchor="ELIGIBILITYDISCUSS"> <reference anchor="COMMENTDEADLINE" target="https://mailarchive.ietf.org
<front> /arch/msg/ietf/cc3rdjSTz8Vrzps8Ci6fi-VIDq8/">
<title>Mailing list to discuss revision to IETF eligibility procedures <front>
</title> <title>Subject: Re: NomCom eligibility &amp; IETF 107</title>
<author initials="" surname="IETF" fullname="IETF"> <author initials="" surname="The IESG" fullname="The IESG">
<organization>IETF</organization> <organization>IETF</organization>
</author> </author>
<date month="April" year="2020" /> <date day="13" month="March" year="2020"/>
</front> </front>
<annotation> <refcontent>message to the IETF discussion list</refcontent>
Mailing list: </reference>
https://www.ietf.org/mailman/listinfo/eligibility-discuss
</annotation>
</reference>
<reference anchor="PANDEMIC"> <reference anchor="ELIGIBILITYDISCUSS" target="https://www.ietf.org/mail
<front> man/listinfo/eligibility-discuss">
<title>WHO Director-General's opening remarks at the media briefing on <front>
COVID-19</title> <title>Mailing list to discuss revision to IETF eligibility procedur
<author initials="T" surname="Adhanom Ghebreyesus" fullname="Tedros Ad es</title>
hanom Ghebreyesus"> <author initials="" surname="IETF" fullname="IETF">
<organization>World Health Organization</organization> <organization>IETF</organization>
</author> </author>
<date month="March" year="2020" /> <date/>
</front> </front>
<annotation> </reference>
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"> <reference anchor="PANDEMIC" target="https://www.who.int/dg/speeches/det
<front> ail/who-director-general-s-opening-remarks-at-the-media-briefing-on-covid-19---1
<title>NomCom eligibility &amp; IETF 107</title> 1-march-2020">
<author initials="" surname="The IESG" fullname="The IESG"> <front>
<organization>IETF</organization> <title>WHO Director-General's opening remarks at the media briefing
</author> on COVID-19</title>
<date month="March" year="2020" /> <author initials="T" surname="Adhanom Ghebreyesus" fullname="Tedros
</front> Adhanom Ghebreyesus">
<annotation> <organization>World Health Organization</organization>
Email to the IETF discussion list: </author>
https://mailarchive.ietf.org/arch/msg/ietf/uBt8FeKeN4CRl7YTDMoy6m8leS0 <date month="March" year="2020"/>
/ </front>
</annotation>
</reference>
<reference anchor="VIRTUAL107"> </reference>
<front> <reference anchor="SOLICITINPUT" target="https://mailarchive.ietf.org/ar
<title>Important Information for IETF 107 Virtual</title> ch/msg/ietf/uBt8FeKeN4CRl7YTDMoy6m8leS0/">
<author initials="" surname="IETF Secretariat" fullname="IETF Secretar <front>
iat"> <title>NomCom eligibility &amp; IETF 107</title>
<organization>IETF</organization> <author initials="" surname="The IESG" fullname="The IESG">
</author> <organization>IETF</organization>
<date month="March" year="2020" /> </author>
</front> <date month="March" year="2020"/>
<annotation> </front>
Email to the IETF announcement list: <refcontent>message to the IETF discussion list</refcontent>
https://mailarchive.ietf.org/arch/msg/ietf-announce/cVDlJ4fVJIkfakBysT </reference>
fsFchERCs/
</annotation> <reference anchor="VIRTUAL107" target="https://mailarchive.ietf.org/arch
</reference> /msg/ietf-announce/cVDlJ4fVJIkfakBysTfsFchERCs/">
<front>
<title>Important Information for IETF 107 Virtual</title>
<author initials="" surname="IETF Secretariat" fullname="IETF Secret
ariat">
<organization>IETF</organization>
</author>
<date month="March" year="2020"/>
</front>
<refcontent>message to the IETF announcement list</refcontent>
</reference>
</references>
</references> </references>
</back> </back>
</rfc> </rfc>
 End of changes. 38 change blocks. 
209 lines changed or deleted 185 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/