Re: Selection of the committee

Kyle Rose <krose@krose.org> Mon, 08 August 2022 12:43 UTC

Return-Path: <krose@krose.org>
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 D064CC14F74E for <ietf@ietfa.amsl.com>; Mon, 8 Aug 2022 05:43:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=krose.org
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 5dzaOPaNpSen for <ietf@ietfa.amsl.com>; Mon, 8 Aug 2022 05:43:11 -0700 (PDT)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 01BDEC13CCDA for <ietf@ietf.org>; Mon, 8 Aug 2022 05:43:10 -0700 (PDT)
Received: by mail-ed1-x52c.google.com with SMTP id x21so11152002edd.3 for <ietf@ietf.org>; Mon, 08 Aug 2022 05:43:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=ou0rf8KxmS5xeJ8XbJqT9xX6qkcBMHNlgRFzS2as0tE=; b=kJ5TmbnxtEwY3nZV/S8pH1kUKZazot1PdLL/eR3MHuXKP2qjIaldRjzWHgZPoD3w/P Yf5VTbfRTRvStQ6mjq/4DYfeTGaCy4LY6nfboBCTDMI5azXfBM8wZcIBC1Vwk+kDjefJ moiVVvOG3SfQr3iVIa9al02gNgITifyuymjhw=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=ou0rf8KxmS5xeJ8XbJqT9xX6qkcBMHNlgRFzS2as0tE=; b=EkCI7jolx2jPfMC++cvSYMuaq6QIxJ4scoUqjKSIZISmDl4X1bF9yPKePsb/spSXMh 5KctoOBv4M/l30KUUs49vSDTknIINQexpuxCW2kLX94sjyEjACf4RxI45u0LKursDBSb vuuOV0p0eKxahdPfKce0CuA1J0UQHYAzEDvzjD7vlf2wiVx/DSIqNW1o301cIhkWd9Ub PTnxiyry2VKbesUSI08n3naydYacyAMbJ/Ck3sDkg+Qvq6WiAKahsaAD7oSR1VyoQbL2 yWAJ4bnZrwqmd7TytuTtkUzaBSIwF+TRrBRqj30TxZSpeXY42+1sVcn/r+L7n5yeX8ZL QTmg==
X-Gm-Message-State: ACgBeo0z9iS+6ZwfZ4H57ao6RF9TPhLtJeazpWkiaBcW9TR09Q74ilVE RaALjoINEF8vhoSBwkMGLdl8SFk3rPanBodzgj3VL95MkbJJmg==
X-Google-Smtp-Source: AA6agR7rJthhhOY9Ux+5vdNxs6eNUNqIXYriFYseC4ViKzkOhrhlAnB8HDNyWPciYngK7r8gpvpZTvUHGLsM/DjVj/k=
X-Received: by 2002:a05:6402:5202:b0:43d:d2ff:5109 with SMTP id s2-20020a056402520200b0043dd2ff5109mr17235684edd.88.1659962588951; Mon, 08 Aug 2022 05:43:08 -0700 (PDT)
MIME-Version: 1.0
References: <165962842267.55560.5671027661352747211@ietfa.amsl.com> <CAC4RtVBJE6yLkcWiaseiCfZd+=RmPqPXfyt5oNCay29P+O+2XA@mail.gmail.com>
In-Reply-To: <CAC4RtVBJE6yLkcWiaseiCfZd+=RmPqPXfyt5oNCay29P+O+2XA@mail.gmail.com>
From: Kyle Rose <krose@krose.org>
Date: Mon, 08 Aug 2022 08:42:57 -0400
Message-ID: <CAJU8_nWjC2Dm1kJK4SueosZQftDF4TnKre3gu3zo9nVYvGdJ0w@mail.gmail.com>
Subject: Re: Selection of the committee
To: Barry Leiba <barryleiba@computer.org>
Cc: nomcom-chair-2022@ietf.org, ietf@ietf.org
Content-Type: multipart/alternative; boundary="000000000000748dd105e5ba2813"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9K-QiMNMwOIo4ADXZE-lvZ98HEY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 08 Aug 2022 12:43:15 -0000

To maintain the integrity of the process as-intended by RFC 3797, there can
be no changes to the candidate pool once the seeds have been determined
(i.e., once the selected events have come to pass). At that point, the pool
must be immutable. If there are policy disqualifications such as those
you've identified, Barry, they must now be made by skipping such candidates
after the order has been determined. While the text in the RFC refers to
"uncertainty" in the pool:

   The best way to handle this is to maintain the announced schedule,
   INCLUDE in the published pool all those whose eligibility is
   uncertain and to keep the published pool list numbering IMMUTABLE
   after its publication.  If someone in the pool is later selected by
   the algorithm and random input but it has been determined they are
   ineligible, they can be skipped and the algorithm run further to make
   an additional selection.

the need to avoid any possibility of gaming the selection process is the
*purpose* of the pool being made immutable prior to determination of the
seeds, and so using the resolution process recommended for "uncertain
eligibility" for those who should have been removed at an earlier stage is
the only appropriate action at this point.

Kyle

On Mon, Aug 8, 2022 at 8:24 AM Barry Leiba <barryleiba@computer.org> wrote:

> Rich, I note that on the last "final list" that you posted, you still
> list me and Victor Kuarsingh.  We both asked you to remove our names,
> because as ISOC Trustees we can not be on the NomCom (the ISOC BoT is
> the confirmation body for IAB selections).
>
> Did you run the algorithm with our names on the list?  Did you remove
> our names before running the algorithm?  Running the algorithm against
> the list you posted on 25 July does not give the same results you
> posted below.  Can you please post the actual volunteer list that you
> used, with the volunteers numbered?
>
> Thanks,
> Barry
>
> On Thu, Aug 4, 2022 at 11:54 AM NomCom Chair 2022
> <nomcom-chair-2022@ietf.org> wrote:
> >
> > The random seeds, as specified earlier, are as follows:
> > # The seven numbers from Tuesday August 2 Euro-Millions
> > 7 18 28 40 48 8 11
> > # The six numbers from Monday August 1 US Powerball
> > 15 21 31 36 65 16
> > # The eight numbers from Saturday July 30 Australian TattsLotto
> > 17 21 12 26 8 42 35 13
> > # The nine numbers from the July 29 Japanese Lotto 7
> > 1 10 13 14 16 25 27 5 21
> >
> > I implemented RFC 3797 in Python and it can be found at
> https://github.com/richsalz/ietf-rfc3797  It includes a test-case to run
> against the "worked example" from that RFC.
> >
> > The following people have been picked:
> > Mike Jones Microsoft michael.jones@microsoft.com p1+p2
> > Ron Bonica Juniper Networks rbonica@juniper.net p1+p2+p3
> > Marc Petit-Huguenin Impedance Mismatch LLC marc@petit-huguenin.org p1+p3
> > Chris Lemmons Comcast alficles@gmail.com p1
> > Vishnu Pavan Beeram Juniper Networks vbeeram@juniper.net p1+p2+p3
> > Sarah Banks Corelight sbanks@encrypted.net p1+p2+p3
> > Varun Singh Daily.co varun.singh@iki.fi p3
> > Pascal Thubert Cisco Systems pthubert@cisco.com p1+p2+p3
> > Daniel King Lancaster University d.king@lancaster.ac.uk p1+p3
> > Christian Huitema Private Octopus Inc. huitema@huitema.net p1+p3
> >
> > I have contacted them separately.  This note starts the two-week
> challenge time.
> >
>
>