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

Paul Hoffman <paul.hoffman@vpnc.org> Mon, 29 May 2023 22:27 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 AF9F5C14CF1D for <eligibility-discuss@ietfa.amsl.com>; Mon, 29 May 2023 15:27:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.495
X-Spam-Level:
X-Spam-Status: No, score=-1.495 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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 m-vsmSyITJnA for <eligibility-discuss@ietfa.amsl.com>; Mon, 29 May 2023 15:27:27 -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 C0274C14E513 for <eligibility-discuss@ietf.org>; Mon, 29 May 2023 15:27:27 -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 34TMVxAc053082 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 29 May 2023 15:32:01 -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: Lars Eggert <lars@eggert.org>
Cc: eligibility-discuss@ietf.org
Date: Mon, 29 May 2023 15:27:14 -0700
X-Mailer: MailMate (1.14r5937)
Message-ID: <18537EEF-4E16-4C48-8456-02A8FB0C8CFC@vpnc.org>
In-Reply-To: <1229DD7D-3640-4EFD-8058-D0EC18020038@eggert.org>
References: <54F373CD-1E97-42BC-9AAB-0451ABD9D448@eggert.org> <1229DD7D-3640-4EFD-8058-D0EC18020038@eggert.org>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/CApV9zjMCF3va7jmJYFHW2V-BPA>
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, 29 May 2023 22:27:32 -0000

By a weird coincidence, I was creating a new, simpler choosing protocol when this discussion came up. A colleague was seeing if RFC 3979 fit their need to select m of n people, but had problems with the implementation of 3797. When I looked at draft-eastlake-rfc3797bis-02, I saw that the pitfalls that were in 3797 were still there, and this spurred me to come up with something as good but simpler.

Please see <https://datatracker.ietf.org/doc/draft-hoffman-genarea-random-candidate-selection/>. It may be of interest for the discussion of draft-eastlake-rfc3797bis. Please note that the proposal could be turned into an RFC even if the IETF wants to keep using the protocol in draft-eastlake-rfc3797bis; there is good reason to have a simpler protocol defined for others who want to have the same result as what we have for NomCom, but using an easier-to-understand alternative.

--Paul Hoffman