idnits 2.17.00 (12 Aug 2021) /tmp/idnits54053/draft-iesg-nomcom-eligibility-2020-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (April 2, 2020) is 778 days in the past. Is this intentional? Checking references for intended status: Best Current Practice ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group B. Leiba 3 Internet-Draft FutureWei Technologies 4 Intended status: Best Current Practice April 2, 2020 5 Expires: October 4, 2020 7 Eligibility for the 2020-2021 Nominating Committee 8 draft-iesg-nomcom-eligibility-2020-00 10 Abstract 12 The 2020-2021 Nominating Committee (NomCom) needs to be formed 13 between IETF 107 and IETF 108, and the issue of eligibility of who 14 can serve on that NomCom needs clarification. This document provides 15 a one-time interpretation of the eligibility rules that is required 16 for the exceptional situation of the cancellation of the in-person 17 IETF 107 meeting. This document only affects the seating of the 18 2020-2021 NomCom, and does not set a precedent for the future. 20 Status of This Memo 22 This Internet-Draft is submitted in full conformance with the 23 provisions of BCP 78 and BCP 79. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF). Note that other groups may also distribute 27 working documents as Internet-Drafts. The list of current Internet- 28 Drafts is at https://datatracker.ietf.org/drafts/current/. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 This Internet-Draft will expire on October 4, 2020. 37 Copyright Notice 39 Copyright (c) 2020 IETF Trust and the persons identified as the 40 document authors. All rights reserved. 42 This document is subject to BCP 78 and the IETF Trust's Legal 43 Provisions Relating to IETF Documents 44 (https://trustee.ietf.org/license-info) in effect on the date of 45 publication of this document. Please review these documents 46 carefully, as they describe your rights and restrictions with respect 47 to this document. Code Components extracted from this document must 48 include Simplified BSD License text as described in Section 4.e of 49 the Trust Legal Provisions and are provided without warranty as 50 described in the Simplified BSD License. 52 1. Introduction 54 The COVID-19 outbreak, which at the time of this writing has been 55 declared a global pandemic [PANDEMIC], has resulted in the 56 cancellation of the in-person IETF 107 meeting [CANCEL107], resulting 57 in its conversion to a limited-agenda virtual meeting, with remote 58 participation only. 60 The 2020-2021 Nominating Committee (NomCom) needs to be formed 61 between IETF 107 and IETF 108, and the issue of eligibility of who 62 can serve on that NomCom needs clarification: a one-time 63 interpretation of the eligibility rules is required for this 64 particular exceptional situation, given the tight timeframe for 65 seating this year's NomCom. 67 2. Background 69 Section 4.14 of BCP 10 [RFC8713] includes these requirements for 70 eligibility: 72 Members of the IETF community must have attended at least three of 73 the last five IETF meetings in order to volunteer. 75 The five meetings are the five most recent meetings that ended 76 prior to the date on which the solicitation for NomCom volunteers 77 was submitted for distribution to the IETF community. 79 On 13 March a message was posted to the IETF discussion list 80 [SOLICITINPUT], suggesting two possible interpretations and asking 81 for community input that might include suggesting other 82 interpretations. Discussion over the subsequent two weeks centered 83 around three: 85 1. Do not count IETF 107 at all, for the purpose of NomCom 86 eligibility, as BCP 10 clearly refers to in-person meetings only. 87 NomCom eligibility would, therefore, be based on attendance at 88 IETFs 102 through 106. 90 2. Do not have anyone lose eligibility because of IETF 107, but do 91 count someone as having attended 107, for the purpose of NomCom 92 eligibility, if that person attended the IETF 107 virtual meeting 93 (signed the electronic blue sheet). People could thus gain 94 eligibility from IETF 107, but could not lose eligibility from 95 it, and eligibility would be based on attendance at IETFs 102 96 through 107. 98 3. Count virtual attendance at IETF 107 and consider IETF 107 as one 99 of the last five meetings, so that NomCom eligibility would be 100 based on attendance at IETFs 103 through 107. 102 In judging rough consensus the IESG has considered the arguments and 103 levels of support in favor of and against each option: largely, 104 issues of fairness to newer participants, acceptance of more 105 participants in the volunteer pool, and greatest adherence to the 106 spirit of the rules defined in BCP 10, which is the community- 107 consensus basis we are working from. 109 On 25 March a message was posted to the IETF discussion list 110 [COMMENTDEADLINE], asking for final comments by 30 April. This 111 document serves as a recommendation for review during that last call 112 period. As such, this document could substantively change, depending 113 upon the last-call discussion. [[CREF1: Note: The previous sentence 114 will be removed before publication.]] 116 3. Eligibility for the 2020-2021 Nominating Committee 118 The following text modifies, for the 2020-2021 NomCom selection only, 119 the first two paragraphs (quoted above) of Section 4.14 of BCP 10 120 [RFC8713]: 122 Members of the IETF community must have attended at least three of 123 the last five in-person IETF meetings in order to volunteer. 125 The five meetings are the five most recent in-person meetings that 126 ended prior to the date on which the solicitation for NomCom 127 volunteers was submitted for distribution to the IETF community. 128 Because no IETF 107 in-person was held, for the 2020-2021 129 Nominating Committee those five meetings are IETFs 102, 103, 104, 130 105, and 106. 132 This update is an emergency interpretation of the intent of BCP 10 133 for this current exceptional situation only, and applies only to the 134 2020-2021 NomCom, which is expected to be seated prior to IETF 108. 135 It will explicitly not apply to any future NomCom and does not set 136 precedent: another update to BCP 10 will be necessary to address 137 future eligibility, as there will be time for proper community work 138 on such an update. 140 4. IANA Considerations 142 There are no IANA considerations for this document. 144 5. Security Considerations 146 This document is purely procedural, and there are no related security 147 considerations. 149 6. References 151 6.1. Normative References 153 [RFC8713] Kucherawy, M., Ed., Hinden, R., Ed., and J. Livingood, 154 Ed., "IAB, IESG, IETF Trust, and IETF LLC Selection, 155 Confirmation, and Recall Process: Operation of the IETF 156 Nominating and Recall Committees", BCP 10, RFC 8713, 157 DOI 10.17487/RFC8713, February 2020, 158 . 160 6.2. Informative References 162 [CANCEL107] 163 The IESG and the IRTF Chair, "IETF 107 Vancouver In-Person 164 Meeting Cancelled", March 2020. 166 Email to the IETF discussion list: 167 https://mailarchive.ietf.org/arch/msg/ietf-announce/ 168 XenAlx4Nw6Jmg69QpXRUOwbzsXY/ 170 [COMMENTDEADLINE] 171 The IESG, "NomCom eligibility & IETF 107", March 2020. 173 Email to the IETF discussion list: 174 https://mailarchive.ietf.org/arch/msg/ietf/ 175 cc3rdjSTz8Vrzps8Ci6fi-VIDq8/ 177 [PANDEMIC] 178 Adhanom Ghebreyesus, T., "WHO Director-General's opening 179 remarks at the media briefing on COVID-19", March 2020. 181 https://www.who.int/dg/speeches/detail/who-director- 182 general-s-opening-remarks-at-the-media-briefing-on-covid- 183 19---11-march-2020 185 [SOLICITINPUT] 186 The IESG, "NomCom eligibility & IETF 107", March 2020. 188 Email to the IETF discussion list: 189 https://mailarchive.ietf.org/arch/msg/ietf/ 190 uBt8FeKeN4CRl7YTDMoy6m8leS0/ 192 Author's Address 194 Barry Leiba 195 FutureWei Technologies 197 Phone: +1 914 433 2749 198 Email: barryleiba@computer.org 199 URI: http://internetmessagingtechnology.org/