[Eligibility-discuss] Re: [Gendispatch] Re: Re: Re: Comments on Composition and Comportment of the IETF Nominating Committee draft

Joel Halpern <jmh@joelhalpern.com> Tue, 18 August 2026 20:58 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: eligibility-discuss@mail2.ietf.org
Delivered-To: eligibility-discuss@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id DD0AF12BEAAC2 for <eligibility-discuss@mail2.ietf.org>; Tue, 18 Aug 2026 13:58:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1787086714; bh=IQW3mIkJPPj/hQ2hzJf71hJd+wG2VRqF++OWIrwFDmg=; h=Date:Subject:To:References:From:In-Reply-To; b=sjhzncxTBvcGfIIGD45I2OYmeTtcvvieYfHxXAXZdD/o06pyYEiS1zvdI6cDPSdZf +8DkF7JJ3TJUCgqzSPhRyIuBF1kiJZ0CxGlCsOUul95DuG3CwGieCaEV27lRNVShsU 7OTgCdYfTW+jwzAqVcPi2X7EEcka0Bv5ymVVSbAI=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.796
X-Spam-Level:
X-Spam-Status: No, score=-2.796 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7nnvDb8XpS4i for <eligibility-discuss@mail2.ietf.org>; Tue, 18 Aug 2026 13:58:34 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 4AB1212BEAAB5 for <eligibility-discuss@ietf.org>; Tue, 18 Aug 2026 13:58:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1787086706; bh=uaS8dzo2NLXRIDkRD2+c42zG15XLRQJjhINUxVi2NUU=; h=Date:Subject:To:References:From:In-Reply-To:From; b=WValMelg1XRu4p3bxWqwtXT5rGNlsqdBSlq1oCJHdwxCd8MPcDk+lMNNltQxBBaPS HlFjOJ/kEOLiaXztYyQAWN1enGj338bi9pv6nr405RfMH3igkckAHnvMXivSbtBe8A vVSdglAR+MWo19x4US2gB5tuLCaRPSmkethbjYmA=
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4hPhr23hNkz21y7c; Tue, 18 Aug 2026 13:58:26 -0700 (PDT)
X-Quarantine-ID: <EQfFYgsrgLOJ>
X-Virus-Scanned: Debian amavis at b2.tigertech.net
Received: from [IPV6:2600:8806:101:d200:9571:38d6:b8ac:1fd6] (unknown [IPv6:2600:8806:101:d200:9571:38d6:b8ac:1fd6]) (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 mailb2.tigertech.net (Postfix) with ESMTPSA id 4hPhr16mvZz21y7Z; Tue, 18 Aug 2026 13:58:25 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------UV9r7nkA4IKAf8jrWPPgjo6G"
Message-ID: <d43d5599-3ce4-4102-a72d-6662372cbfd0@joelhalpern.com>
Date: Tue, 18 Aug 2026 16:58:25 -0400
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Tara Tarakiyee <me=40tarakiyee.com@dmarc.ietf.org>, eligibility-discuss@ietf.org
References: <6.2.5.6.2.20260706031812.0b0262a8@elandnews.com> <6.2.5.6.2.20260707201930.17fe3b28@elandnews.com> <629856737.2603.1783519201973@appsuite.open-xchange.com> <6.2.5.6.2.20260708114232.10d83b28@elandnews.com> <CABMXHrHGB9-jPhqkvThxy_Kxa5VASTjSw3c2Od_TowwKxNazjQ@mail.gmail.com> <CABMXHrHLfQeBm+G4h-hXTPyYB4BfyHz--MoO388Omdu-eSwY+A@mail.gmail.com> <6.2.5.6.2.20260807115249.0f393600@elandnews.com> <CABMXHrFzRPKQAiMf9OWmnvj_QEy_n9L_QDYLdfDsXBTTONcyWA@mail.gmail.com> <d66e9d26-48e4-4f11-a146-2bd7b89adb28@joelhalpern.com> <MN2PR17MB4031443262CFA19D4174130DCDA72@MN2PR17MB4031.namprd17.prod.outlook.com> <ead772a9-0bf2-4adf-93ae-5103e272b465@joelhalpern.com> <0228ce06-661a-4781-b39a-5f74afb6d8dc@huitema.net> <CANeU+ZAjFwmWzX62jtmg6mR3W89SApiFCo2xngN+2DPBu-Zsrw@mail.gmail.com> <515245cb-049c-415c-9a0c-6e9dba4a4408@tarakiyee.com> <MN2PR17MB40311127234F683717B42AE1CDA62@MN2PR17MB4031.namprd17.prod.outlook.com> <f306d97c-26e9-4e95-879e-36b0b12937a6@tarakiyee.com>
Content-Language: en-US
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <f306d97c-26e9-4e95-879e-36b0b12937a6@tarakiyee.com>
Message-ID-Hash: GTV3PQYUEPNOA4SCIXVGQZN7W362PJ2V
X-Message-ID-Hash: GTV3PQYUEPNOA4SCIXVGQZN7W362PJ2V
X-MailFrom: jmh@joelhalpern.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Eligibility-discuss] Re: [Gendispatch] Re: Re: Re: Comments on Composition and Comportment of the IETF Nominating Committee draft
List-Id: IETF eligibility procedures <eligibility-discuss.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/zKs2Sc4CAOAWYoCnKO834CTLxbA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Owner: <mailto:eligibility-discuss-owner@ietf.org>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Subscribe: <mailto:eligibility-discuss-join@ietf.org>
List-Unsubscribe: <mailto:eligibility-discuss-leave@ietf.org>

May I suggest structuring the algorithm around drawing from the common 
pool , noting how many people from the alternate pool are selected.  
Stop drawing from the common pool when the number of remaining seats to 
be filled is equal to the number of additional alternate pool 
participants that are needed.

For example, using the old "we need 1" goal, one would fill the first 9 
slots from the common pool.  If noone from the alternate pool was 
selected among those 9, then the last one is from the alternate pool 
rather than the general pool

Yours,

Joel

On 8/18/2026 4:20 PM, Tara Tarakiyee wrote:
> No, that is not what I was expecting. Thank you for pointing it out, 
> the overlap between the two pools is doing something I did not intend. 
> I will look into correcting the formula.
>
> Best,
> Tara
>
> On 8/18/26 9:42 PM, Salz, Rich wrote:
>>
>>  *
>>     Joel: on the upper end, the 5-slot case only arises when the pool
>>     is at or near parity, and at that point 5 is approximately the
>>     expected value of the flat draw, so the formula is not
>>     intervening at all.
>>
>>
>> I don’t think that’s accurate. Replace ’n’ with ’10’ and simplify:
>>
>>       r = min(p, max(3, min(5, floor(10 * p / t))))      
>>
>> So the range is [3..5] or one-third to one-half depending on the size 
>> of the opt-in pool as you say. But then we fill up the rest of the 
>> seats, five in this case, and the total count increases  (call t=100 
>> and p=50) then the true representation will be 5 + [2,3]. Is that 
>> what you were expecting or want?
>>
>>
>