IETF Logo Mail Archive

Re: [Eligibility-discuss] The NomCom replacement selection process (with seed)

"Salz, Rich" <rsalz@akamai.com> Thu, 27 July 2023 23:13 UTC

Return-Path: <rsalz@akamai.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 3F70DC15106F for <eligibility-discuss@ietfa.amsl.com>; Thu, 27 Jul 2023 16:13:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, 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_NONE=0.001, T_SCC_BODY_TEXT_LINE=-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 (2048-bit key) header.d=akamai.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 LtnzhBRpcZP9 for <eligibility-discuss@ietfa.amsl.com>; Thu, 27 Jul 2023 16:13:53 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (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 4849CC14E515 for <eligibility-discuss@ietf.org>; Thu, 27 Jul 2023 16:13:53 -0700 (PDT)
Received: from pps.filterd (m0122331.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 36RI4sF0023339; Fri, 28 Jul 2023 00:13:52 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=5+xiPTVn77DmEF/71TKXZhFhxUI/BszydJSG6/imWMQ=; b=BxagV4tkOQpYt8GcMo496SltNzPgsNxwN3kQc8vd/EtENKYll0MEJ7vM8i2OJl+JV5UW nsNEX4Asu8lhOU2xaJh0AkZy9EGDWEbTKHqVPZTdKmzKksudvJS518+QucQrpGcjHc7d PsrmYgatFDCHANd6g4QpjF7+om/bhROyHWF20b0wsz8gfH4t7cvRxlht+bJZ5suSbuSR uXFvhx6DqpEz8S0Rzjz4KR20wCvlXZkSPLG226W0QSgnEEfqbFH8nVb44A7780tt+wnB cDn/2+0FfBH5zk6rnKU4RhUOzfzT/G/pOPMGhORkMe6DUeUATh3lB6MCMy8udjpHiww6 bA==
Received: from prod-mail-ppoint7 (a72-247-45-33.deploy.static.akamaitechnologies.com [72.247.45.33] (may be forged)) by mx0b-00190b01.pphosted.com (PPS) with ESMTPS id 3s0400ah0b-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 28 Jul 2023 00:13:52 +0100
Received: from pps.filterd (prod-mail-ppoint7.akamai.com [127.0.0.1]) by prod-mail-ppoint7.akamai.com (8.17.1.19/8.17.1.19) with ESMTP id 36RJn1vT028579; Thu, 27 Jul 2023 19:13:51 -0400
Received: from email.msg.corp.akamai.com ([172.27.50.201]) by prod-mail-ppoint7.akamai.com (PPS) with ESMTPS id 3s0aewjhv7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 27 Jul 2023 19:13:51 -0400
Received: from ustx2ex-dag4mb4.msg.corp.akamai.com (172.27.50.203) by ustx2ex-dag4mb2.msg.corp.akamai.com (172.27.50.201) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.12; Thu, 27 Jul 2023 16:13:51 -0700
Received: from ustx2ex-dag4mb4.msg.corp.akamai.com ([172.27.50.203]) by ustx2ex-dag4mb4.msg.corp.akamai.com ([172.27.50.203]) with mapi id 15.02.1258.012; Thu, 27 Jul 2023 16:13:51 -0700
From: "Salz, Rich" <rsalz@akamai.com>
To: Martin Thomson <mt@lowentropy.net>, "eligibility-discuss@ietf.org" <eligibility-discuss@ietf.org>
Thread-Topic: [Eligibility-discuss] The NomCom replacement selection process (with seed)
Thread-Index: AQHZwNyES2LcxZe5x0S+CD25K39+zK/ObYiA
Date: Thu, 27 Jul 2023 23:13:51 +0000
Message-ID: <7DDE0EB4-1E97-400F-B873-2A2F98A41830@akamai.com>
References: <f3c7a87a-4125-433c-aee5-71bc19ffb2f5@app.fastmail.com>
In-Reply-To: <f3c7a87a-4125-433c-aee5-71bc19ffb2f5@app.fastmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.75.23070901
x-originating-ip: [172.27.164.43]
Content-Type: text/plain; charset="utf-8"
Content-ID: <3BF34AABA4BC9142B7ABBD18E86C88EB@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.957,Hydra:6.0.591,FMLib:17.11.176.26 definitions=2023-07-27_10,2023-07-26_01,2023-05-22_02
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 malwarescore=0 mlxscore=0 bulkscore=0 mlxlogscore=503 adultscore=0 suspectscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2306200000 definitions=main-2307270210
X-Proofpoint-ORIG-GUID: eyOk02msZNDMQOlALwu_A--iM40z64VJ
X-Proofpoint-GUID: eyOk02msZNDMQOlALwu_A--iM40z64VJ
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.957,Hydra:6.0.591,FMLib:17.11.176.26 definitions=2023-07-27_10,2023-07-26_01,2023-05-22_02
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 impostorscore=0 lowpriorityscore=0 phishscore=0 adultscore=0 spamscore=0 suspectscore=0 priorityscore=1501 mlxlogscore=475 malwarescore=0 clxscore=1011 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2306200000 definitions=main-2307270212
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/fpkHULgIAvJN8c8kPN0YILpSqwQ>
Subject: Re: [Eligibility-discuss] The NomCom replacement selection process (with seed)
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, 27 Jul 2023 23:13:57 -0000

A couple of clarifying questions.

>The NomCom process tends to need to run the entire challenge period before each fallback iteration. Given that, it should be relatively easy to make a hash commitment at that time or - and this is my preference - announce a new entropy source. 

If you use the hash-chain, the idea is that at the time you announce the candidate members, you generate a secret, share it with the prev chair, and run it forward 11 times? And if you do multiple rounds you repeat the process each time you have to pick a new challengeable volunteer?

As for a new entropy source, do you replace the used ones or is it an *additional* entropy source?

> I disagree with Donald about the suitability of drand.love. For the purpose of replacement selection I believe that it is fine and better than the process that I used.

If it's additional entropy, I'd probably be okay. Another option is to say take whichever lottery source comes first after you announce the need to do an additional draw. I'd prefer that, and it probably doesn't add much delay.

v2.23.0 | Report a Bug | By Email