<?xml version='1.0' encoding='utf-8'?>
<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
<!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.4.9) -->
<rfc xmlns:xi="http://www.w3.org/2001/XInclude" ipr="trust200902" docName="draft-ietf-procon-chair-standin-00" category="bcp" consensus="true" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true" version="3">
  <!-- xml2rfc v2v3 conversion 3.34.1 -->
  <front>
    <title>The IETF Chair Has a Stand-In</title>
    <seriesInfo name="Internet-Draft" value="draft-ietf-procon-chair-standin-00"/>
    <author initials="L." surname="Eggert" fullname="Lars Eggert" role="editor">
      <organization>Mozilla</organization>
      <address>
        <postal>
          <street>Stenbergintie 12 B</street>
          <city>Kauniainen</city>
          <code>02700</code>
          <country>FI</country>
        </postal>
        <email>lars@eggert.org</email>
        <uri>https://eggert.org/</uri>
      </address>
    </author>
    <date year="2026" month="November" day="02"/>
    <workgroup>Process Document Consolidation</workgroup>
    <abstract>
      <?line 27?>

<t>This document defines a stand-in for the IETF Chair, called the
Acting IETF Chair, in case the IETF Chair becomes indisposed.</t>
    </abstract>
    <note removeInRFC="true">
      <name>About This Document</name>
      <t>
        The latest revision of this draft can be found at <eref target="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 <eref target="https://datatracker.ietf.org/doc/draft-ietf-procon-chair-standin/"/>.
      </t>
      <t>
        Discussion of this document takes place on the
        procon Working Group mailing list (<eref target="mailto:procon@ietf.org"/>),
        which is archived at <eref target="https://mailarchive.ietf.org/arch/browse/procon/"/>.
        Subscribe at <eref target="https://www.ietf.org/mailman/listinfo/procon/"/>.
      </t>
      <t>Source for this draft and an issue tracker can be found at
        <eref target="https://github.com/ietf-wg-procon/ietf-chair-may-delegate"/>.</t>
    </note>
  </front>
  <middle>
    <?line 32?>

<section anchor="intro">
      <name>Introduction</name>
      <t>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 <xref section="3.5" sectionFormat="of" target="RFC8713"/>, which can take up to six weeks to complete and only
allows for the permanent replacement of the IETF Chair by another
individual.)</t>
    </section>
    <section anchor="acting-ietf-chair">
      <name>Acting IETF Chair</name>
      <t>This section describes who may serve as Acting IETF Chair if the IETF Chair
becomes indisposed.</t>
      <section anchor="background">
        <name>Background</name>
        <t>As described in <xref target="intro"/>, 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.</t>
        <aside>
          <t><xref section="7.1.1" sectionFormat="of" target="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.</t>
        </aside>
      </section>
      <section anchor="selection-of-the-acting-ietf-chair">
        <name>Selection of the Acting IETF Chair</name>
        <t>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 <xref section="7" sectionFormat="of" target="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.</t>
        <t>The Acting IETF Chair holds the full role of the IETF Chair, including
the ability to delegate <xref target="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.</t>
        <t>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.</t>
      </section>
    </section>
    <section anchor="security-considerations">
      <name>Security Considerations</name>
      <t>The usual security considerations <xref target="RFC3552"/> do not apply to this
document.</t>
    </section>
    <section anchor="iana-considerations">
      <name>IANA Considerations</name>
      <t>This document has no IANA actions.</t>
    </section>
    <section anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>These individuals suggested improvements to this document:</t>
      <ul spacing="normal">
        <li>
          <t>Alvaro Retana</t>
        </li>
        <li>
          <t>Brian Carpenter</t>
        </li>
        <li>
          <t>Eric Rescorla</t>
        </li>
        <li>
          <t>Jari Arkko</t>
        </li>
        <li>
          <t>Joel Halpern</t>
        </li>
        <li>
          <t>Mike Bishop</t>
        </li>
        <li>
          <t>Mirja Kühlewind</t>
        </li>
        <li>
          <t>Rob Sayre</t>
        </li>
        <li>
          <t>Robert Sparks</t>
        </li>
        <li>
          <t>Ted Lemon</t>
        </li>
      </ul>
    </section>
  </middle>
  <back>
    <references anchor="sec-combined-references">
      <name>References</name>
      <references anchor="sec-normative-references">
        <name>Normative References</name>
        <reference anchor="RFC8713">
          <front>
            <title>IAB, IESG, IETF Trust, and IETF LLC Selection, Confirmation, and Recall Process: Operation of the IETF Nominating and Recall Committees</title>
            <author fullname="M. Kucherawy" initials="M." role="editor" surname="Kucherawy"/>
            <author fullname="R. Hinden" initials="R." role="editor" surname="Hinden"/>
            <author fullname="J. Livingood" initials="J." role="editor" surname="Livingood"/>
            <date month="February" year="2020"/>
            <abstract>
              <t>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.</t>
              <t>This document obsoletes RFC 7437 and RFC 8318.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="10"/>
          <seriesInfo name="RFC" value="8713"/>
          <seriesInfo name="DOI" value="10.17487/RFC8713"/>
        </reference>
      </references>
      <references anchor="sec-informative-references">
        <name>Informative References</name>
        <reference anchor="I-D.eggert-procon-chair-delegate">
          <front>
            <title>The IETF Chair May Delegate</title>
            <author fullname="Lars Eggert" initials="L." surname="Eggert">
              <organization>Mozilla</organization>
            </author>
            <date day="29" month="June" year="2026"/>
            <abstract>
              <t>   This document affirms that the IETF Chair may delegate some of their
   responsibilities to other Area Directors, and updates several
   existing RFCs to enable that.

              </t>
            </abstract>
          </front>
          <seriesInfo name="Internet-Draft" value="draft-eggert-procon-chair-delegate-02"/>
        </reference>
        <reference anchor="RFC3552">
          <front>
            <title>Guidelines for Writing RFC Text on Security Considerations</title>
            <author fullname="E. Rescorla" initials="E." surname="Rescorla"/>
            <author fullname="B. Korver" initials="B." surname="Korver"/>
            <date month="July" year="2003"/>
            <abstract>
              <t>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.</t>
            </abstract>
          </front>
          <seriesInfo name="BCP" value="72"/>
          <seriesInfo name="RFC" value="3552"/>
          <seriesInfo name="DOI" value="10.17487/RFC3552"/>
        </reference>
      </references>
    </references>
    <?line 115?>

<!-- markdownlint-disable MD022 -->

<section numbered="false" anchor="changes-since-draft-eggert-procon-chair-standin-00">
      <name>Changes since draft-eggert-procon-chair-standin-00</name>
      <!-- markdownlint-enable MD022 -->

<ul spacing="normal">
        <li>
          <t>Rename "stand-in" to "Acting IETF Chair".</t>
        </li>
        <li>
          <t>Have the IESG select a willing Area Director as Acting IETF Chair,
instead of the IETF Chair designating one in advance.</t>
        </li>
        <li>
          <t>Define who decides that the IETF Chair is indisposed or available
again.</t>
        </li>
        <li>
          <t>Cover a vacant IETF Chair position.</t>
        </li>
        <li>
          <t>Give the Acting IETF Chair the full role of the IETF Chair, including
the ability to delegate.</t>
        </li>
        <li>
          <t>State that the ability to serve as Acting IETF Chair is not a NomCom
criterion for selecting Area Directors.</t>
        </li>
        <li>
          <t>Soften the language and add guidance for short absences.</t>
        </li>
        <li>
          <t>Editorial fixes.</t>
        </li>
      </ul>
    </section>
  </back>
  <!-- ##markdown-source:
H4sIAAAAAAAAA5VY25LbNhJ9x1cg8kN2q0TNeFwup1Sby1xsRxs7tWX5ByCi
RSJDAlwAlKxMzZ/t2/5YTgPkjG6uJE8jkmig+/Tp040pikJEExuay8nnmuTi
7ed38rZWxsufVZBKLqOyuljYiShVpMr53Vyuyk5oV1rVwkx7tY6FobguOu9K
Z4uSzYvAhsYWl5ci9KvWhGCcjbsOJnyIwMpANvRhLqPvSWzm8pXYOn9fedd3
cOc/2I1CkHeu7FuyUd7CwjVGq4idJmJDtqe5kLJVpsH6fPpP7MnM+WqCL5WJ
db/Ct+Tetho8vEiP2c1W7QpNDVWIjk0a/A0RJnWMXZhfXByazvKWM+O+tsnF
nwAyq2PbTIRQfaydnwtR4FQpM5gflA/ybVWRj+mtd5wZ0iY6n14gsLn86H43
TaPSixA9EfxdRrIr8pWx0ZB8eSVv0ufSRCTsF9Vbo4wlm186zfm+vHpzeTkZ
3vQ2cmrfLdIzZUwbuPMTJXcY0vSp92YuR3Cev10gkKKQagWHVBmF+FybIPWY
O01rHM+ESjAUxsq18zIeUG4qS9U0pPm1uC6jsdXBVxiVKtCRlVxR6VrsbQBv
6FwgPcvOtEbrhoR4IReIzum+ZObIhxeGHx/ZR0oQS7c+3tQkX+EBvnYOBrxm
DVR6T6PrAnEra35PhJzKLaghrRti1bLLBIZnvB6RuS1H5GCJLEcn/tub8r7Z
SQBywTtS2zmvvMGrqO7h1YZgFzoqYxhdTO6aZ3fFIQad8tHgqB2YItc9/+it
WsEmOhnIb2gm/8FhD06KwUmON9YqJlcnAK6I5Fu5UaWypaEwkR18eXhYUsbw
1ey1gEfffHp3+92bl68eHxF+bcoaCbLZ+b5LR5ovckt0z/GCZW3XUCQOWDrb
7EQCJTxRAWe0yjJfPHWNKilx5zQ5K8Ys4Sg46Ruje9XM/smZPqHNwMQwOK4p
lN6sANW2dpCOXUYFMJ+a7uM8bHaWay9eyBtVJuGyWojr8HSKZs4+PGS+AaOj
OHIywbSYvrQuxavEn/BO7vNuJhd/wcsp2OyJywsgQ/AZirVj9OEj4KQvVPYc
vlAn6d9NDtKxdX2jpSWuUwfiDbb5kWUMAVja7vkzkykFI9W2EC/ZmHsaeR4I
RFfNQBSAgfTEqdCQGuQj8yqaNhW+T4DtVdlJ1pCQh7kKRtOj+GGPsm9mL2cv
Gc0fn0gry957xARHOg8nLOrsV9feuhYCRY2pDFdOKjOZS6s0neJVa+9auMkn
B1NZBX1GlYDUxyiHHDzsjS2bXrMG2p2zlHjH9mCIGk8NaCIlQ8nMGGArE94r
rhreJYSepqxMJXu2fD+Vi+ubVFEfPtzKG6e8li21K9YYpjcM18aHWNRYgw2g
UjarEtLlSQX4mEs/J7Ylb8BBe8DTFNNUrnpuS8gC6g+JeEbvWWOMRdhog5JD
1AaW+J5rZJmC41QMFX2mVhd/VeKnctQMFzKdhzUikZYLCuVY1fA9JyhJ9JAc
mCb12JpAY1Eu38uMPidIC2UtqrlM6Upr5TXAkncpItizepjMZY5hVNcjHRFD
5+LV2MRK07bo5sCHZR+p5KDiV7vQTBzNZJpK9OQkXtgsJSKHvYdM4sLzdywX
agMBSRlSFcaAM5LBsQxJRHC93YtLIzTHcIssh7kCcZqqMHqwJOxBCAdReAPp
YUpcq6DTeg3YUs8c62PsO3a/RBmCp+rkTc6RJAHN7kbTpJNz8UjVJcHkxj3q
z9AdTyaNJLrHoPBpamUajEz7+TydRLICISoJkYdQZjH1+74k/DOf2Ja5I0bu
hFmePE73rV2jMx+4dX+FFNNBSVis46HL4wwKSH9cFHezPJ4djqHjGm5HzJTI
6jR2R0DYmCwN2LplNkMMUhrzqwNVv8tbscpBajQJNJLjDseTpJV53INi9bbh
rJ+tfgkHbYUK5qOB0QlJvw08XxIrHzJAX7qslbkLBUzTAxPPUKZO2lbWzgUa
kII2AhU0ZjSfgJkpcTekYJ6pdZD04zpKMw8/HIx2UMnAs26CLNE8DwnQPwgm
Z4ovMqgSn6HLZOgDRhieUvKS8mAJ5xNl8er16ys0LRRkYh9ytctpgWvjpJ1O
Wlz/en3mlP2BvFapi6aVqsydKs9P99ZtMYRXvCw7F7K85DELo1QPWgVG3rQd
w5dWjp48HcFXG3ndbJR38hNh6ld4vvEGreVW+Q4rML4V8q03Jb6H0vmGV/wb
AzDq5f7e8YOjBhfRBoOhxeNHDA3yxiCbXXryvyn5y///VzcE+DVefXIruVQ7
SF76DfLLJfr2fcDzZzj8gVpn091ghYFNiH99w9cELNBuayF4sWBd4wR/vLu8
upJF8QODcpuJOXTdfME7V1t7d96Hue25CZP+frIGajR5PHcc2ePT4DilKWoy
3pQmDO3khNSTGdb+rDZ03MCgS6N8H/asczPuNE0myKbSZwZtPTZPJrelNKvo
DWZC4sPv0giWmtug+3mQONXave7EfoxlhLOz9mKz23zbkUP73rMfOzyvem+G
eE/V42/IZpphzgknH7GMrKBPgZzpCOduCmNHyPqPEw5bw2ErkHutAAe6dczd
GhduW/WqyjckpbWseqMZ7rwJS9wogcn0bfrPAIvX2nzhV38A6+WeMdARAAA=

-->

</rfc>
