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

Robert Sparks <rjsparks@nostrum.com> Mon, 22 May 2023 13:03 UTC

Return-Path: <rjsparks@nostrum.com>
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 E60DAC151B31 for <eligibility-discuss@ietfa.amsl.com>; Mon, 22 May 2023 06:03:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.077
X-Spam-Level:
X-Spam-Status: No, score=-2.077 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, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, 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 (1024-bit key) header.d=nostrum.com
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 Ut2PywelCkcr for <eligibility-discuss@ietfa.amsl.com>; Mon, 22 May 2023 06:03:35 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 E11EFC14CE4B for <eligibility-discuss@ietf.org>; Mon, 22 May 2023 06:03:35 -0700 (PDT)
Received: from [192.168.1.102] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.17.1) with ESMTPSA id 34MD3WhN013854 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <eligibility-discuss@ietf.org>; Mon, 22 May 2023 08:03:33 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1684760614; bh=z17NmIaFD/MexjK2cFdiZ+YYpNhMSj5N2PE9BiBDyIY=; h=Date:Subject:To:References:From:In-Reply-To; b=X4tv/ERF3q9ejEggz2jDfBoP2sUTHlq+6HQLhAepjME/qiCXZryDpIh4dr9TkFKgQ HfYrtxKrGnA5DtoO8ZhG8SX1k/Lxm95r2C99m6I6D21MNxyL5Qn6mW0/7qGFyGR+nE ou/+DqIXBe17dPHfN2gL6YD67O/T0RnopcXKVXXw=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.102]
Message-ID: <52d600e9-c5fd-a086-9690-d4ac4a6d6de2@nostrum.com>
Date: Mon, 22 May 2023 08:03:27 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.11.0
Content-Language: en-US
To: eligibility-discuss@ietf.org
References: <54F373CD-1E97-42BC-9AAB-0451ABD9D448@eggert.org>
From: Robert Sparks <rjsparks@nostrum.com>
In-Reply-To: <54F373CD-1E97-42BC-9AAB-0451ABD9D448@eggert.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/P7AMqG5lfTFrEumFHOibaq3h2J4>
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 13:03:40 -0000

I think this needs a working group, and I don't the Elegy is really the 
right place to stuff it.

The work, if taken on, isn't focusing on eligibility - it's reach is 
much broader, and I think it would deserve something shaped more like a 
BoF leading to a purposed charter.

(My opinion is that consensus around the draft's goals will be quite 
hard to build, and a bof-like chartering effort might help further 
identify what's obtainable.)

RjS

p.s. I think it's fine to close Elegy, but keep reopening it in the 
future in mind as you settle its state.

On 5/22/23 5:38 AM, Lars Eggert wrote:
> 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