Re: [Eligibility-discuss] NomCom selection Fwd: Notification for draft-eastlake-rfc3797bis-00.txt

Lars Eggert <lars@eggert.org> Mon, 22 May 2023 10:39 UTC

Return-Path: <lars@eggert.org>
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 69C51C151063 for <eligibility-discuss@ietfa.amsl.com>; Mon, 22 May 2023 03:39:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=eggert.org
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 aruaJtgbAsPm for <eligibility-discuss@ietfa.amsl.com>; Mon, 22 May 2023 03:39:03 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 A37D4C1519BF for <eligibility-discuss@ietf.org>; Mon, 22 May 2023 03:39:03 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by localhost (Mailerdaemon) with ESMTPSA id 457E88C3F2; Mon, 22 May 2023 13:38:55 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eggert.org; s=dkim; t=1684751937; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding; bh=5aPxWQ+9NMjSkrH66Adx0XQR+aTv1GYJV7jTLu7PC2M=; b=NdLp80tc+wt/1fnvNOtLODsrAJmq8xnqmxu32IcRfs7O3n9ifop42GhAxjOfbpz1uNHo7J 3v3OLQL1fHNOpVrzpf24bYKAR7Qpr68cGyxeVMqjp+oUpZ35NW4m/ZyxPdj1hPQszqazoW oAmH8lDvj4+LUKPtIThGtqceHrRtNB5r3e5gP+JVTThtxp8O1jBn9qG7O2iKjKsZtlOhkt jFhRNC6Wxm/MgFf3P4X4oJGT36Eoq3vmlhQQgO6Y65jtX0An2mIjbVthJzi6ERRKKxkH/+ fOUXggRP2XlLw1VVc5ZhOaSkPuEiHXHjCX3qDnR5kY0/U6JSGTx2psqPXeeCvg==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Lars Eggert <lars@eggert.org>
Mime-Version: 1.0 (1.0)
Message-Id: <54F373CD-1E97-42BC-9AAB-0451ABD9D448@eggert.org>
Date: Mon, 22 May 2023 13:38:55 +0300
Cc: Donald Eastlake <d3e3e3@gmail.com>
To: eligibility-discuss@ietf.org
X-Last-TLS-Session-Version: TLSv1.3
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/cbCGyzpaLUzsUb53Q8K2rY4LtHU>
Subject: Re: [Eligibility-discuss] NomCom selection Fwd: Notification for draft-eastlake-rfc3797bis-00.txt
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: Mon, 22 May 2023 10:39:07 -0000

Hi,

with the publication of RFC9389, I am ready to close the ELEGY WG. I am unaware of any suggestions for future work, with one wrinkle:

There is one wrinkle, and that is Don's I-D below. *If* there is any interest in the community that that should be talken forward at this time to become an RFC, a (rechartered) ELEGY WG seems like the correct home. (It could of course also go forward as AD-sponsored.)

(I'll note that Don hasn't indicated whether he would like to see this progressed towards an RFC, but I am assuming that he would.)

The chairs and I would appreciate some feedback on what to do here.

Thanks,
Lars

> On 24. Aug 2022, at 03:56, Donald Eastlake <d3e3e3@gmail.com> wrote:
> 
> I have posted an rfc3797bis draft. It has lots of updates but
> currently has the same basic algorithm. I plan to add material to it
> to address the need some people see to re-randomize when selection has
> to be extended beyond the initial selection provided in RFC 3797.
> 
> Thanks,
> Donald
> ===============================
> Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> 2386 Panoramic Circle, Apopka, FL 32703 USA
> d3e3e3@gmail.com
> 
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org>
> Date: Tue, Aug 23, 2022 at 8:13 PM
> Subject: New Version Notification for draft-eastlake-rfc3797bis-00.txt
> To: Donald E. Eastlake <d3e3e3@gmail.com>
> 
> A new version of I-D, draft-eastlake-rfc3797bis-00.txt
> has been successfully submitted by Donald E. Eastlake and posted to the
> IETF repository.
> 
> Name:           draft-eastlake-rfc3797bis
> Revision:       00
> Title:          Publicly Verifiable Nominations Committee (NomCom)
> Random Selection
> Document date:  2022-08-23
> Group:          Individual Submission
> Pages:          26
> URL:            https://www.ietf.org/archive/id/draft-eastlake-rfc3797bis-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-eastlake-rfc3797bis/
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-eastlake-rfc3797bis
> 
> 
> Abstract:
> This document describes a method for making random selections in such
> a way that the unbiased nature of the choice is publicly verifiable.
> For example, the selection of the voting members of the IETF
> Nominations Committee (NomCom) from the pool of eligible volunteers.
> Similar techniques would be applicable to other cases.
> 
> 
> 
> The IETF Secretariat