Re: [Eligibility-discuss] some numbers

Alissa Cooper <alissa@cooperw.in> Wed, 22 April 2020 17:17 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64E483A109A for <eligibility-discuss@ietfa.amsl.com>; Wed, 22 Apr 2020 10:17:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=Bl6AqIl3; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Dt1cTh6t
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uhkDaCMAP3Xo for <eligibility-discuss@ietfa.amsl.com>; Wed, 22 Apr 2020 10:17:22 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9920E3A0FE1 for <eligibility-discuss@ietf.org>; Wed, 22 Apr 2020 10:17:22 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id EC5A85C0289; Wed, 22 Apr 2020 13:17:21 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 22 Apr 2020 13:17:21 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=L cnqOXDSTMbRSitaL9a4XqQwxACVZIq/Fd2caWmAlEo=; b=Bl6AqIl3znnMD9YpV lOhMOhQm3S2jYg2ozSiNQc3+Y5AsPehlvmJRpyVKwnUjufAqWPjtZQzlQMat2nMc le3fIZsKNcTBa22q8Ywr6WuJjCRMXDG7jgz3uqUlVqsBiBfYxpdK2TL3FYpd+hUZ qWyuY87qG7alT9T7rYHq3Bch++oBnPVh96EjfrL7///4wAIVbz/PhaXQyroPdwZf lWK+/48AgO6BTzJoEJxzTEs+95CxRzVZ+AaZIRj+U7k7yfU0XQlwxdDd0S5uOEYp c+N9oNWXXYgqtPg3MUU9b2H/HUO5z2EY+mb/cOhYmOheN0I7kaFm9aMHl0MPMCDb b0Low==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=LcnqOXDSTMbRSitaL9a4XqQwxACVZIq/Fd2caWmAl Eo=; b=Dt1cTh6tO0qaUzWArYg408VML0gwzLwqBrJlCinkDcBVk1nUibp5IKACt Roxlc+07we+isdink7JoV8j2xtl+SNzYwD0wFxtHpceyjhyjgP85RTKALieg7bxA vgC8mFo8pw82wk87ZYIrnArlnHhVQZpg5F5eE5kthSb+BRw2+yEAGY1ZcUEi3rSt N2CQi9lf9owRWJkrMUOQTHY5f12qjXq26Yg7wGCHXTs5KGkhrvbJFBAz2eSsZ7HU zkvRSz+FiPKTu7EySyO6YRpnaNtfDOsKtaklEWym9ZlpXQBh0ka9/WIpwbGpRqtT SQNIlIFoxSDHmg2Jkc8iHLVLMS2+Q==
X-ME-Sender: <xms:IXygXvybRiqmi5klwCwpkta6Kipb8FysiRTPxvV4Ppu7XLUCAybKTw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrgeejgddutddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtjeenucfhrhhomheptehlihhs shgrucevohhophgvrhcuoegrlhhishhsrgestghoohhpvghrfidrihhnqeenucffohhmrg hinhepihgvthhfrdhorhhgpdhgihhthhhusgdrtghomhenucfkphepuddtkedrhedurddu tddurdelkeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh hmpegrlhhishhsrgestghoohhpvghrfidrihhn
X-ME-Proxy: <xmx:IXygXjgtm9im2q4cWRgqMnsZaPcB3DMrouFYeJVyugSJdcGqyMwHTQ> <xmx:IXygXvlO6rFmiNty58UC30k-OTmz9SDnDY3RyU3-h0KqLx9k6p0TWA> <xmx:IXygXnL39lwF4y7cAkpswA8Hbgoy4yo6HR3AQ_tFaVXvn3FYnd2zhQ> <xmx:IXygXlAhFlMYAdD5HWCw0MQOpwCkKgQA_67F88bDvYjZHzl9jUBajg>
Received: from alcoop-m-c46z.fios-router.home (pool-108-51-101-98.washdc.fios.verizon.net [108.51.101.98]) by mail.messagingengine.com (Postfix) with ESMTPA id 116723065CD0; Wed, 22 Apr 2020 13:17:21 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.5\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <63a8511a-f727-d0e8-b3ce-6c81ac547eec@cs.tcd.ie>
Date: Wed, 22 Apr 2020 13:17:20 -0400
Cc: Ted Lemon <mellon@fugue.com>, "eligibility-discuss@ietf.org" <eligibility-discuss@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <84348F48-1535-4EA9-BA6E-BA66F067EA7C@cooperw.in>
References: <1f887326-339d-078f-e718-71ca090f762c@cs.tcd.ie> <C5D4414C-80C8-465A-AF5A-9485BE748BFA@fugue.com> <63a8511a-f727-d0e8-b3ce-6c81ac547eec@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.3445.9.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/VGBkJ96XOeCsO5Bk0ZpEh1SnlmA>
Subject: Re: [Eligibility-discuss] some numbers
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2020 17:17:25 -0000

Hi Stephen,

Thanks so much for doing this. 

> On Apr 21, 2020, at 9:08 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
> 
> 
> Hiya,
> 
> On 22/04/2020 01:59, Ted Lemon wrote:
>> Stephen, what results do you get if you run this on historical data,
>> say for the past two years?  The problem with this run is that it
>> doesn’t really tell us who this would disenfranchise under normal
>> circumstances, given that circumstances are anything but normal.
>> 
>> IOW, pretend that it’s just after IETF 106, and now run the old
>> algorithm, run the new algorithm (in the second case pretending IETF
>> 106 didn’t happen) and see who loses eligibility.  Do this again for
>> IETF 105, 104 and 103, so that we have more than one test case.
>> 
>> Does that make sense?  Is it hard to do?
> 
> I'm not 100% sure I'm answering the right question but I
> think that'd be the 357 people who are only eligible based
> on f2f meetings and not otherwise. (See the Venn diagram
> near the bottom of [2].)
> 
> Put another way: if we have no f2f meetings before the 2021
> nomcom are selected, and we adopted draft-02, then those
> are the people who'd "lose" (assuming nomcom-eligibility is
> a "win";-).
> 
> It is absolutely a non-trivial, interesting and subtle
> question as to whether we'd be ok with dropping that set
> of 357 people and replacing them with the set of 452 who
> would be eligible without having been at a f2f meeting
> recently.
> 
> Optimistically, if we do have another f2f meeting before
> nomcom2021 are picked, I'd guess many of those 357 people
> might re-gain eligibility, but I'd have to change code
> to put a number on that.
> 
> I guess I could also check how many of the 290 who are
> in the intersection have previously volunteered to be
> on a nomcom. (Another one for tomorrow or the next day:-)

If possible I think a good comparison with what you have would be to look at the 5- and 3-year periods that ended in April 2019 or 2018. I.e., generate the lists using the five meetings prior to that date and the 5- and 3-year periods prior to that date. Then we could see how similar the lists and the venn diagram look at two points in time, rather than one.

If you do that, then also looking at how the list of who actually did volunteer for the nomcom in that particular year and how that group breaks down between those who would be eligible via paths 2/4/5 and those who would not would be revealing. In other words, it would be interesting to see if most of the people who volunteer land at the center of the venn diagram or not.

None of this implies any normative judgment as you say, but at least it could help people understand numerically what the impact could be of the paths you propose.

Thanks,
Alissa

> 
> Cheers,
> S.
> 
>> 
>>> On Apr 21, 2020, at 8:50 PM, Stephen Farrell
>>> <stephen.farrell@cs.tcd.ie> wrote:
>>> 
>>> 
>>> Hiya,
>>> 
>>> With many thanks to Robert Sparks for writing up some initial code
>>> to query the datatracker DB exploring the results of drafts such as
>>> the one Brian and I wrote, we have some initial numbers to report.
>>> 
>>> If one applied the rules from our -02 draft [1] then if seems we'd
>>> end up with a similarly sized set of nomcom eligible folks without
>>> requiring f2f meeting attendance.
>>> 
>>> Details are at [2].
>>> 
>>> The status quo with only f2f meetings gives 647 people, the
>>> draft-02 scheme gives us 742 eligible people without requiring f2f
>>> attendance. 290 of those are eligible both ways. From eyeballing
>>> the lists, the eligible people who'd not usually be eligible seem
>>> no more crazy than any random subset of IETFers;-)
>>> 
>>> I didn't put the actual lists of names up as I'm allergic to
>>> publishing lists of people's names, but I'd be fine with publishing
>>> hashes of them if that helped, or with answering any on or off list
>>> queries. [2] does have instructions that allow you to replicate
>>> creating the lists yourself if you are willing to do a bit of work.
>>> (Before we could consider ourselves "done" here, I do think we'd
>>> want someone to have independently replicated results like this.)
>>> 
>>> For me, this means that draft-02 seems credible enough to pursue
>>> some more, based on the data and not only based on a hunch, which
>>> is good.
>>> 
>>> Happy to try answer queries or check out alternatives if people
>>> have any to suggest...
>>> 
>>> Cheers, S.
>>> 
>>> PS: I'm sure there'll be some errors in this somewhere. Apologies
>>> in advance for those and they are of course my fault and not
>>> Robert's nor Brian's ;-)
>>> 
>>> [1]
>>> https://tools.ietf.org/html/draft-carpenter-eligibility-expand-02 
>>> [2] https://github.com/sftcd/elig/blob/master/queries.md 
>>> <0x5AB2FAF17B172BEA.asc>-- Eligibility-discuss mailing list 
>>> Eligibility-discuss@ietf.org 
>>> https://www.ietf.org/mailman/listinfo/eligibility-discuss
>> 
> <0x5AB2FAF17B172BEA.asc>-- 
> Eligibility-discuss mailing list
> Eligibility-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/eligibility-discuss