IETF Logo Mail Archive

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

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 30 May 2023 00:03 UTC

Return-Path: <paul.hoffman@vpnc.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 B64F8C1516E2 for <eligibility-discuss@ietfa.amsl.com>; Mon, 29 May 2023 17:03:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, KHOP_HELO_FCRDNS=0.399, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no 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 38Y6aq-q6EPP for <eligibility-discuss@ietfa.amsl.com>; Mon, 29 May 2023 17:03:26 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 054C2C14CEFA for <eligibility-discuss@ietf.org>; Mon, 29 May 2023 17:03:25 -0700 (PDT)
Received: from [10.32.60.195] (76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70]) (authenticated bits=0) by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id 34U08Aie057122 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 29 May 2023 17:08:11 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host 76-209-242-70.lightspeed.mtryca.sbcglobal.net [76.209.242.70] claimed to be [10.32.60.195]
From: Paul Hoffman <paul.hoffman@vpnc.org>
To: Joel Halpern <jmh@joelhalpern.com>
Cc: eligibility-discuss@ietf.org
Date: Mon, 29 May 2023 17:03:24 -0700
X-Mailer: MailMate (1.14r5937)
Message-ID: <B953359D-72A9-4032-857E-490AEAF60C4A@vpnc.org>
In-Reply-To: <ffa1d82b-a22b-f68f-5000-6a1ca437d147@joelhalpern.com>
References: <54F373CD-1E97-42BC-9AAB-0451ABD9D448@eggert.org> <1229DD7D-3640-4EFD-8058-D0EC18020038@eggert.org> <18537EEF-4E16-4C48-8456-02A8FB0C8CFC@vpnc.org> <4a8f2bb4-25c3-5514-f13f-8db1804619a6@joelhalpern.com> <0531CD69-AAA4-4657-9B90-B50F76D997B7@vpnc.org> <ffa1d82b-a22b-f68f-5000-6a1ca437d147@joelhalpern.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/at79xtaFFX42G8_FNGm2eDC0UMc>
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: Tue, 30 May 2023 00:03:27 -0000

On 29 May 2023, at 16:54, Joel Halpern wrote:

> Sorry, I can parse which parts of 3797 you w want to replace and which parts you want to retain.  Apparently, I misunderstood your intention.  Can you please explain?

Sure.

1) RFC 3797 explains how to have a ceremony with a list of candidates, where a subset of those candidates are selected using a random number that cannot be significantly affected by any of the candidates, nor by the person holding the ceremony. RFC 3797 uses integer modular arithmetic on an ordered group based on a large random number; my draft uses hashes of names concatenated with an difficult-to-predict value.

2) RFC 3797 shows how to have this ceremony within the context of the IETF (eligibility, challenge, over-representation in the selected set, ...).

My draft is only aimed at making #1 simpler and easier to understand and having essentially the same security. If folks here like that idea, all the parts of the ceremony from #2 can be wrapped around it.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email