idnits 2.17.00 (12 Aug 2021) /tmp/idnits54233/draft-iesg-nomcom-eligibility-2020-02.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 30, 2020) is 750 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 30, 2020 5 Expires: November 1, 2020 7 Eligibility for the 2020-2021 Nominating Committee 8 draft-iesg-nomcom-eligibility-2020-02 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 any rules that relate to NomCom eligibility or 19 process before IETF 108, and does not set a precedent for the future. 21 Status of This Memo 23 This Internet-Draft is submitted in full conformance with the 24 provisions of BCP 78 and BCP 79. 26 Internet-Drafts are working documents of the Internet Engineering 27 Task Force (IETF). Note that other groups may also distribute 28 working documents as Internet-Drafts. The list of current Internet- 29 Drafts is at https://datatracker.ietf.org/drafts/current/. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet-Drafts as reference 34 material or to cite them other than as "work in progress." 36 This Internet-Draft will expire on November 1, 2020. 38 Copyright Notice 40 Copyright (c) 2020 IETF Trust and the persons identified as the 41 document authors. All rights reserved. 43 This document is subject to BCP 78 and the IETF Trust's Legal 44 Provisions Relating to IETF Documents 45 (https://trustee.ietf.org/license-info) in effect on the date of 46 publication of this document. Please review these documents 47 carefully, as they describe your rights and restrictions with respect 48 to this document. Code Components extracted from this document must 49 include Simplified BSD License text as described in Section 4.e of 50 the Trust Legal Provisions and are provided without warranty as 51 described in the Simplified BSD License. 53 1. Introduction 55 The COVID-19 outbreak, which at the time of this writing has been 56 declared a global pandemic [PANDEMIC], has resulted in the 57 cancellation of the in-person IETF 107 meeting [CANCEL107], resulting 58 in its conversion to a limited-agenda virtual meeting, with remote 59 participation only [VIRTUAL107]. 61 The 2020-2021 Nominating Committee (NomCom) needs to be formed 62 between IETF 107 and IETF 108, and the issue of eligibility of who 63 can serve on that NomCom needs clarification: a one-time 64 interpretation of the eligibility rules is required for this 65 particular exceptional situation. That interpretation will apply to 66 the seating of that NomCom and to any rules that relate to NomCom 67 eligibility or process before the scheduled time for IETF 108. 69 [[CREF1: RFC Editor: Please remove this paragraph.]] This document 70 will be part of BCP 10 when it is published. 72 2. Background 74 Section 4.14 of BCP 10 [RFC8713] includes these requirements for 75 eligibility: 77 Members of the IETF community must have attended at least three of 78 the last five IETF meetings in order to volunteer. 80 The five meetings are the five most recent meetings that ended 81 prior to the date on which the solicitation for NomCom volunteers 82 was submitted for distribution to the IETF community. 84 On 13 March a message was posted to the IETF discussion list 85 [SOLICITINPUT], suggesting two possible interpretations and asking 86 for community input that might include suggesting other 87 interpretations. Discussion over the subsequent two weeks centered 88 around three: 90 1. Do not count IETF 107 at all, for the purpose of NomCom 91 eligibility, as BCP 10 clearly refers to in-person meetings only. 92 NomCom eligibility would, therefore, be based on attendance at 93 IETFs 102 through 106. 95 2. Do not have anyone lose eligibility because of IETF 107, but do 96 count someone as having attended 107, for the purpose of NomCom 97 eligibility, if that person attended the IETF 107 virtual meeting 98 (signed the electronic blue sheet). People could thus gain 99 eligibility from IETF 107, but could not lose eligibility from 100 it, and eligibility would be based on attendance at IETFs 102 101 through 107. 103 3. Count virtual attendance at IETF 107 and consider IETF 107 as one 104 of the last five meetings, so that NomCom eligibility would be 105 based on attendance at IETFs 103 through 107. 107 In judging rough consensus the IESG has considered the arguments and 108 levels of support in favor of and against each option: largely, 109 issues of fairness to newer participants, acceptance of more 110 participants in the volunteer pool, and greatest adherence to the 111 spirit of the rules defined in BCP 10, which is the community- 112 consensus basis we are working from. 114 On 25 March a message was posted to the IETF discussion list 115 [COMMENTDEADLINE], asking for final comments by 30 April. This 116 documents the outcome of that discussion. 118 3. Eligibility for the 2020-2021 Nominating Committee 120 The following text modifies, for the 2020-2021 NomCom selection only, 121 the first two paragraphs (quoted above) of Section 4.14 of BCP 10 122 [RFC8713]: 124 Members of the IETF community must have attended at least three of 125 the last five in-person IETF meetings in order to volunteer. 127 The five meetings are the five most recent in-person meetings that 128 ended prior to the date on which the solicitation for NomCom 129 volunteers was submitted for distribution to the IETF community. 130 Because no IETF 107 in-person meeting was held, for the 2020-2021 131 Nominating Committee those five meetings are IETFs 102, 103, 104, 132 105, and 106. 134 This update is an emergency interpretation of the intent of BCP 10 135 for this current exceptional situation only, and applies only to the 136 2020-2021 NomCom, which is expected to be seated prior to IETF 108, 137 and to any rules that relate to NomCom eligibility or process before 138 IETF 108. It will explicitly not apply to any future NomCom and does 139 not set precedent: an update to BCP 10 will be necessary to address 140 future eligibility, as there will be time for proper community work 141 on such an update (see [ELIGIBILITYDISCUSS]). That update could 142 change any part of the BCP 10 process, including anything specified 143 in this document. 145 4. IANA Considerations 147 There are no IANA considerations for this document. 149 5. Security Considerations 151 This document is purely procedural, and there are no related security 152 considerations. 154 6. References 156 6.1. Normative References 158 [RFC8713] Kucherawy, M., Ed., Hinden, R., Ed., and J. Livingood, 159 Ed., "IAB, IESG, IETF Trust, and IETF LLC Selection, 160 Confirmation, and Recall Process: Operation of the IETF 161 Nominating and Recall Committees", BCP 10, RFC 8713, 162 DOI 10.17487/RFC8713, February 2020, 163 . 165 6.2. Informative References 167 [CANCEL107] 168 The IESG and the IRTF Chair, "IETF 107 Vancouver In-Person 169 Meeting Cancelled", March 2020. 171 Email to the IETF announcement list: 172 https://mailarchive.ietf.org/arch/msg/ietf-announce/ 173 XenAlx4Nw6Jmg69QpXRUOwbzsXY/ 175 [COMMENTDEADLINE] 176 The IESG, "NomCom eligibility & IETF 107", March 2020. 178 Email to the IETF discussion list: 179 https://mailarchive.ietf.org/arch/msg/ietf/ 180 cc3rdjSTz8Vrzps8Ci6fi-VIDq8/ 182 [ELIGIBILITYDISCUSS] 183 IETF, "Mailing list to discuss revision to IETF 184 eligibility procedures", April 2020. 186 Mailing list: https://www.ietf.org/mailman/listinfo/ 187 eligibility-discuss 189 [PANDEMIC] 190 Adhanom Ghebreyesus, T., "WHO Director-General's opening 191 remarks at the media briefing on COVID-19", March 2020. 193 https://www.who.int/dg/speeches/detail/who-director- 194 general-s-opening-remarks-at-the-media-briefing-on-covid- 195 19---11-march-2020 197 [SOLICITINPUT] 198 The IESG, "NomCom eligibility & IETF 107", March 2020. 200 Email to the IETF discussion list: 201 https://mailarchive.ietf.org/arch/msg/ietf/ 202 uBt8FeKeN4CRl7YTDMoy6m8leS0/ 204 [VIRTUAL107] 205 IETF Secretariat, "Important Information for IETF 107 206 Virtual", March 2020. 208 Email to the IETF announcement list: 209 https://mailarchive.ietf.org/arch/msg/ietf-announce/ 210 Gqc4-GIsnvccObQrrciL_Vm0HMU/ 212 Author's Address 214 Barry Leiba 215 FutureWei Technologies 217 Phone: +1 914 433 2749 218 Email: barryleiba@computer.org 219 URI: http://internetmessagingtechnology.org/