]> The IETF Chair Has an Emergency Stand-In Mozilla
Stenbergintie 12 B Kauniainen 02700 FI lars@eggert.org https://eggert.org/
Process Document Consolidation This document defines a succession of emergency stand-ins in case the IETF Chair becomes incapacitated. About This Document The latest revision of this draft can be found at . Status information for this document may be found at . Discussion of this document takes place on the procon Working Group mailing list (), which is archived at . Subscribe at . Source for this draft and an issue tracker can be found at .
Introduction The role of the IETF Chair is a single point of failure for the organization, with no defined processes for allowing others to quickly and/or temporarily take over aspects of the role if the IETF Chair becomes partially or fully unable to serve. (The defined process is that for "mid-term vacancies" per , which can take up to six weeks to complete and only allows for the permanent replacement of the IETF Chair by another individual.)
Emergency Stand-In This section describes who may stand in for the IETF Chair in case of emergency if they become unable to fulfill their duties.
Background As described in , the IETF Chair role is at the moment a single point of failure for the organization. In an emergency that incapacitated the IETF Chair, a recall petition followed by executing a "mid-term vacancy" replacement would need to be executed to name a new IETF Chair. This process will likely take several weeks at best, during which time there is no defined stand-in for the IETF Chair.
Delegation of the IETF Chair Role This document proposes that the IETF Chair, at their sole discretion, designates another Area Director as their stand-in immediately upon being seated and at anytime afterward in case changes need to be made. In case the IETF Chair becomes incapacitated, the stand-in will automatically and immediately assume the role of the IETF Chair. This emergency delegation ends as soon as the NomCom appoints a new IETF Chair or the IETF Chair declares themselves fit for duty again.
Security Considerations The usual security considerations do not apply to this document.
IANA Considerations This document has no IANA actions.
Acknowledgments These individuals suggested improvements to this document:
  • Alvaro Retana
  • Brian Carpenter
  • Jari Arkko
References Normative References IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees The process by which the members of the IAB and IESG, some Trustees of the IETF Trust, and some Directors of the IETF Administration LLC (IETF LLC) are selected, confirmed, and recalled is specified in this document. This document is based on RFC 7437. Only those updates required to reflect the changes introduced by IETF Administrative Support Activity (IASA) 2.0 have been included. Any other changes will be addressed in future documents. This document obsoletes RFC 7437 and RFC 8318. Informative References Guidelines for Writing RFC Text on Security Considerations All RFCs are required to have a Security Considerations section. Historically, such sections have been relatively weak. This document provides guidelines to RFC authors on how to write a good Security Considerations section. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.