Re: Challenge: was Re: Updated Nomcom 2020-2021: Result of random selection process

Martin Duke <martin.h.duke@gmail.com> Fri, 10 July 2020 21:26 UTC

Return-Path: <martin.h.duke@gmail.com>
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 6FCBA3A09F2 for <ietf@ietfa.amsl.com>; Fri, 10 Jul 2020 14:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 cBj7GqOSoBpE; Fri, 10 Jul 2020 14:26:39 -0700 (PDT)
Received: from mail-io1-xd29.google.com (mail-io1-xd29.google.com [IPv6:2607:f8b0:4864:20::d29]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E54F3A09E3; Fri, 10 Jul 2020 14:26:39 -0700 (PDT)
Received: by mail-io1-xd29.google.com with SMTP id a12so7463540ion.13; Fri, 10 Jul 2020 14:26:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=n7n+Bqh0MvceRsjlrCdB5Y6ruWpqTtw4IY7daTUF5hY=; b=htnWGPGR3PGfiIsJMqscaitDoaVj8wbRx3w5kl1S7tJUc2GIldJ5Sirc20lg2X2vK6 153tvowk58R2HxNffmfNh1bz9H3JpBtHcfMZtLce3/GEW6/gnIZyA4FhovG88ziyKzLX DIqCoxW/KqAizWiU5vAtzG51mwTMnA7M+BJHIwLMesRCvQFFvW6BKlReCFbKtoZH4m6t Tqy/cDRstcT4jGtoW8aMseg6jJ7QldwvakYSfcA39Jhxn+68nnmCdMj/+nYjJnWx4bdc niVMwcjZemZoSZLv5Q/b/5MDHZSajMlOcFcqthRslr/31xjRalDhpQh3sR/oD8mVI/2q WHbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=n7n+Bqh0MvceRsjlrCdB5Y6ruWpqTtw4IY7daTUF5hY=; b=qQ+CuSM8hmms0eoRhvmyjr+M6XramlahKoTxu6dWA6hpbeyaOwGtP9hEy+vIx5RyV0 fsiVLPhR6f5hKg/tYIMht1cyaoZc0Y3r4iNPpxtBl6u2oVNp4KkqEfNlCKhBb0zdKs7T tslWTeKD1UFeFggX3lpd/B5Hd4Uyxi0GEVSzUT5vSoEHOQAg7ZPok1LGwjTtpLmtEAyo tDaHoFzTajvB8aT7603WhJ6crBKBSiOpHzAPnZzy+YAYXNp6otvq3Z6JW8pYiFMy0EIg nNMWiMRPVfPkNUgXmllU0bcz4PKtcgbM4yEyRxiyVy4TGMKQkMQ4wSxuhd4IJ95YLdOk qQiw==
X-Gm-Message-State: AOAM533mKeCO6SVEj8l+80MN9f/oUiLfhSBeJO2oyP6aWfU2usGe7vMC IoKlPmOBTfjKfVWjZ2Z2u1EvfdA8ESaLqrvEIrg=
X-Google-Smtp-Source: ABdhPJw4KdIQcspi/M82varWKTv3N5ztvaKsaZ8ffHzZ9NOYinGGIiW43LeiWrPM9cr3SXJVoCbB3qH7JWmqKvfoh8Y=
X-Received: by 2002:a05:6638:223:: with SMTP id f3mr79859668jaq.144.1594416397973; Fri, 10 Jul 2020 14:26:37 -0700 (PDT)
MIME-Version: 1.0
References: <159422819660.27889.6475902734358747001@ietfa.amsl.com> <b4f5a3cf-5fab-8188-926a-a4100f776610@comcast.net> <2085D0ED888C7E7E50DCE8B4@PSB>
In-Reply-To: <2085D0ED888C7E7E50DCE8B4@PSB>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Fri, 10 Jul 2020 14:26:26 -0700
Message-ID: <CAM4esxTc48ApCfx_aPakG5HgRsA_4am1h3K9TTQzy2HJjq9SfQ@mail.gmail.com>
Subject: Re: Challenge: was Re: Updated Nomcom 2020-2021: Result of random selection process
To: John C Klensin <john-ietf@jck.com>
Cc: Michael StJohns <mstjohns@comcast.net>, NomCom Chair 2020 <nomcom-chair-2020@ietf.org>, ietf@ietf.org
Content-Type: multipart/alternative; boundary="000000000000067d4f05aa1cffc3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X24KWyBLHlGP1VWhkOtj7sbAs88>
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: Fri, 10 Jul 2020 21:26:42 -0000

On Fri, Jul 10, 2020 at 11:28 AM John C Klensin <john-ietf@jck.com> wrote:

> The attack scenario would be: suppose EvilCo [1] wants to get,
> not only two people on the Nomcom but, if possible, two of their
> most skilled committee-manipulators.  In that case, they put
> _many_ people into the Nomcom candidate pool, enough to create,
> not only high odds of getting two positions in the top ten but
> good odds of getting several of slots 11-15 as well.  Then those
> who are selected stop down in favor of of the preferred
> manipulators.  Note that redoing the random draw would not
> effect that scenario and the likelihood that more people in the
> pool would yield more top slots (as sell as more bottom slots of
> course)-- it would just reshuffle the deck.
>

I don't believe this analysis is correct. For EvilCo's plan to work, the
two preferred people have to be in positions N+1 and N+2 on the list, which
is exceedingly unlikely. If the secondary people withdraw, it's as if they
had never been on the list in terms of positioning.

What is possible is for EvilCo to increase the probability of getting
someone onto the NomCom, and if more than two people are drawn, for EvilCo
to pick which two actually serve. This eliminates the disincentive for more
staff from a single entity to volunteer, because they might bump someone
more senior or capable. That may or may not be a problem! But adding dummy
volunteers doesn't get you any closer to getting a certain person on, IIUC.