Nomcom Eligibility
draft-duke-elegy-rfc8989bis-00
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Martin Duke | ||
| Last updated | 2022-08-11 | ||
| Replaces | draft-duke-gendispatch-rfc8989bis | ||
| Replaced by | RFC 9389 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-elegy-rfc8989bis | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The IETF Nominating Committee (NomCom) appoints candidates to most IETF leadership committee. RFC8713 provides criteria for membership on Nomcom that attempts to ensure that NomCom volunteers are members of the loosely defined IETF community, by requiring in-person attendance in three of the past five in- person meetings. In 2020 and 2021, the IETF had six consecutive fully online plenary meetings that drove rapid advancement in remote meeting technologies and procedures, including an experiment that included remote attendance for NomCom eligibility. This document updates RFC8713 by building a new set of eligibility criteria from first principles, with consideration for the increased salience of remote attendance.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)