Re: Randomness sources for the IETF 2021-2022 Nomcom Selection

Samuel Weiler <weiler@csail.mit.edu> Thu, 01 July 2021 13:42 UTC

Return-Path: <weiler@csail.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4FD83A091B for <ietf@ietfa.amsl.com>; Thu, 1 Jul 2021 06:42:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0j_pxUsSejfE for <ietf@ietfa.amsl.com>; Thu, 1 Jul 2021 06:42:14 -0700 (PDT)
Received: from cyrus.watson.org (cyrus.watson.org [204.107.128.30]) by ietfa.amsl.com (Postfix) with ESMTP id 0A73F3A0914 for <ietf@ietf.org>; Thu, 1 Jul 2021 06:42:13 -0700 (PDT)
Received: from sams-2020-air (c-24-63-251-193.hsd1.ma.comcast.net [24.63.251.193]) by cyrus.watson.org (Postfix) with ESMTPSA id 3A5A966E44; Thu, 1 Jul 2021 13:42:12 +0000 (UTC)
Date: Thu, 01 Jul 2021 09:42:11 -0400
From: Samuel Weiler <weiler@csail.mit.edu>
To: Michael StJohns <mstjohns@comcast.net>
cc: ietf@ietf.org
Subject: Re: Randomness sources for the IETF 2021-2022 Nomcom Selection
In-Reply-To: <41ee7838-1214-29b6-3f6b-460718d7bebc@comcast.net>
Message-ID: <191d38f-15a5-9e6a-3c1e-22b61614824@watson.org>
References: <162508214004.24798.754651887914942887@ietfa.amsl.com> <41ee7838-1214-29b6-3f6b-460718d7bebc@comcast.net>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1494629730-1625146932=:6534"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SDo2-AKi68KDcOhOgxi6mfeCUhE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Jul 2021 13:42:24 -0000

On Wed, 30 Jun 2021, Michael StJohns wrote:

> First, you may want to give yourself a few days between close of challenges 
> and doing the pull.  If there are challenges and they need to be resolved, 
> you need to be able to reschedule *before* ANY of the random sources are 
> resolved without looking like you're putting your thumb on the scale.  If 
> you've already resolved the randomness, it's possible to game things a slight 
> bit by announcing changes of affiliation or withdrawals.

Thanks for flagging this Mike.

As I understand it, the current "challenge period" is one the current 
NomCom chair adopted - it is not required by 8713 nor 8989.  8713 
does, though, require a challenge period AFTER the selection is run - 
see section 4.17.

I think the NomCom chair can proceed down this path, perhaps with the 
precaution that the order and numbering of the current list be fixed 
as it is now - and anyone later disqualified (even in the interval 
before the selection) will be skipped over.

This would be consistent with the practice in 8713 section 4.17 when 
challenges are raised after the selection runs.

-- Sam