Status of This Memo

This memo documents an Internet Best Current Practice.¶

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on BCPs is available in Section 2 of RFC 7841.¶

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained athttps://www.rfc-editor.org/info/rfc8788.¶

Copyright Notice

Copyright (c) 2020 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.¶

Table of Contents

1.Introduction

The COVID-19 outbreak, which at the time of this writing wasdeclared a global pandemic[PANDEMIC],has resulted in the cancellation of the in-person IETF 107 meeting[CANCEL107]. This resulted in itsconversion to a virtual meeting with a limited agenda and remoteparticipation only[VIRTUAL107].¶

The 2020-2021 Nominating Committee (NomCom) is to be formed between the IETF 107and IETF 108 meetings, and the issue of eligibility of who can serve on that NomComneeds clarification: a one-time interpretation of the eligibility rules isrequired for this particular exceptional situation. That interpretation willapply to the seating of that NomCom and to any rules or processes that relateto NomCom eligibility before the scheduled time for IETF 108.¶

2.Background

Section 4.14 of [RFC8713] (BCP 10) includes these requirements for eligibility:¶

Members of the IETF community must have attended at least three of the last five IETF meetings in order to volunteer.¶

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.¶

On 13 March 2020, a message was posted to the IETF discussion list[SOLICITINPUT] suggesting two possibleinterpretations and asking for community input that might includesuggesting other interpretations. Discussion over the subsequent twoweeks centered around three:¶

1. 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.¶
2. 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.¶
3. 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.¶

In judging rough consensus, the IESG has considered the arguments andlevels of support 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.¶

On 25 March 2020, a message was posted to the IETF discussion list[COMMENTDEADLINE] asking for finalcomments by 30 April 2020. This documents the outcome of that discussion with the choice of interpretation 1, above.¶

3.Eligibility for the 2020-2021 Nominating Committee

The following text modifies, for the 2020-2021 NomCom cycle only, the first two paragraphs (quoted above) ofSection 4.14 of [RFC8713] (BCP 10) as follows:¶

• Members of the IETF community must have attended at least three of the last five in-person IETF meetings in order to volunteer.¶
• 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, those five meetings are IETFs 102, 103, 104, 105, and 106.¶

This update is an emergency interpretation of the intent of BCP 10 forthis current exceptional situation only. It applies only to the2020-2021 NomCom, which is expected to be seated prior to IETF 108,and to any rules or processes that relate to NomCom eligibility beforeIETF 108. It will explicitly not apply to any future NomCom and doesnot set precedent: an update to BCP 10 will be necessary to addressfuture eligibility, as there will be time for proper community work onsuch an update (see[ELIGIBILITYDISCUSS]). That update could change any part of the BCP 10process, including anything specified in this document.¶

Author's Address