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

Stewart Bryant <stewart.bryant@gmail.com> Tue, 19 September 2023 13:27 UTC

Return-Path: <stewart.bryant@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 3E21EC151982 for <ietf-nomcom@ietfa.amsl.com>; Tue, 19 Sep 2023 06:27:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, 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 8tSrEXnSQkL6 for <ietf-nomcom@ietfa.amsl.com>; Tue, 19 Sep 2023 06:27:05 -0700 (PDT)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 7B020C15171B for <IETF-Nomcom@ietf.org>; Tue, 19 Sep 2023 06:27:02 -0700 (PDT)
Received: by mail-wm1-x332.google.com with SMTP id 5b1f17b1804b1-401b5516104so61012075e9.2 for <IETF-Nomcom@ietf.org>; Tue, 19 Sep 2023 06:27:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695130021; x=1695734821; darn=ietf.org; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:from:to:cc:subject:date :message-id:reply-to; bh=DKmoZEZt63Kxoe6d4gZ7K9aIPJpBdXD9jCzCOq2Zp+c=; b=PtSe4bQTnwxV6ge0iB9iSV1in9rj56fg1EsL9tw1T3QholbfGw01XzoNQL6v29uGkE VQEqZTEL/dynDNMpo2v/yXCNQki43uh/ewZbwy05hfS9thJiGTEN9dyVTs9JAkdbgw17 sT4Jzqky9i09GnoIAeneiMAEHU7pf8n5hzdEZTMnWoM/OaylfjtZ0eY80tVfs4iu5tAN lQG9IiCTckAadCGFRPTKdYiFJSZYdpLjP4BxFXM0wmG1SOU5YpK1S5JoipQQl1XdK6wT rK+zcrdWykcX4ZI75G/5zDJC8ReiDHvbkAsfLoKJPBWTaPrDoHFYmiMHG7tOb0tjqAoj nzaQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695130021; x=1695734821; h=to:references:message-id:cc:date:in-reply-to:from:subject :mime-version:content-transfer-encoding:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=DKmoZEZt63Kxoe6d4gZ7K9aIPJpBdXD9jCzCOq2Zp+c=; b=DjRtr+cUlQXa4JvI4VL7gXcCsRBb36Yz9+H9n1xrWs9a/4dGjZ8zzv4RWExpy1XIud PBYq5CndT+uc49bGDWlC4PXLmO6rgFZMntJa4qR3VFHUksO8vo+HVK3zAD8KeIGEEvAh 9BkTV6m0tfzUx4FlPq44iqhUxQrXTTgzw/Kfe0sy/dCRzqWOfA/ZiF90SJjOcGIwj40L lRTebX6lobXwvb5gd7VQVFPhv+ax0hsqtZvxARV9DmclyFgs8HaeCmZdE6FyE8dyNJHi w4SlbJRWOlTnEOPDct3/OplDKgeXr0OIBcyMe+Q4AMCXCVzxvCTV5nrGdctwYf8cbArI F3fQ==
X-Gm-Message-State: AOJu0Yw3z00l3uenbPwnyO0/2xwCpR7unZulr8ew6X3Nas2HGsHyxmGC ohXe8K2vcpaAmogcnWb6nUM=
X-Google-Smtp-Source: AGHT+IEwAJtfOE0eIo7knB33QBwYaK+VHZTs5MUH8iXQCFpVVU4B0DmG6TG1D1l19ATQ2c2cIUKgow==
X-Received: by 2002:a05:600c:21cb:b0:401:bf87:9895 with SMTP id x11-20020a05600c21cb00b00401bf879895mr10492243wmj.22.1695130020466; Tue, 19 Sep 2023 06:27:00 -0700 (PDT)
Received: from smtpclient.apple ([2a02:8012:7161:0:7916:b04:824f:4a15]) by smtp.gmail.com with ESMTPSA id m10-20020a7bcb8a000000b003fed7fa6c00sm18320872wmi.7.2023.09.19.06.26.59 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 19 Sep 2023 06:26:59 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: Stewart Bryant <stewart.bryant@gmail.com>
In-Reply-To: <531E8702-FB7D-4C12-A77D-9F787E50BF42@gmail.com>
Date: Tue, 19 Sep 2023 14:26:49 +0100
Cc: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>, IETF-Nomcom@ietf.org
Message-Id: <44E18FE7-139B-459E-8E52-E0509CDCE7AE@gmail.com>
References: <531E8702-FB7D-4C12-A77D-9F787E50BF42@gmail.com>
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
X-Mailer: iPhone Mail (20G81)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/iqY5HM7K3KPDNRDBGad1MU06d_Y>
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 13:27:09 -0000

I support this obvious approach.

Stewart 

> On 19 Sep 2023, at 11:19 am, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com> wrote:
> 
> I also support a reset to 2 years.
> 
> Best regards,
> Kathleen 
> 
> Sent from my mobile device
> 
>> On Sep 19, 2023, at 4:22 AM, Martin J. Dürst <duerst@it.aoyama.ac.jp> wrote:
>> 
>> I support this proposal (to reset the term). It's simply what makes most sense.
>> 
>> Regards,   Martin.
>> 
>>>> On 2023-09-19 16:05, NomCom Chair 2023 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
>> 
>> _______________________________________________
>> ietf-nomcom mailing list
>> ietf-nomcom@ietf.org
>> https://www.ietf.org/mailman/listinfo/ietf-nomcom
> 
> _______________________________________________
> ietf-nomcom mailing list
> ietf-nomcom@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-nomcom