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

Michael StJohns <msj@nthpermutation.com> Tue, 19 September 2023 17:14 UTC

Return-Path: <msj@nthpermutation.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 0A2D2C1519A9 for <ietf-nomcom@ietfa.amsl.com>; Tue, 19 Sep 2023 10:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.995
X-Spam-Level:
X-Spam-Status: No, score=-1.995 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.091, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=nthpermutation-com.20230601.gappssmtp.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 qO0IaQbiSgDK for <ietf-nomcom@ietfa.amsl.com>; Tue, 19 Sep 2023 10:14:38 -0700 (PDT)
Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) (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 90116C14F748 for <ietf-nomcom@ietf.org>; Tue, 19 Sep 2023 10:14:38 -0700 (PDT)
Received: by mail-ot1-x32b.google.com with SMTP id 46e09a7af769-6c0b8f42409so3575961a34.0 for <ietf-nomcom@ietf.org>; Tue, 19 Sep 2023 10:14:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20230601.gappssmtp.com; s=20230601; t=1695143676; x=1695748476; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=wr+TsqUtFAUacea2+PiGDZtKotJr1YQgByqF7ZfuEWY=; b=Fn5BBrNJ12ifmvWLjHrecjaikq3BwYVZTHiGmk8DYRO57r+n7OOXed5bsQhEuptcYE VRL8wzafO06IR6TUJC1AgWOwEU9qgojejyWSbAeLv6tPgEh3r87JnEr+V854v0nwfTua JatkdQw4zxIRHMHMWogTCv1u6zMk6+lPO/5iB884h0SimxRsSgnzRxH1fn9Dz8un+/1E GfDGe8AT2IajxTEALtPjhyEAxT8ZXB6iqX80WG6M+5rFt83vqXlVqkl686vU7WRyCHaY wZecMX+FodGxeHjlRlK6G00xgnFax7qkgn60Px6pLhYdm1zUgWbDT1vNRaUtGELnHFnD u1Fg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695143676; x=1695748476; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=wr+TsqUtFAUacea2+PiGDZtKotJr1YQgByqF7ZfuEWY=; b=eZeWlOxAdAWL5Y1RaCA7rVHMspm9WZb3fhy2Lx3TiUMNUekp9NOoeGIP7oCyNuZ/PK iGWld5v/e2U7hjZrDMTnA25DTJICWWakhOUmmJjAXvABV3LFFv7qTi3uPGpir8cDlVTa fJPo5apgJaxD30lH1/WIx7/8VJzBDMQm2vk1uzAcqB3swV5d20lhNPJQPn4hyOCRXjL0 VQvWt7jWsEhR+yPziDcs1AjtiwYFcAspym2k2BJ5S+so11fH+x+U4QaiyUj2eK6wTMSu 42fuKkbm8EBjWAXDlBNQNJ9Azvqg8q9SpkhudVX12N9MG6zfUcDlYnYNl1pAY8ncHtZl hPew==
X-Gm-Message-State: AOJu0Yz3Zhm94E4J1bw/8nUJ482NmoasZOsNU684BQrAz+34Gj/+mArC 8KkTKfBDykm2fvlQ4yT38r4vFfwlOfSj3YUK4Cw=
X-Google-Smtp-Source: AGHT+IFPNqnEmkjfEIX/tw5kPQQXa617gdari5MCIpU4i4W7VaBrYngPkL320JmnLmxIasZGxKHL/Q==
X-Received: by 2002:a9d:62d6:0:b0:6bd:b5f7:187a with SMTP id z22-20020a9d62d6000000b006bdb5f7187amr211169otk.20.1695143676666; Tue, 19 Sep 2023 10:14:36 -0700 (PDT)
Received: from [192.168.1.23] (pool-108-31-156-76.washdc.fios.verizon.net. [108.31.156.76]) by smtp.gmail.com with ESMTPSA id t25-20020a05620a005900b0076cdb0afbc4sm4131511qkt.118.2023.09.19.10.14.36 for <ietf-nomcom@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 19 Sep 2023 10:14:36 -0700 (PDT)
Message-ID: <d0ed47c1-f6ee-e7f3-4a51-718213703a16@nthpermutation.com>
Date: Tue, 19 Sep 2023 13:14:34 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1
Content-Language: en-US
To: ietf-nomcom@ietf.org
References: <169510712484.33106.6003546482401163584@ietfa.amsl.com>
From: Michael StJohns <msj@nthpermutation.com>
In-Reply-To: <169510712484.33106.6003546482401163584@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-nomcom/fTo-uWNbDEN1wJ0yte1IhZHq99k>
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 17:14:43 -0000

I'd support either a 2 year or 3 year term, and I'd leave it up to the 
Nomcom to decide whether to offer a shorter or longer term (a good 
candidate might not be able to commit to a 3 year term for example), and 
to the confirming body to also get a say as to two or three years (e.g. 
a good candidate, but with not quite as much track record who the nomcom 
wanted to pick for a three year term, but the IAB wanted to hedge its bets).

Pedantically, according to the black and white of 8713, if Lars resigns 
after the end of the First Meeting this should be an almost three year 
appointment; and if he resigns before it should be a 1 year plus a few 
month appointment.  Pragmatically, the language of that section (3.5) 
needs work but can be made to cover a 1+ or 3- year term, but section 
3.4 has

> Confirmed IESG and IAB candidates are expected to serve at least a 
> two-year term. The intent of this rule is to ensure that members of 
> the IESG and IAB serve the number of years that best facilitates the 
> review of one-half of the members each year.

and

> The term of a confirmed candidate selected according to the mid-term 
> vacancy rules may be less than a full term (two years for IESG and 
> IAB, three years for the IETF Trust and IETF LLC), as stated elsewhere 
> in this document.

and

> It is consistent with this rule for the NomCom to choose one or more 
> of the currently open positions that share responsibilities with other 
> positions (both those being reviewed and those sitting) to which it 
> may assign a term of not more than three years to ensure that all such 
> members, Directors, or Trustees will not be reviewed at the same time.

This last section came into being as a result of our re-balancing things 
many years ago.  Interestingly, it was the Chair, not one of the ADs 
that got a 3 year tour.  I think that was Fred Baker in his first term.

These sections somewhat interact, and somewhat conflict with section 3.5 
so I think any of 1+, 2, or 3 years would work.

If the Nomcom does not appoint a chair to a 3 year term, they should 
consider whether to appoint/reappoint some other AD to a three year term 
if not doing so would unbalance the number of positions even/odd Nomcoms 
have to consider.  The balancing phrase above did not contemplate areas 
with three directors.

Mike -

ps - sorry to see Lars go.



On 9/19/2023 3:05 AM, 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-nomcom mailing list
> ietf-nomcom@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-nomcom