Re: List of volunteers for the 2021-2022 NomCom

Brian E Carpenter <brian.e.carpenter@gmail.com> Mon, 28 June 2021 02:12 UTC

Return-Path: <brian.e.carpenter@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 E5A523A2617 for <ietf@ietfa.amsl.com>; Sun, 27 Jun 2021 19:12:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level:
X-Spam-Status: No, score=-2.437 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, NICE_REPLY_A=-0.338, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-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 QTpbrsQznr60 for <ietf@ietfa.amsl.com>; Sun, 27 Jun 2021 19:12:17 -0700 (PDT)
Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (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 4C19F3A2612 for <ietf@ietf.org>; Sun, 27 Jun 2021 19:12:17 -0700 (PDT)
Received: by mail-pj1-x1034.google.com with SMTP id bb10-20020a17090b008ab029016eef083425so11782797pjb.5 for <ietf@ietf.org>; Sun, 27 Jun 2021 19:12:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=m0L5LLTItaSVFoJOeCqBdgQVUfzJNLF/Yhmq47neQ7U=; b=gRHmsIebdvLE5x98GFuv/NBY4MGO/QeniYy9fTsfLDArQ3hUlUwat8kvJQij/iSnXW yUtC9TyPVfAey7j8v2Bbxffktnw9v6fJCD+cF7VZm5lAL3fKpV/NM+HiYe3JbSqpSY2+ gPo+YoHj9TEjFBvZzBWB4H3z0YcBHKu4ZziOWzVbXcuAhcGSyop9Ulwna9Z8hpPIYu0H +MGrYXlUzM+sHr0TnHUbN0rPf5SaZGFT9dd10Zx6GEez4Z/rr82sCtfCUBuaJldKhrhn Gi5mGCZ2+Vl1mxKXyOAuE8dIetaO18GgyquMMNPXEC+kosHEXPrbeRJNv60cd0b9oxEA wFLA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=m0L5LLTItaSVFoJOeCqBdgQVUfzJNLF/Yhmq47neQ7U=; b=dAo46hGQxXU8LqqqgDvP4z4mgU/WL0xTcxeWCe5KVf+VC9bv/Sq+2SAojClGOVp9TM aPxqh5YwPIUmXR2OS9vvPCNrlFLVC1C8Cy/ktxHuYKMvMaT16A2ZVAtMRpP5NWW8RLvZ MAzA+fSulqbaQvDhiJ2oc25tBbN7XEq+bt38L3WVZTXHS1Sicha96cKddiAavL0K4fN+ M7MaX9ws+fDLPuUhm/TTBna11rtDPvKpnHq3pPmn7Ivv+YOK8n8D4YkTYb2qps4bMgzn jOtLrk8L8LG+9vuL97z0KRW/OnHH+HMEsNPYvnWmrzZhf61z9df4ztiV5N84s+lrrhIW kffQ==
X-Gm-Message-State: AOAM533toFrF3QtSJPLmfQhaDSaN381PP2RVtSjT7JgvX1s/lgbkJn5o 7FiMUUjTX3LbswfioOERLGpJOnNrqmv+rw==
X-Google-Smtp-Source: ABdhPJxqZ1hWC5eso/LO79X51yvNfYPlD04rVsOCdVjuQuxDNfdeiKBpPfffGkmmklrojJ7c9JBetQ==
X-Received: by 2002:a17:902:d88b:b029:128:cd59:ead2 with SMTP id b11-20020a170902d88bb0290128cd59ead2mr5742834plz.27.1624846335800; Sun, 27 Jun 2021 19:12:15 -0700 (PDT)
Received: from ?IPv6:2406:e003:100d:901:80b2:5c79:2266:e431? ([2406:e003:100d:901:80b2:5c79:2266:e431]) by smtp.gmail.com with ESMTPSA id gl17sm464528pjb.13.2021.06.27.19.12.14 for <ietf@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 27 Jun 2021 19:12:15 -0700 (PDT)
Subject: Re: List of volunteers for the 2021-2022 NomCom
To: ietf@ietf.org
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> <9CF84BC133A96E4584BECF33@PSB>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <60d88c9f-b233-038c-00d7-b7a2721c45c7@gmail.com>
Date: Mon, 28 Jun 2021 14:12:12 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <9CF84BC133A96E4584BECF33@PSB>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IORm8qmwR29YsWs9lE2B7Zi8R_c>
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 02:12:19 -0000

On 28-Jun-21 13:21, John C Klensin wrote:
> 
> 
> --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.

I'm not against significant changes. I'm just against significant
changes on the fly during the current year's process.

Having looked again at BCP10, I do agree that the NomCom Chair has the
power to re-open the call for volunteers for a week or so, but that
doesn't seem worth doing without a mail shot to everybody that
the code deems to be eligible. Judging by the model we used to justify
RFC8989, it seems to me there are probably several hundred people
who may well not realise that they are eligible or even that the
call for volunteers went out. Remember we have *lots* of participants
who are not on the general lists.

   Brian

> 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.
> 
>