Re: [ietf-nomcom] NomCom 2023 IETF Chair/GEN AD Term Reset Proposal

Phillip Hallam-Baker <phill@hallambaker.com> Wed, 20 September 2023 17:22 UTC

Return-Path: <hallam@gmail.com>
X-Original-To: ietf-nomcom@ietfa.amsl.com
Delivered-To: ietf-nomcom@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC7B9C15153E for <ietf-nomcom@ietfa.amsl.com>; Wed, 20 Sep 2023 10:22:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.404
X-Spam-Level:
X-Spam-Status: No, score=-6.404 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kIWKni13O5sh for <ietf-nomcom@ietfa.amsl.com>; Wed, 20 Sep 2023 10:22:35 -0700 (PDT)
Received: from mail-oo1-f41.google.com (mail-oo1-f41.google.com [209.85.161.41]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C68A3C14CE38 for <ietf-nomcom@ietf.org>; Wed, 20 Sep 2023 10:22:35 -0700 (PDT)
Received: by mail-oo1-f41.google.com with SMTP id 006d021491bc7-57b4300a38bso53356eaf.1 for <ietf-nomcom@ietf.org>; Wed, 20 Sep 2023 10:22:35 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695230554; x=1695835354; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=nbVFMmuOj+JLcagjUPonlKwfm1W6hoWlVZHVMIlJ31c=; b=hf9At7nqXLMyLeS6GGjGzxaLv066eyASDdxcXix5Q+3avDXm/0vD6TIxXOA46OWgrw XK2pPq0XGoAdYU+yG871iPUvWJBK649WuwD/lThRHCXPeIshbQgcQJlsFapeO8G1XmNs oFuRKXwbrKlH/F8Dk0GVcSCuUQ8Es00zJ/G018wfHyBFKiFpozbmrlSawkMkARo/vMZa y03QcPxi5zzS9Spvjkt8gQqRQ3crCdYabGQQu3b3aiWRI2oWdUF2IXRbNtBEsqgpuxiP c33RvaTcLibbHEa8XbmalHpqiqSLVMvHWR+x001YDxWI46N1X5tp5Sa5K0+kZvrdTjkX SlaQ==
X-Gm-Message-State: AOJu0Yw/h14W1DbiLi5CCZ0EuvnPkRsNxlX6i0355Q6MXBA//o0S2l6H o5zt91CObTDTXKgM0Xu6UnLfcEgYdZiRpcmJJ/hl2AMV
X-Google-Smtp-Source: AGHT+IEsDnT0rYNLvzjIvDNQFyWx7X35t0vviijxh6gIaSvmiBQb3jV0kSBtqw4FS0CU0n5te6TD1NpOSU/KGtnociw=
X-Received: by 2002:a05:6820:1b82:b0:57b:469d:8af6 with SMTP id cb2-20020a0568201b8200b0057b469d8af6mr638951oob.4.1695230554495; Wed, 20 Sep 2023 10:22:34 -0700 (PDT)
MIME-Version: 1.0
References: <169510712484.33106.6003546482401163584@ietfa.amsl.com>
In-Reply-To: <169510712484.33106.6003546482401163584@ietfa.amsl.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 20 Sep 2023 13:22:22 -0400
Message-ID: <CAMm+LwhJV3aWL=c90sm=5myMT0yB5WBnW4CzHAfG9d76d50L0A@mail.gmail.com>
To: ietf-nomcom@ietf.org
Content-Type: multipart/alternative; boundary="000000000000035e220605cd9f4d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/nD8uKL1o9kJsr6zPdLl-rTIH4-A>
Subject: Re: [ietf-nomcom] NomCom 2023 IETF Chair/GEN AD Term Reset Proposal
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-nomcom/>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Sep 2023 17:22:36 -0000

+1 do it.

But also consider making it a general thing that the NomCon can extend any
1 year term to 2 with the agreement of the IESG and IAB.

The same can occur in any unique role such as RFC Editor. But it might also
be handy for cases where there is a vacancy due to some major reshuffle.
The only boundary condition being that we should not end up in a
situation where there are two slots and both are filled in the same year.
But if there are three AD slots, we could end up in the same place.



On Tue, Sep 19, 2023 at 3:06 AM NomCom Chair 2023 <
nomcom-chair-2023@ietf.org> wrote:

> All,
>
> In discussions of the process for replacing Lars as IETF chair, it was
> observed that the IETF chair role is exceptional. With the vacancy coming
> at the March IETF, it is possible that the term could be reset.
>
> According to Section 3.5 of RFC 8713, when filling a vacancy of precisely
> one year, the new term is a single year. Though this does not apply in this
> case, a vacancy that occurs after the meeting results in a term that is
> almost three years.
>
> For other positions, it is necessary to ensure that the usual cadence of
> replacements remains synchronised with other appointments to the same
> position. The IETF chair has no such need.
>
> In requesting that the NomCom fill this vacancy, the IESG have expressed a
> preference for a two year term. However, this would deviate from the
> documented process.
>
> The question therefore:
>     Should the cycle of appointments for IETF chair (GEN AD) be reset?
>
> If the term is reset in 2024, someone selected for IETF chair would have a
> two year term. Subsequent IETF chairs would then be selected for 2026 and
> subsequent even-numbered years thereafter, or until a similar reset occurs.
>
> The NomCom would like to solicit community feedback on this suggestion.
> Input on this process is welcome over the next month at
> ietf-nomcom@ietf.org, ending on 2023-10-20.  As the responsible body for
> RFC 8713, the IESG will be responsible for judging consensus and whether
> this process variation is acceptable to the community.
>
> If the community does not reach consensus, the rules in RFC 8713 will be
> followed strictly. The next IETF chair will be seated for one year.  The
> possibility of term variation will be made known to prospective nominees as
> part of the upcoming call for nominations.
>
> Martin Thomson
> nomcom-chair-2023@ietf.org
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce
>