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

Hesham ElBakoury <helbakoury@gmail.com> Tue, 19 September 2023 07:10 UTC

Return-Path: <helbakoury@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 A831FC153CA8; Tue, 19 Sep 2023 00:10:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 S83YfgTWRgDt; Tue, 19 Sep 2023 00:10:17 -0700 (PDT)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 F0A3EC14CE5D; Tue, 19 Sep 2023 00:10:16 -0700 (PDT)
Received: by mail-ed1-x532.google.com with SMTP id 4fb4d7f45d1cf-52bcb8b199aso6571466a12.3; Tue, 19 Sep 2023 00:10:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695107414; x=1695712214; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=7M37YX0VRKk5UC1hlE4GDIAetOlzKzeWx97KLlLW9S0=; b=YNOKUZHgK41jl46pJqD03iDvkMIYe8H75GjEvwlpUWRuXz7GA+YP19h/aAWGcdU8R1 RGMCVJkT+1eK+UfGevMbee03n9RuP4lfXhBtQCb/CqkQ8fWJn66RC+zwZldmh3KHAtk1 62BkrsAINxSaAYEYxo3U/Mcf+Dnw1HBLp1M/KukurRYO/LSrAAqVSRT5euLjtMA2a2Xv hmGIRqa6W3NR0HyQQq+dEOwxfy2GdNlm7/6MRTUPHNl1DG92rUoV2IcISsVuNFfk42B7 Oz07npSzqnsHNvBh+dh/g5rbdkudR20w1aV/da1HqLcCQUyt0B47Z6nmuTiG29XOLErA bdbg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695107414; x=1695712214; h=cc: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=7M37YX0VRKk5UC1hlE4GDIAetOlzKzeWx97KLlLW9S0=; b=kahrUNoTm3QLxmgupVbxRA5+wzr0pJ2OfWrYuvAMz4jU2kFZFYZRtQUv/PMiXhEpEC 0/aXwdUv5Xi8h/fhdpxvwA2CZBqotxSXkpkLxdhD2w5HJ0/lL07ZjOS0cUQWrLjTDcPk obQpIh4S4Teq1JZQqEZwgUJhjoK4xakndurZYMQdpR+DIyTifYPimOEy+ll/gV9XSpV+ KMHgb5TJXUyrHwSZWe8U8PBguJl/Oh4U1PHYHPewdyQQOVkkHj8YPqK6yElkn3zBFB+7 7ecIHBVXc3LIrS6JrE3dLHfr6zQBkwgOfCcen5DIurk991l8WNnk2ha0UuvwPn7jV1jo OZUQ==
X-Gm-Message-State: AOJu0YwccgnAXwYLR8F3Qt+EBQ9J7n9BKJFksix5lLOOrwRdKbQf1xHk Jb/MMnyIEt2jcZyxLMDSEPVnvAm2tFl3maZN0VIdBrA6OB4=
X-Google-Smtp-Source: AGHT+IERFttYhjyduuA1toJ5zMimhaS3cF+HSZH6IHSfhPFR1cnopFDKXKH7ki24hdQbEqllPTxC15n5BqYntxQputc=
X-Received: by 2002:a05:6402:297:b0:526:5c70:7311 with SMTP id l23-20020a056402029700b005265c707311mr8448200edv.8.1695107414067; Tue, 19 Sep 2023 00:10:14 -0700 (PDT)
MIME-Version: 1.0
References: <169510712484.33106.6003546482401163584@ietfa.amsl.com>
In-Reply-To: <169510712484.33106.6003546482401163584@ietfa.amsl.com>
From: Hesham ElBakoury <helbakoury@gmail.com>
Date: Tue, 19 Sep 2023 00:10:00 -0700
Message-ID: <CAFvDQ9odRqj+c_UjAm=Da6wd4A7sP+wtA7etoRyiZxPaSEzS3Q@mail.gmail.com>
To: ietf-nomcom@ietf.org
Cc: IETF Announcement List <ietf-announce@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000458e880605b0f385"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/9Iozzfmect-opFsE9SkqyjNgewM>
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: Tue, 19 Sep 2023 07:10:17 -0000

Can we nominate someone who has been chair before?

Hesham

On Tue, Sep 19, 2023, 12:07 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
>