IETF Logo Mail Archive

Re: [Eligibility-discuss] On 3797 alternatives

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 01 June 2023 18:00 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 1B760C1522D7 for <eligibility-discuss@ietfa.amsl.com>; Thu, 1 Jun 2023 11:00:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 W6u4ojxFowmW for <eligibility-discuss@ietfa.amsl.com>; Thu, 1 Jun 2023 11:00:52 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (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 5C941C151B2D for <eligibility-discuss@ietfa.amsl.com>; Thu, 1 Jun 2023 11:00:52 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [142.169.16.93]) by relay.sandelman.ca (Postfix) with ESMTPS id 5ACAC1F45B; Thu, 1 Jun 2023 18:00:50 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 0AA0EA63A4; Thu, 1 Jun 2023 14:00:49 -0400 (EDT)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 0792DA6377; Thu, 1 Jun 2023 14:00:49 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
cc: eligibility-discuss@ietfa.amsl.com
In-reply-to: <8320D717-9BE0-4B94-8CE4-B560AA7B9BC0@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>
Comments: In-reply-to "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org> message dated "Thu, 01 Jun 2023 14:16:22 -0000."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 01 Jun 2023 14:00:49 -0400
Message-ID: <20951.1685642449@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/vr9cCIQTrtnWd0sigbZUO0fRHc0>
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: Thu, 01 Jun 2023 18:00:55 -0000

Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org> wrote:
    > That is an important question. Precedent says to “just pick the next
    > one on the list” without re-seeding. It is what has been done
    > previously, most recently as this past NomCom. RFC 8713 implies you
    > reseed, and I cannot see how to do that without taking approximately
    > two weeks to do the whole process (announce, confirm, select,
    > challenge).

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?

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

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*

v2.23.0 | Report a Bug | By Email