| < draft-iesg-nomcom-eligibility-2020-00.txt | draft-iesg-nomcom-eligibility-2020-01.txt > | |||
|---|---|---|---|---|
| Network Working Group B. Leiba | Network Working Group B. Leiba | |||
| Internet-Draft FutureWei Technologies | Internet-Draft FutureWei Technologies | |||
| Intended status: Best Current Practice April 2, 2020 | Intended status: Best Current Practice April 10, 2020 | |||
| Expires: October 4, 2020 | Expires: October 12, 2020 | |||
| Eligibility for the 2020-2021 Nominating Committee | Eligibility for the 2020-2021 Nominating Committee | |||
| draft-iesg-nomcom-eligibility-2020-00 | draft-iesg-nomcom-eligibility-2020-01 | |||
| Abstract | Abstract | |||
| The 2020-2021 Nominating Committee (NomCom) needs to be formed | The 2020-2021 Nominating Committee (NomCom) needs to be formed | |||
| between IETF 107 and IETF 108, and the issue of eligibility of who | between IETF 107 and IETF 108, and the issue of eligibility of who | |||
| can serve on that NomCom needs clarification. This document provides | can serve on that NomCom needs clarification. This document provides | |||
| a one-time interpretation of the eligibility rules that is required | a one-time interpretation of the eligibility rules that is required | |||
| for the exceptional situation of the cancellation of the in-person | for the exceptional situation of the cancellation of the in-person | |||
| IETF 107 meeting. This document only affects the seating of the | IETF 107 meeting. This document only affects the seating of the | |||
| 2020-2021 NomCom, and does not set a precedent for the future. | 2020-2021 NomCom and any rules that relate to NomCom eligibility or | |||
| process before IETF 108, and does not set a precedent for the future. | ||||
| Status of This Memo | Status of This Memo | |||
| This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
| provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF). Note that other groups may also distribute | Task Force (IETF). Note that other groups may also distribute | |||
| working documents as Internet-Drafts. The list of current Internet- | working documents as Internet-Drafts. The list of current Internet- | |||
| Drafts is at https://datatracker.ietf.org/drafts/current/. | Drafts is at https://datatracker.ietf.org/drafts/current/. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| This Internet-Draft will expire on October 4, 2020. | This Internet-Draft will expire on October 12, 2020. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2020 IETF Trust and the persons identified as the | Copyright (c) 2020 IETF Trust and the persons identified as the | |||
| document authors. All rights reserved. | document authors. All rights reserved. | |||
| This document is subject to BCP 78 and the IETF Trust's Legal | This document is subject to BCP 78 and the IETF Trust's Legal | |||
| Provisions Relating to IETF Documents | Provisions Relating to IETF Documents | |||
| (https://trustee.ietf.org/license-info) in effect on the date of | (https://trustee.ietf.org/license-info) in effect on the date of | |||
| publication of this document. Please review these documents | publication of this document. Please review these documents | |||
| skipping to change at page 2, line 19 ¶ | skipping to change at page 2, line 20 ¶ | |||
| The COVID-19 outbreak, which at the time of this writing has been | The COVID-19 outbreak, which at the time of this writing has been | |||
| declared a global pandemic [PANDEMIC], has resulted in the | declared a global pandemic [PANDEMIC], has resulted in the | |||
| cancellation of the in-person IETF 107 meeting [CANCEL107], resulting | cancellation of the in-person IETF 107 meeting [CANCEL107], resulting | |||
| in its conversion to a limited-agenda virtual meeting, with remote | in its conversion to a limited-agenda virtual meeting, with remote | |||
| participation only. | participation only. | |||
| The 2020-2021 Nominating Committee (NomCom) needs to be formed | The 2020-2021 Nominating Committee (NomCom) needs to be formed | |||
| between IETF 107 and IETF 108, and the issue of eligibility of who | between IETF 107 and IETF 108, and the issue of eligibility of who | |||
| can serve on that NomCom needs clarification: a one-time | can serve on that NomCom needs clarification: a one-time | |||
| interpretation of the eligibility rules is required for this | interpretation of the eligibility rules is required for this | |||
| particular exceptional situation, given the tight timeframe for | particular exceptional situation. That interpretation will apply to | |||
| seating this year's NomCom. | the seating of that NomCom and to any rules that relate to NomCom | |||
| eligibility or process before IETF 108. | ||||
| [[CREF1: RFC Editor: Please remove this paragraph.]] This document | ||||
| will be part of BCP 10 when it is published. | ||||
| 2. Background | 2. Background | |||
| Section 4.14 of BCP 10 [RFC8713] includes these requirements for | Section 4.14 of BCP 10 [RFC8713] includes these requirements for | |||
| eligibility: | eligibility: | |||
| 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. | |||
| The five meetings are the five most recent meetings that ended | The five meetings are the five most recent meetings that ended | |||
| skipping to change at page 3, line 20 ¶ | skipping to change at page 3, line 25 ¶ | |||
| levels of support in favor of and against each option: largely, | levels of support in favor of and against each option: largely, | |||
| issues of fairness to newer participants, acceptance of more | issues of fairness to newer participants, acceptance of more | |||
| participants in the volunteer pool, and greatest adherence to the | participants in the volunteer pool, and greatest adherence to the | |||
| spirit of the rules defined in BCP 10, which is the community- | spirit of the rules defined in BCP 10, which is the community- | |||
| consensus basis we are working from. | consensus basis we are working from. | |||
| On 25 March a message was posted to the IETF discussion list | On 25 March a message was posted to the IETF discussion list | |||
| [COMMENTDEADLINE], asking for final comments by 30 April. This | [COMMENTDEADLINE], asking for final comments by 30 April. This | |||
| document serves as a recommendation for review during that last call | document serves as a recommendation for review during that last call | |||
| period. As such, this document could substantively change, depending | period. As such, this document could substantively change, depending | |||
| upon the last-call discussion. [[CREF1: Note: The previous sentence | upon the last-call discussion. [[CREF2: Note: The previous sentence | |||
| will be removed before publication.]] | will be removed before publication.]] | |||
| 3. Eligibility for the 2020-2021 Nominating Committee | 3. Eligibility for the 2020-2021 Nominating Committee | |||
| The following text modifies, for the 2020-2021 NomCom selection only, | The following text modifies, for the 2020-2021 NomCom selection only, | |||
| the first two paragraphs (quoted above) of Section 4.14 of BCP 10 | the first two paragraphs (quoted above) of Section 4.14 of BCP 10 | |||
| [RFC8713]: | [RFC8713]: | |||
| 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. | |||
| 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 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 IETFs 102, 103, 104, | Nominating Committee those five meetings are IETFs 102, 103, 104, | |||
| 105, and 106. | 105, and 106. | |||
| This update is an emergency interpretation of the intent of BCP 10 | This update is an emergency interpretation of the intent of BCP 10 | |||
| for this current exceptional situation only, and applies only to the | for this current exceptional situation only, and applies only to the | |||
| 2020-2021 NomCom, which is expected to be seated prior to IETF 108. | 2020-2021 NomCom, which is expected to be seated prior to IETF 108, | |||
| It will explicitly not apply to any future NomCom and does not set | and to any rules that relate to NomCom eligibility or process before | |||
| precedent: another update to BCP 10 will be necessary to address | IETF 108. It will explicitly not apply to any future NomCom and does | |||
| not set precedent: an update to BCP 10 will be necessary to address | ||||
| future eligibility, as there will be time for proper community work | future eligibility, as there will be time for proper community work | |||
| on such an update. | on such an update. That update could change any part of the BCP 10 | |||
| process, including anything specified in this document. | ||||
| 4. IANA Considerations | 4. IANA Considerations | |||
| There are no IANA considerations for this document. | There are no IANA considerations for this document. | |||
| 5. Security Considerations | 5. Security Considerations | |||
| This document is purely procedural, and there are no related security | This document is purely procedural, and there are no related security | |||
| considerations. | considerations. | |||
| End of changes. 9 change blocks. | ||||
| 13 lines changed or deleted | 20 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||