RE: On diversity in the NomCom

John C Klensin <john-ietf@jck.com> Wed, 15 July 2020 04:50 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 852333A0EBE for <ietf@ietfa.amsl.com>; Tue, 14 Jul 2020 21:50:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 MGSAYTCjB3yS for <ietf@ietfa.amsl.com>; Tue, 14 Jul 2020 21:50:57 -0700 (PDT)
Received: from bsa2.jck.com (ns.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 73C453A0EBD for <ietf@ietf.org>; Tue, 14 Jul 2020 21:50:56 -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 1jvZNc-000D56-B3; Wed, 15 Jul 2020 00:50:52 -0400
Date: Wed, 15 Jul 2020 00:50:47 -0400
From: John C Klensin <john-ietf@jck.com>
To: Andrew Campling <andrew.campling@419.consulting>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: RE: On diversity in the NomCom
Message-ID: <F3139D113B3E26A10A4FA773@PSB>
In-Reply-To: <LO2P265MB057314666B58592E78DEFB40C2610@LO2P265MB0573.GBRP265.PROD.OUTLOOK.COM>
References: <7429392e-a411-4c40-8fa9-f03de558b7ca@dogfood.fastmail.com> <CAChr6Sweag6G2sfdOrpGUZnPybK4eqn-EHFVHMgSv5V+MtHcow@mail.gmail.c om> <d3187a20-76a8-0ef9-d32f-6b8e400a0d30@gmail.com> <ee517835-1ad4-e2c0-a33b-e194f7c37f95@gmail.com> <LO2P265MB057314666B58592E78DEFB40C2610@LO2P265MB0573.GBRP265.PROD.OUTLOOK.COM>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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/asHrUgf_wqTOJtntGic4ipccVlc>
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: Wed, 15 Jul 2020 04:50:59 -0000


--On Tuesday, July 14, 2020 22:54 +0000 Andrew Campling
<andrew.campling@419.consulting> wrote:

> On 14-Jul-20 21:57, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
> 
>> I'd also like to challenge the assumption that the result is
>> necessarily bad.
>> 
>> If the IETF was a more typical SDO, we'd be funded by
>> membership subscriptions and we might  well have voting
>> weighted by membership categories. So big companies would
>> have  proportionate power. For good reasons, we don't do
>> that. Nevertheless, the fact is that big  companies can (and
>> do) send more people, and provide more sponsorship (such as
>> hosting  meetings, and funding Area Directors), than small
>> companies. If they didn't get something  back for that, they
>> would complain, or simply withdraw their resources. The
>> chance to have  two people in the NomCom is quite a small
>> "something" IMHO.
> 
> I think that this is a very valid point.  I do wonder though
> whether there may be an opportunity to inject a little more
> diversity into the process by requiring the second NomCom
> member from any organisation to be based in a different
> continent than the first?  This shouldn't be too onerous for
> big companies as their operations will typically have
> multinational if not global scope.  It would be even better to
> have limits on the total number of NomCom members from a given
> country and/or continent but at least seeking some diversity
> from within companies would be a good start.

I'm not sure that is the right problem to solve.  First, some
big companies who have multinational operations may not have
technical Internet operations in as many countries as they have
operations of any type, so the effect of such a rule might
easily be to limit them to a single Nomcom member where the
randomization process would have given them too.  Those same
companies often move people around for either short or long
appointments in different facilities.  That can lead to the sort
of hairsplitting that I think we are best off avoiding rather
than trying to make rules to cover every case (or require us to
give the Chair sufficient discretion to make at least some of us
anxious).  For example, assume the first person selected from a
given company is in country A.  The second person is a citizen
of country B but is on a long-time assignment, perhaps nominally
a permanent one, in country A.  Eligible or not?   If that is a
short-term appointment for, say, less than a year, but they
normally work in country B, does that change the eligibility?
Conversely, suppose the second person is a citizen of country A
working in country B?   Are they eligible?  Or suppose they
normally work in country A but transfer to country B.   How long
before or after the first Nomcom list is drawn from the pool is
it ok for them make that move and be eligible because there is
already someone on the Nomcom list from that company and country
A?

I don't know the answer to any of those questions, but I'm
fairly sure that trying to lay out all of the cases (the above
is certainly not a complete list) and make rules for each would
be crazy-making and that we would still encounter an edge case.


So I don't think we should go there regardless of the advantages
of perceived demographic diversity unless we are really, really
sure that those advantages would be worth the pain.

Let me suggest something different, and a different kind of
diversity, that has come up before in other forms.  Assume that
we can agree that the current 6 of 10 situation is a problem.  I
think it could then actually be three rather different problems:

(1) Absent the kinds of geographical you suggest, it may reduce
geographical diversity.

(2) I recognize what Brian is saying and may have more to say
about it when I get my thoughts together, but the very fact that
a disproportionate fraction of the Nomcom puts us at risk of a
Nomcom with certain types of biases that typically go with such
companies.  For example, suppose there are two candidates for a
given slot on the IESG.  Both are qualified from the standpoint
of prior IETF participation and leadership at the WG level and
both are technical leaders in the relevant area.   One of them
believes quite passionately that the IETF has gotten too complex
and too expensive in which to participate and that it should be
an objective to reduce complexity, costs, time commitments
needed to participate in the leadership, and so on.   The other
has spent most of her or his career in large companies with
generous travel support and generous support for the IETF and
similar bodies.  All thing being equal, one would expect a
Nomcom most of whose members come out of those large (and
generous) company environments to be less sympathetic to the
problems the first person identifies with and hence less
sympathetic to that person than would be the case for a Nomcom
with more diversity of organization types, occupational
categories, etc.

(3) Typically, these bigger companies tend to have much of their
technical interests --at least as represented by the people they
support to participate in  the IETF-- in a relatively small
number of IETF areas.  To the extent that is true and their two
Nomcom members (or five or six of the group from that collection
of companies), that face may reduce the diversity of the Nomcom
with regard to Areas (both in the IETF sense and areas of work
more generally), reducing the range of perspectives about what
is important, where the Nomcom should spend its time getting
things just right, and what expertise is available in the Nomcom
for candidate evaluation.

It is not impossible to address the third and still stick to
objective criteria.  One could ask volunteers for the Nomcom to
identify, not just an employer but the not more than two IETF
Areas in which they most strongly identify and/or have done most
of their work.  One could then think about a rule much like the
one you suggested about geography: if a given company already
had one volunteer seated who was associated with a given Area,
any other candidates from that company who came to the top of
the queue would be disqualified unless they identified with a
different area.     If that information were made public --it
certainly should not be a secret -- it would be hard to game
(and much less complex than sorting out geography) because its
not passing a laugh test would be grounds for a challenge.  

I don't know whether having that sort of criterion would be a
good idea, but I believe that examining it would be, at least, a
useful thought experiment and that more diversity in the Nomcom
along those lines would be useful in practice.

best,
   john