Re: List of volunteers for the 2021-2022 NomCom

John C Klensin <john-ietf@jck.com> Mon, 28 June 2021 01:22 UTC

Return-Path: <john-ietf@jck.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 C0B683A2435 for <ietf@ietfa.amsl.com>; Sun, 27 Jun 2021 18:22:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] 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 0X9auD468Lz3 for <ietf@ietfa.amsl.com>; Sun, 27 Jun 2021 18:22:08 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC7743A2433 for <ietf@ietf.org>; Sun, 27 Jun 2021 18:22:06 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1lxfyL-0006vg-AN; Sun, 27 Jun 2021 21:22:01 -0400
Date: Sun, 27 Jun 2021 21:21:55 -0400
From: John C Klensin <john-ietf@jck.com>
To: Michael StJohns <mstjohns@comcast.net>, Mary B <mary.h.barnes@gmail.com>
cc: ietf@ietf.org
Subject: Re: List of volunteers for the 2021-2022 NomCom
Message-ID: <9CF84BC133A96E4584BECF33@PSB>
In-Reply-To: <18f319d8-01d9-efb3-c576-aace73d88f76@comcast.net>
References: <c2148075-606d-8aa9-d7b4-71aa92a09fae@comcast.net> <1E2C4254-FE64-4862-8650-D5BA8A8CF86D@gmail.com> <3975.1624807060@localhost> <CAP8yD=tKs6jeMs-ZGUYoAWJqTAWTx5EzciEwsZGUrV9v8MFX4A@mail.gmail.com> <LO2P265MB0399544A2F5CC973B22CB9CBC2049@LO2P265MB0399.GBRP265.PRO D.OUTLOOK.COM> <71ca761b-5987-3c5e-83f2-20a661e6a14f@joelhalpern.com> <22399.1624829128@localhost> <ccacbe24-cdd5-1707-03cb-a2e09ae801a9@comcast.net> <CABmDk8nvDD9tM-ybaw+fZcEHZ14S84f9MFaT8vrTrtX+EgEXbQ@mail.gmail.com> <18f319d8-01d9-efb3-c576-aace73d88f76@comcast.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kZn56aUkJQsgP_2Yd_h6cKLpi8w>
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: Mon, 28 Jun 2021 01:22:13 -0000


--On Sunday, June 27, 2021 20:12 -0400 Michael StJohns
<mstjohns@comcast.net> wrote:

> On 6/27/2021 8:00 PM, Mary B wrote:
>> [MB] Per the process, I don't think that it allows more than
>> *2*  from  a single company.  So, I think the problem isn't
>> as bad as some  perceive.  Personally, I see the bigger
>> problem as the fact that  *many* that were qualified didn't
>> volunteer. [/MB]
>> 
> The problem (IMNSHO) is that, statistically, if you (company)
> have a large enough proportion of the pool, you have a pretty
> much guaranteed probability of having 2 members.   If you
> have 2 members for every nomcom, you can have a
> disproportionate impact in the overall composition of the
> leadership of the IETF over time.
>...

Mike, while I completely agree, I am also thinking about how
much bigger we would need to make the pool to overcome the
number of volunteers from that company, i.e., to make their
fraction of the volunteers small enough relative to the total to
significantly reduce the chances of their ending up with two
Nomcom members.  If the goal is to increase pool diversity,
getting more volunteers would probably do it.  If it is to
reduce the influence of a small list of organizations, I'd
doubtful that we could bring enough people out even though I
think it might be worth a try.

I favor extending the period for people to volunteer by a week
or so and believe, as you and others have suggested, that it
falls well within the limits and precedents of other deadlines
we extend when that seems sensible.  However, if the goal is to
prevent an organization from guaranteeing itself one or two
Nomcom seats [1] there are some obvious ways to do that, but
they would clearly require the sort of significant procedural
changes that Joel, Brian, and others seem to be warning against.

best,
   john



[1] Whether that is via a coordinated effort or just as
consequence of the ways in which people are encouraged to
participate (including trying to guarantee support for
attendance at IETF meetings as others have suggested) actually
makes no difference as far as Nomcom diversity (not just pool
diversity) is concerned.