Re: [Eligibility-discuss] On 3797 alternatives

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 02 June 2023 18:02 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 2B549C14F747 for <eligibility-discuss@ietfa.amsl.com>; Fri, 2 Jun 2023 11:02:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.397
X-Spam-Level:
X-Spam-Status: No, score=-4.397 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_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 W0Jl0jKQsBKQ for <eligibility-discuss@ietfa.amsl.com>; Fri, 2 Jun 2023 11:02:07 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 EA68BC14CE24 for <eligibility-discuss@ietf.org>; Fri, 2 Jun 2023 11:02:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 985953898E; Fri, 2 Jun 2023 14:02:04 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id OSxNHoXjnt5t; Fri, 2 Jun 2023 14:02:03 -0400 (EDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:40a:34ff:fe10:f571]) by tuna.sandelman.ca (Postfix) with ESMTP id 3189F3898D; Fri, 2 Jun 2023 14:02:03 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1685728923; bh=RoCu4weqzgIqyJQ36MNGo/pFK/p7LcNercKoAeL8Lik=; h=From:To:Subject:In-Reply-To:References:Date:From; b=TDWOAWTLb1ygs46FDyPxwrpxlTPR3yjThNi89lNC/7zBB+qPSmJblKu7h0JrGvIpG FIuq1frOYiDuqS7h4IkzO3TrHUIOmjNC6nwrzuRElRdmohyyMNclS4gMH4GtPI+QzT ZkSnSY25beeGAYf886yyqntH7QovWHI/QghGaoHSxg2yQZNEkGtlCekUJzk7DE5yQY yXxJdY0epvkf7jfHQtpgoT8ipgTOyfcY3x/1Tjely+A506TOI7ToDzlSzH7nZr9OG7 WFtEmUywbEXKWgnFK6sT70UM7fb1M4mEVgnGcxb52xVKRCg+IChYirSRDxvsoJOs3u Uxes4iOidXTLA==
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 1786449; Fri, 2 Jun 2023 14:02:03 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, eligibility-discuss@ietf.org
In-Reply-To: <F396F327-FC9C-4688-8ECA-31F5176CE9FC@akamai.com>
References: <CAChr6Szvewhk0_z5DVqTJ37qR6eHxBw0Am2MnycxsS=a9x_bzw@mail.gmail.com> <4b2070b2-21e7-4887-b9a2-1049b930d0be@betaapp.fastmail.com> <CAChr6SyLNfEHxSCaj+w_j4Zzxf0vLudqzfpsGO7kDd1jO1AFLg@mail.gmail.com> <CAF4+nEGAsAvD4Vzy7BVOKVE+5wnGspP+QC+_bYKEWfYihVYdsA@mail.gmail.com> <CAChr6Swg5An=n9gAo1dYA=U_DY-Qd5h48Aq6Wqhf=QUae9pB7Q@mail.gmail.com> <BY5PR11MB4196BD7045991FDB8FDE8DA1B5499@BY5PR11MB4196.namprd11.prod.outlook.com> <8320D717-9BE0-4B94-8CE4-B560AA7B9BC0@akamai.com> <20951.1685642449@dyas> <F396F327-FC9C-4688-8ECA-31F5176CE9FC@akamai.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 02 Jun 2023 14:02:03 -0400
Message-ID: <933.1685728923@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/e0AM4dG3tEIFEfZJwomvQjl76LM>
Subject: Re: [Eligibility-discuss] On 3797 alternatives
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF eligibility procedures <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: Fri, 02 Jun 2023 18:02:11 -0000

Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote:
    >> It's not the random sources that are the problem, I think.  We could
    >> say that we will take the XYZ Lotto on June 12th, and then if we need
    >> further randomness, take the XYZ Lotto from June 19th, or June 26th,
    >> right?

    > In general the lotteries that have been used for NomCom choices are
    > once or twice a week.  That means on average 2-4 days delay just
    > waiting for the numbers to be drawn.  (E.g., in your example, suppose
    > someone is disqualified on June 20?)

On June 13, one collects the random numbers from June 12th
The list is published, and the lotto of June 19th is identified as being (a)
re-initialize source.  We wait for challenges and refusals.
On June 19th the new lotto numbers come out, and they get collected.
If this person is disqualified before the process is re-run on the 20th, then
maybe it's all good.   Or maybe it's this EKR-detailed attack where people
are strategically withdrawn?

Worse case, of course, is that they are disqualified after the new numbers,
and one has do it again.

    >> The two weeks are because we have to give people a chance to review.
    >> That's a people process, not a technical one, right?

    > Not just.  The whole process.

So, what I'm not getting is why the new random sources are such a major
impact to the timeline, when I think it's really the people process.
(I agree that they are a pain, and I'm not convinced they are worth it)



--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide