rfc8788.original.v2v3.xml   rfc8788.form.xml 
<?xml version='1.0' encoding='utf-8'?> <?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent"> <!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="0000" docName="draft-iesg-nomcom
<?rfc comments="yes" ?> -eligibility-2020-03" obsoletes="" updates="" xml:lang="en" tocInclude="true" sy
<?rfc inline="yes" ?> mRefs="true" sortRefs="true" version="3">
<?rfc iprnotified="no" ?>
<?rfc strict="yes" ?>
<?rfc toc="yes" ?>
<?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" obsoletes="" updates="" xml:lang="en" tocInclude="tr
ue" symRefs="true" sortRefs="true" version="3">
<!-- xml2rfc v2v3 conversion 2.44.0 --> <!-- xml2rfc v2v3 conversion 2.44.0 -->
<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="Internet-Draft" value="draft-iesg-nomcom-eligibility-2020- <seriesInfo name="RFC" value="0000"/>
03"/> <seriesInfo name="BCP" value="999"/>
<author initials="B." surname="Leiba" fullname="Barry Leiba"> <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/> <date month="May" year="2020"/>
<area>General</area> <area>General</area>
<workgroup/> <workgroup/>
<!--[rfced] Please insert any keywords (beyond those that appear in
the title) for use on https://www.rfc-editor.org/search. -->
<keyword>example</keyword>
<abstract> <abstract>
<t> <t>
The 2020-2021 Nominating Committee (NomCom) is to be formed between IETF 107 and IETF 108, and the issue of eligibility of who can serve on that NomCom needs cl arification. 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 does not set a precedent for the future. The 2020-2021 Nominating Committee (NomCom) is to be formed between IETF 107 and IETF 108, and the issue of eligibility of who can serve on that NomCom needs cl arification. 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 does not set a precedent for the future.
</t> </t>
</abstract> </abstract>
</front> </front>
<middle> <middle>
<section anchor="intro" numbered="true" toc="default"> <section anchor="intro" numbered="true" toc="default">
<name>Introduction</name> <name>Introduction</name>
<t> <t>
skipping to change at line 54 skipping to change at line 52
The 2020-2021 Nominating Committee (NomCom) is to be formed between IETF 107 and IETF 108, and the issue of eligibility of who can serve on that NomCom needs cl arification: a one-time interpretation of the eligibility rules is required for this particular exceptional situation. That interpretation will apply to the sea ting of that NomCom and to any rules or processes that relate to NomCom eligibil ity before the scheduled time for IETF 108. The 2020-2021 Nominating Committee (NomCom) is to be formed between IETF 107 and IETF 108, and the issue of eligibility of who can serve on that NomCom needs cl arification: a one-time interpretation of the eligibility rules is required for this particular exceptional situation. That interpretation will apply to the sea ting of that NomCom and to any rules or processes that relate to NomCom eligibil ity before the scheduled time for IETF 108.
</t> </t>
<t> <t>
<cref>RFC Editor: Please remove this paragraph.</cref> <cref>RFC Editor: Please remove this paragraph.</cref>
This document will be part of BCP 10 when it is published. This document will be part of BCP 10 when it is published.
</t> </t>
</section> </section>
<section anchor="background" numbered="true" toc="default"> <section anchor="background" numbered="true" toc="default">
<name>Background</name> <name>Background</name>
<t> <t>
Section 4.14 of BCP 10 <xref target="RFC8713" format="default"/> includes these <xref target="RFC8713" sectionFormat="of"
requirements for eligibility: section="4.14"></xref> (BCP 10) includes these requirements for eligibility:
</t> </t>
<ul spacing="normal"> <blockquote>
<li> <t>
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 IETF meetings in order to volunteer. the last five IETF meetings in order to volunteer.
</li> </t>
<li> <t>
The five meetings are the five most recent meetings that ended prior 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.
</li> </t>
</ul> </blockquote>
<t> <t>
On 13 March a message was posted to the IETF discussion list <xref target="SOLIC ITINPUT" format="default"/>, suggesting two possible interpretations and asking for community input that might include suggesting other interpretations. Discus sion over the subsequent two weeks centered around three: On 13 March a message was posted to the IETF discussion list <xref target="SOLIC ITINPUT" format="default"/>, suggesting two possible interpretations and asking for community input that might include suggesting other interpretations. Discus sion over the subsequent two weeks centered around three:
</t> </t>
<ol spacing="normal" type="1"> <ol spacing="normal" type="1">
<li> <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.
</li> </li>
<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 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.
</li> </li>
skipping to change at line 91 skipping to change at line 90
<t> <t>
In judging rough consensus the IESG has considered the arguments and levels of s upport in favor of and against each option. The arguments largely involved issue s of fairness to newer participants, acceptance of more participants in the volu nteer pool, and greatest adherence to the spirit of the rules defined in BCP 10, which is the community-consensus basis we are working from. In judging rough consensus the IESG has considered the arguments and levels of s upport in favor of and against each option. The arguments largely involved issue s of fairness to newer participants, acceptance of more participants in the volu nteer 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>
<t> <t>
On 25 March a message was posted to the IETF discussion list <xref target="COMME NTDEADLINE" format="default"/>, asking for final comments by 30 April. This doc uments the outcome of that discussion with the choice of interpretation 1, above . On 25 March a message was posted to the IETF discussion list <xref target="COMME NTDEADLINE" format="default"/>, asking for final comments by 30 April. This doc uments the outcome of that discussion with the choice of interpretation 1, above .
</t> </t>
</section> </section>
<section anchor="eligibility" numbered="true" toc="default"> <section anchor="eligibility" numbered="true" toc="default">
<name>Eligibility for the 2020-2021 Nominating Committee</name> <name>Eligibility for the 2020-2021 Nominating Committee</name>
<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" forma paragraphs (quoted above) of <xref target="RFC8713" sectionFormat="of"
t="default"/>: section="4.14"></xref> (BCP 10):
</t> </t>
<ul spacing="normal"> <ul spacing="normal" empty="true">
<li> <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.
</li> </li>
<li> <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
skipping to change at line 132 skipping to change at line 132
</section> </section>
</middle> </middle>
<back> <back>
<references> <references>
<name>References</name> <name>References</name>
<references> <references>
<name>Normative References</name> <name>Normative References</name>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="https://xml 2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8713.xml"/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="https://xml 2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.8713.xml"/>
</references> </references>
<references> <references>
<name>Informative References</name> <name>Informative References</name>
<reference anchor="CANCEL107"> <reference anchor="CANCEL107" target="https://mailarchive.ietf.org/arch/ msg/ietf-announce/XenAlx4Nw6Jmg69QpXRUOwbzsXY">
<front> <front>
<title>IETF 107 Vancouver In-Person Meeting Cancelled</title> <title>Subject: IETF 107 Vancouver In-Person Meeting Cancelled</titl e>
<author initials="" surname="The IESG and the IRTF Chair" fullname=" The IESG and the IRTF Chair"> <author initials="" surname="The IESG and the IRTF Chair" fullname=" The IESG and the IRTF Chair">
<organization>IETF</organization> <organization>IETF</organization>
</author> </author>
<date month="March" year="2020"/> <date day="10" month="March" year="2020"/>
</front> </front>
<annotation> <refcontent>message to the IETF announcement list</refcontent>
Email to the IETF announcement list:
https://mailarchive.ietf.org/arch/msg/ietf-announce/XenAlx4Nw6Jmg69QpX
RUOwbzsXY/
</annotation>
</reference> </reference>
<reference anchor="COMMENTDEADLINE">
<reference anchor="COMMENTDEADLINE" target="https://mailarchive.ietf.org
/arch/msg/ietf/cc3rdjSTz8Vrzps8Ci6fi-VIDq8/">
<front> <front>
<title>NomCom eligibility &amp; IETF 107</title> <title>Subject: Re: NomCom eligibility &amp; IETF 107</title>
<author initials="" surname="The IESG" fullname="The IESG"> <author initials="" surname="The IESG" fullname="The IESG">
<organization>IETF</organization> <organization>IETF</organization>
</author> </author>
<date month="March" year="2020"/> <date day="13" month="March" year="2020"/>
</front> </front>
<annotation> <refcontent>message to the IETF discussion list</refcontent>
Email to the IETF discussion list:
https://mailarchive.ietf.org/arch/msg/ietf/cc3rdjSTz8Vrzps8Ci6fi-VIDq8
/
</annotation>
</reference> </reference>
<reference anchor="ELIGIBILITYDISCUSS">
<reference anchor="ELIGIBILITYDISCUSS" target="https://www.ietf.org/mail
man/listinfo/eligibility-discuss">
<front> <front>
<title>Mailing list to discuss revision to IETF eligibility procedur es</title> <title>Mailing list to discuss revision to IETF eligibility procedur es</title>
<author initials="" surname="IETF" fullname="IETF"> <author initials="" surname="IETF" fullname="IETF">
<organization>IETF</organization> <organization>IETF</organization>
</author> </author>
<date month="April" year="2020"/> <date/>
</front> </front>
<annotation>
Mailing list:
https://www.ietf.org/mailman/listinfo/eligibility-discuss
</annotation>
</reference> </reference>
<reference anchor="PANDEMIC">
<reference anchor="PANDEMIC" target="https://www.who.int/dg/speeches/det
ail/who-director-general-s-opening-remarks-at-the-media-briefing-on-covid-19---1
1-march-2020">
<front> <front>
<title>WHO Director-General's opening remarks at the media briefing on COVID-19</title> <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"> <author initials="T" surname="Adhanom Ghebreyesus" fullname="Tedros Adhanom Ghebreyesus">
<organization>World Health Organization</organization> <organization>World Health Organization</organization>
</author> </author>
<date month="March" year="2020"/> <date month="March" year="2020"/>
</front> </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>
<reference anchor="SOLICITINPUT"> <reference anchor="SOLICITINPUT" target="https://mailarchive.ietf.org/ar ch/msg/ietf/uBt8FeKeN4CRl7YTDMoy6m8leS0/">
<front> <front>
<title>NomCom eligibility &amp; IETF 107</title> <title>NomCom eligibility &amp; IETF 107</title>
<author initials="" surname="The IESG" fullname="The IESG"> <author initials="" surname="The IESG" fullname="The IESG">
<organization>IETF</organization> <organization>IETF</organization>
</author> </author>
<date month="March" year="2020"/> <date month="March" year="2020"/>
</front> </front>
<annotation> <refcontent>message to the IETF discussion list</refcontent>
Email to the IETF discussion list:
https://mailarchive.ietf.org/arch/msg/ietf/uBt8FeKeN4CRl7YTDMoy6m8leS0
/
</annotation>
</reference> </reference>
<reference anchor="VIRTUAL107">
<reference anchor="VIRTUAL107" target="https://mailarchive.ietf.org/arch
/msg/ietf-announce/cVDlJ4fVJIkfakBysTfsFchERCs/">
<front> <front>
<title>Important Information for IETF 107 Virtual</title> <title>Important Information for IETF 107 Virtual</title>
<author initials="" surname="IETF Secretariat" fullname="IETF Secret ariat"> <author initials="" surname="IETF Secretariat" fullname="IETF Secret ariat">
<organization>IETF</organization> <organization>IETF</organization>
</author> </author>
<date month="March" year="2020"/> <date month="March" year="2020"/>
</front> </front>
<annotation> <refcontent>message to the IETF announcement list</refcontent>
Email to the IETF announcement list:
https://mailarchive.ietf.org/arch/msg/ietf-announce/cVDlJ4fVJIkfakBysT
fsFchERCs/
</annotation>
</reference> </reference>
</references> </references>
</references> </references>
</back> </back>
</rfc> </rfc>
 End of changes. 29 change blocks. 
70 lines changed or deleted 52 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/