The IETF Chair Has a Stand-In
draft-ietf-procon-chair-standin-00

Process Document Consolidation                            L. Eggert, Ed.
Internet-Draft                                                   Mozilla
Intended status: Best Current Practice                   2 November 2026
Expires: 6 May 2027

                     The IETF Chair Has a Stand-In
                   draft-ietf-procon-chair-standin-00

Abstract

   This document defines a stand-in for the IETF Chair, called the
   Acting IETF Chair, in case the IETF Chair becomes indisposed.

About This Document

   This note is to be removed before publishing as an RFC.

   The latest revision of this draft can be found at https://ietf-wg-
   procon.github.io/ietf-chair-may-delegate/draft-ietf-procon-chair-
   standin.html.  Status information for this document may be found at
   https://datatracker.ietf.org/doc/draft-ietf-procon-chair-standin/.

   Discussion of this document takes place on the procon Working Group
   mailing list (mailto:procon@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/browse/procon/.  Subscribe at
   https://www.ietf.org/mailman/listinfo/procon/.

   Source for this draft and an issue tracker can be found at
   https://github.com/ietf-wg-procon/ietf-chair-may-delegate.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on 6 May 2027.

Eggert                     Expires 6 May 2027                   [Page 1]
Internet-Draft        The IETF Chair Has a Stand-In        November 2026

Copyright Notice

   Copyright (c) 2026 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Revised BSD License text as
   described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Revised BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Acting IETF Chair . . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  Background  . . . . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Selection of the Acting IETF Chair  . . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   5.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Changes since draft-eggert-procon-chair-standin-00  . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  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 Section 3.5 of
   [RFC8713], which can take up to six weeks to complete and only allows
   for the permanent replacement of the IETF Chair by another
   individual.)

2.  Acting IETF Chair

   This section describes who may serve as Acting IETF Chair if the IETF
   Chair becomes indisposed.

Eggert                     Expires 6 May 2027                   [Page 2]
Internet-Draft        The IETF Chair Has a Stand-In        November 2026

2.1.  Background

   As described in Section 1, the IETF Chair role is at the moment a
   single point of failure for the organization.  If the IETF Chair
   becomes indisposed, 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 Acting IETF Chair.

      |  Section 7.1.1 of [RFC8713] currently prevents NomCom-ineligible
      |  IETF participants from being signatories on recall petitions.
      |  This includes anyone serving in a NomCom-selected role.  This
      |  could be an issue, since IESG, IAB and LLC Board members may be
      |  first-hand witnesses to reasons that would merit an IETF Chair
      |  recall, but they are currently unable to initiate one directly.

2.2.  Selection of the Acting IETF Chair

   In case the IETF Chair becomes indisposed, or the position becomes
   vacant through resignation, recall or otherwise, the IESG selects and
   announces another Area Director who is willing to serve as Acting
   IETF Chair, who then immediately assumes the role of the IETF Chair.
   The IETF Chair declares when they become indisposed and when they are
   available again.  If the IETF Chair is unable or unwilling to do so,
   or if there is disagreement, the IESG decides.  This does not affect
   the recall process in Section 7 of [RFC8713].  The Acting IETF Chair
   serves until the NomCom appoints a new IETF Chair or the IETF Chair
   is available again.  The ability to serve as Acting IETF Chair is not
   a criterion for the NomCom when selecting Area Directors.

   The Acting IETF Chair holds the full role of the IETF Chair,
   including the ability to delegate [I-D.eggert-procon-chair-delegate],
   and this section applies to them as it does to the IETF Chair.
   Delegations made by the IETF Chair remain in force unless the Acting
   IETF Chair changes them.

   If the IETF Chair's absence is expected to be short, the Acting IETF
   Chair should choose to delay controversial decisions until the IETF
   Chair is available again, while allowing other business to proceed.

3.  Security Considerations

   The usual security considerations [RFC3552] do not apply to this
   document.

Eggert                     Expires 6 May 2027                   [Page 3]
Internet-Draft        The IETF Chair Has a Stand-In        November 2026

4.  IANA Considerations

   This document has no IANA actions.

5.  Acknowledgments

   These individuals suggested improvements to this document:

   *  Alvaro Retana

   *  Brian Carpenter

   *  Eric Rescorla

   *  Jari Arkko

   *  Joel Halpern

   *  Mike Bishop

   *  Mirja Kühlewind

   *  Rob Sayre

   *  Robert Sparks

   *  Ted Lemon

6.  References

6.1.  Normative References

   [RFC8713]  Kucherawy, M., Ed., Hinden, R., Ed., and J. Livingood,
              Ed., "IAB, IESG, IETF Trust, and IETF LLC Selection,
              Confirmation, and Recall Process: Operation of the IETF
              Nominating and Recall Committees", BCP 10, RFC 8713,
              DOI 10.17487/RFC8713, February 2020,
              <https://www.rfc-editor.org/rfc/rfc8713>.

6.2.  Informative References

   [I-D.eggert-procon-chair-delegate]
              Eggert, L., "The IETF Chair May Delegate", Work in
              Progress, Internet-Draft, draft-eggert-procon-chair-
              delegate-02, 29 June 2026,
              <https://datatracker.ietf.org/doc/html/draft-eggert-
              procon-chair-delegate-02>.

Eggert                     Expires 6 May 2027                   [Page 4]
Internet-Draft        The IETF Chair Has a Stand-In        November 2026

   [RFC3552]  Rescorla, E. and B. Korver, "Guidelines for Writing RFC
              Text on Security Considerations", BCP 72, RFC 3552,
              DOI 10.17487/RFC3552, July 2003,
              <https://www.rfc-editor.org/rfc/rfc3552>.

Changes since draft-eggert-procon-chair-standin-00

   *  Rename "stand-in" to "Acting IETF Chair".

   *  Have the IESG select a willing Area Director as Acting IETF Chair,
      instead of the IETF Chair designating one in advance.

   *  Define who decides that the IETF Chair is indisposed or available
      again.

   *  Cover a vacant IETF Chair position.

   *  Give the Acting IETF Chair the full role of the IETF Chair,
      including the ability to delegate.

   *  State that the ability to serve as Acting IETF Chair is not a
      NomCom criterion for selecting Area Directors.

   *  Soften the language and add guidance for short absences.

   *  Editorial fixes.

Author's Address

   Lars Eggert (editor)
   Mozilla
   Stenbergintie 12 B
   FI-02700 Kauniainen
   Finland
   Email: lars@eggert.org
   URI:   https://eggert.org/

Eggert                     Expires 6 May 2027                   [Page 5]