Re: [Eligibility-discuss] [Gendispatch] New Version Notification for draft-knodel-nomcom-gender-representation-00.txt

Michael StJohns <msj@nthpermutation.com> Thu, 23 November 2023 06:45 UTC

Return-Path: <msj@nthpermutation.com>
X-Original-To: eligibility-discuss@ietfa.amsl.com
Delivered-To: eligibility-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DAA1C15108E for <eligibility-discuss@ietfa.amsl.com>; Wed, 22 Nov 2023 22:45:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.904
X-Spam-Level:
X-Spam-Status: No, score=-1.904 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nthpermutation-com.20230601.gappssmtp.com
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 9gwsHiTgrZnW for <eligibility-discuss@ietfa.amsl.com>; Wed, 22 Nov 2023 22:45:10 -0800 (PST)
Received: from mail-qk1-x732.google.com (mail-qk1-x732.google.com [IPv6:2607:f8b0:4864:20::732]) (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 2E8F4C14F6EC for <eligibility-discuss@ietf.org>; Wed, 22 Nov 2023 22:45:09 -0800 (PST)
Received: by mail-qk1-x732.google.com with SMTP id af79cd13be357-777745f1541so32624585a.0 for <eligibility-discuss@ietf.org>; Wed, 22 Nov 2023 22:45:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nthpermutation-com.20230601.gappssmtp.com; s=20230601; t=1700721908; x=1701326708; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=NJuOIVHvZcPdiQEgiTXSf1RqbgGGSekxOqgFPy3UguA=; b=oFlElVNVdMj/22tccPJF2NAyH6Pgw0nkuKRHpRbo6413Z2t+AZ4Tlr/aMo1w27W+3x oGHuWHJvc0jdQ8h10iuO5qOfa2K0qODU0xqAwAD0GddDutEFiQfzBsy4+0xiyzD9wsUW t2CqYm+ZqOVVh81bANW3/7AYRrcU+5zJaZBGaxUuK1VvhmmWhxzkbbCoilYudh4bGLRJ rRvvrynIBK/eeU6sdkl7K14xU09s+ztOFKvwsfNGrsDj+DMp8fzKI2vzOpZJh7UiksQx iPBy1LkGgeHhDsJaazsIMQDYUv//+vHK44bkUFuPOXMRdKYwFr8DQ0bh8ngHgcODhhWe dzGA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700721908; x=1701326708; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=NJuOIVHvZcPdiQEgiTXSf1RqbgGGSekxOqgFPy3UguA=; b=DbLOplXOFFoAB3vy7gWXa93wuZgdW1bkXxO2+Hhy2UeC4fbCL15U8lUUMWnjMloY2J m0GDq/1bWkgFG5Z36tgo2hTustwiJ5nSFFn5q0OWnMK7soKG/H5iTfDQjSBw5oS4R0Oq 1PN8nT7SuZKRaGdVPjD9WYOXj1FU343cIgHrs5uRjIxUS5/bVifjhzzNDOvSJqGrFoyT tRFpFQ4ann9b0fQqNmes54N6h9jtx48MTtTdSkjAt4NFOqO+diUrTip9Z5ibVtkNbDTc 4Qo7fjGuJKEx8G4FKj32ubH/IpODzRSFQV2/yvqDJGWjsap70gFGmXqCfxizI0ur2CW1 yIIA==
X-Gm-Message-State: AOJu0Yxjol5HvTTbENkE02zAV900S8BUF2V486MUPwoUD1BzulzsC6l8 lJeUVicVMQXP5Po+ZZ9YJnh4zGzvoliyMC7uQEM=
X-Google-Smtp-Source: AGHT+IGxezvw+UMoV+ixmwYpWe9FFNuNnx0UC1ayhVNE76SLbwZeyZBx07i/d+KDccp/dqNeF4jklw==
X-Received: by 2002:a05:622a:1013:b0:423:70f7:a9e0 with SMTP id d19-20020a05622a101300b0042370f7a9e0mr6438374qte.17.1700721908159; Wed, 22 Nov 2023 22:45:08 -0800 (PST)
Received: from [192.168.1.23] (pool-108-31-156-76.washdc.fios.verizon.net. [108.31.156.76]) by smtp.gmail.com with ESMTPSA id x25-20020ac87a99000000b004182037f655sm255789qtr.14.2023.11.22.22.45.07 for <eligibility-discuss@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 22 Nov 2023 22:45:07 -0800 (PST)
Message-ID: <39411eb3-7947-49bf-9406-089f43ada331@nthpermutation.com>
Date: Thu, 23 Nov 2023 01:45:05 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: eligibility-discuss@ietf.org
References: <f871d358-8d9d-4714-99a8-6a51198a61c9@cdt.org> <5282ED25-E538-493A-A7B5-DA34CD0460ED@yahoo.com> <CALaySJ+4206AH0BoTvsLkn4LYw-TcdBFJSc0vCK6BR58QH=zfA@mail.gmail.com>
From: Michael StJohns <msj@nthpermutation.com>
In-Reply-To: <CALaySJ+4206AH0BoTvsLkn4LYw-TcdBFJSc0vCK6BR58QH=zfA@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/eligibility-discuss/oWVx3JSbCWqXE77d6hBrqbXD6nI>
Subject: Re: [Eligibility-discuss] [Gendispatch] New Version Notification for draft-knodel-nomcom-gender-representation-00.txt
X-BeenThere: eligibility-discuss@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF eligibility procedures <eligibility-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eligibility-discuss/>
List-Post: <mailto:eligibility-discuss@ietf.org>
List-Help: <mailto:eligibility-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eligibility-discuss>, <mailto:eligibility-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Nov 2023 06:45:15 -0000

Barry -

You tiptoed right across the line in to an ad-hominem discursion, 
arguing against who Lloyd is, rather than addressing his argument.  Not 
appropriate and somewhat deserving of an apology I would think.

Mallory -

The literature goes back further than just your single reference.  And 
in general, the literature claims that "diversity",  not solely "gender 
diversity" is what leads to "productivity, creativity and ...".  Please 
take a look at RFC7704 for a more complete discussion.  I don't agree 
with all that Dave had to say, and I believe he actually misinterpreted 
[Kellogg], but I believe that document is a better starting place than 
your Vervoe reference to a pretty much unsourced light copy document. In 
other words, I believe you need better support for your argument than 
the cited references.

Next, your "make sure you pick at least one of gender N" algorithm is 
naive in that as stated it would result mostly grabbing a woman 
(non-male?) who belongs to the pool of organizations with single 
volunteers.  [[ the max 2 org slots are usually filled before slot 10 is 
filled ]].

  I'd have to check, but that pool is rather small relative to the whole 
pool and the pool of women from organizations with single volunteers is 
a small fraction of that. (Unless the large organizations actually 
resulted in a woman being selected, the 5-6 slots the current algorithm 
guarantees them means that the remaining 4-5 slots would where the 
required selection would take place)

We have a nomcom selection algorithm that's problematic in that it can 
be gamed by organizations with large numbers of volunteers.  Deciding 
that we're going to take one of those 10 slots and assign it to one of a 
small group of 5-10 women each time we do the selection would result in 
a substantial over representation over time by specific persons and a 
specific class of person.

The above two paragraphs are based on the analysis I've done over the 
last 1/2 dz nomcoms and the selection patterns.  I'd have to run a 
number of simulations to confirm my conclusions above, but I think my 
conclusions are close to what the math would show.

Finally, as Lloyd points out, him/her/em/eirs/Ze is not one of the items 
passed on to the selection algorithm at this point, and not  everyone 
would be happy with sharing their personal concept of their gender with 
the community.

We pick randomly, and with the exception of the 2 person per org limit, 
any volunteer has an equal weight in being selected.  If you believe 
some group is underrepresented in the pool, the solutions is to recruit 
members of that group to volunteer.

I appreciate what you're trying to accomplish, but giving any class of 
participant a "me first" by virtue of their membership in that class 
seems to be problematic and may result in causing as many problems as 
they solve.  I can see people who want to be on the nomcom claiming 
membership in that class and an outcry when that's revealed.

Mike


On 11/22/2023 11:58 PM, Barry Leiba wrote:
> I've been involved in workplace gender diversity issues for more than
> 20 years, and my experience is that 100% of those who question the
> statement Mallory cites ("gender diversity has been shown to lead to
> more productivity, creativity and reinforces a culture of respect and
> value for all participants") are men.  100%.  I have never seen anyone
> question it who does not identify as male.  I think that's telling,
> and that we should think about it hard.
>
> Barry
>
> On Tue, Nov 21, 2023 at 11:29 PM Lloyd W
> <lloyd.wood=40yahoo.com@dmarc.ietf.org> wrote:
>> Hi Mallory,
>>
>> "gender diversity has been shown to lead to more productivity, creativity and reinforces a culture of respect and value for all participants"
>>
>> You're going to need some very strong references supporting that claim and similar assertions.
>>
>> Measuring gender diversity introduces privacy concerns; information may only be supplied voluntarily,  would need to be anonymised when aggregated... while gender by itself is not classed as sensitive data under the GDPR, in a predominantly male environment, identifying non-males may not be difficult. I suspect any measuring process will itself raise security concerns.
>>
>> And since this draft is advocating for affirmative action, it does need to say clearly upfront that it is advocating for affirmative action.
>>
>> Why have you chosen to focus here on affirmative action solely for gender, and not for, say, country of residence or culture, which have similarly very unbalanced representation in the IETF and nomcom?
>>
>> regards
>>
>> Lloyd Wood
>> lloyd.wood@yahoo.co.uk
>>
>> On 21 Nov 2023, at 23:02, Mallory Knodel <mknodel=40cdt.org@dmarc.ietf.org> wrote:
>>
>> Hi all,
>>
>> A short draft to consider in the selection of nomcom voting volunteers to ensure minimum gender representation, available here and copied below:
>>
>> URL: https://www.ietf.org/archive/id/draft-knodel-nomcom-gender-representation-00.txt
>> Status: https://datatracker.ietf.org/doc/draft-knodel-nomcom-gender-representation/
>> HTML: https://www.ietf.org/archive/id/draft-knodel-nomcom-gender-representation-00.html
>> HTMLized: https://datatracker.ietf.org/doc/html/draft-knodel-nomcom-gender-representation
>>
>> ===
>>
>> Operation of the IESG/IAB Nominating and Recall Committees     M. Knodel
>> Internet-Draft                       Center for Democracy and Technology
>> Intended status: Informational                          20 November 2023
>> Expires: 23 May 2024
>>
>>
>>          Gender Representation in the IETF Nominating Committees
>>                draft-knodel-nomcom-gender-representation-00
>>
>> Abstract
>>
>>     This document extends the existing limit on nomcom representation by
>>     company in order to improve gender diversity by ensuring that not all
>>     voting members of the IETF Nominating Committee (nomcom) belong to
>>     the same gender.
>>
>> About This Document
>>
>>     This note is to be removed before publishing as an RFC.
>>
>>     The latest revision of this draft can be found at
>>     https://mallory.github.io/nomcom-gender-representation/draft-knodel-
>>     nomcom-gender-representation.html.  Status information for this
>>     document may be found at https://datatracker.ietf.org/doc/draft-
>>     knodel-nomcom-gender-representation/.
>>
>>     Discussion of this document takes place on the Operation of the IESG/
>>     IAB Nominating and Recall Committees Working Group mailing list
>>     (mailto:ietf-nomcom@lists.elistx.com), which is archived at
>>     https://lists.elistx.com/archives/ietf-nomcom/.
>>
>>     Source for this draft and an issue tracker can be found at
>>     https://github.com/mallory/nomcom-gender-representation.
>>
>> Status of This Memo
>>
>>     This Internet-Draft is submitted in full conformance with the
>>     provisions of BCP 78 and BCP 79.
>>
>>     Internet-Drafts are working documents of the Internet Engineering
>>     Task Force (IETF).  Note that other groups may also distribute
>>     working documents as Internet-Drafts.  The list of current Internet-
>>     Drafts is at https://datatracker.ietf.org/drafts/current/.
>>
>>     Internet-Drafts are draft documents valid for a maximum of six months
>>     and may be updated, replaced, or obsoleted by other documents at any
>>     time.  It is inappropriate to use Internet-Drafts as reference
>>     material or to cite them other than as "work in progress."
>>
>>     This Internet-Draft will expire on 23 May 2024.
>>
>> Copyright Notice
>>
>>     Copyright (c) 2023 IETF Trust and the persons identified as the
>>     document authors.  All rights reserved.
>>
>>     This document is subject to BCP 78 and the IETF Trust's Legal
>>     Provisions Relating to IETF Documents (https://trustee.ietf.org/
>>     license-info) in effect on the date of publication of this document.
>>     Please review these documents carefully, as they describe your rights
>>     and restrictions with respect to this document.  Code Components
>>     extracted from this document must include Revised BSD License text as
>>     described in Section 4.e of the Trust Legal Provisions and are
>>     provided without warranty as described in the Revised BSD License.
>>
>> Table of Contents
>>
>>     1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
>>     2.  Gender Representation in the IETF Nomcom  . . . . . . . . . .   2
>>     3.  Suggested Remedy  . . . . . . . . . . . . . . . . . . . . . .   3
>>     4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
>>     5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
>>     6.  Informative References  . . . . . . . . . . . . . . . . . . .   3
>>     Appendix A.  Acknowledgments  . . . . . . . . . . . . . . . . . .   4
>>     Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   4
>>
>> 1.  Introduction
>>
>>     The literature supports the claims that lack of gender diversity in
>>     hiring teams reinforce under representation of gender minorities in
>>     leadership positions and that lack of gender diversity in leadership
>>     perpetuates gender discrimination [Vervoe].
>>
>> 2.  Gender Representation in the IETF Nomcom
>>
>>     The IETF considers influence and weaknesses in nomcom selection in
>>     [RFC8713].  Likewise, gender diversity in IETF leadership should be
>>     considered a community strengthening exercise insofar as gender
>>     diversity has been shown to lead to more productivity, creativity and
>>     reinforces a culture of respect and value for all participants.  If
>>     we consider the nomcom as a "team", it will itself benefit from
>>     having more gender diversity among its voting members.
>>
>>     To address gender representation in the IETF nomcom, we need only
>>     ensure that all voting members are not of the same gender.  All
>>     attempts to ensure gender representation in the nomcom should
>>     include: a. increase participation in the community from women and
>>     non-binary individuals so that the eligible pool is more gender
>>     diverse.  b. encourage eligible women and non-binary members of the
>>     community to accept selection to the nomcom.
>>
>>     While the IETF does not routinely confirm the gender of volunteers,
>>     we have committed to improving gender diversity in the community by
>>     way of measuring it and identifying concrete steps to mitigate
>>     imbalance.
>>
>> 3.  Suggested Remedy
>>
>>     The “two-per-organisation limit” can easily be extended to ensure a
>>     nomcom consisting of no more than n-1 members from any one gender
>>     (where n is the number of available volunteer slots), requiring skips
>>     for the nth slot until a gender minority volunteer is chosen.
>>
>>     This assumes that for any given pool therein contains at least one
>>     gender minority volunteer.
>>
>>     This short remedy might update [RFC8713].
>>
>> 4.  Security Considerations
>>
>>     There are no security considerations for this document.
>>
>> 5.  IANA Considerations
>>
>>     This document has no IANA actions.
>>
>> 6.  Informative References
>>
>>     [RFC8713]  Kucherawy, M., Ed., Hinden, R., Ed., and J. Livingood,
>>                Ed., "IAB, IESG, IETF Trust, and IETF LLC Selection,
>>                Confirmation, and Recall Process: Operation of the IETF
>>                Nominating and Recall Committees", BCP 10, RFC 8713,
>>                DOI 10.17487/RFC8713, February 2020,
>>                <https://www.rfc-editor.org/rfc/rfc8713>.
>>
>>     [RFC9389]  Duke, M., "Nominating Committee Eligibility", BCP 10,
>>                RFC 9389, DOI 10.17487/RFC9389, April 2023,
>>                <https://www.rfc-editor.org/rfc/rfc9389>.
>>
>>     [Vervoe]   Vervo, "Gender Discrimination in Hiring Practices", 2022,
>>                <https://vervoe.com/gender-discrimination-in-hiring-
>>                practices/>.
>>
>> Appendix A.  Acknowledgments
>>
>>     Thanks to Martin Thompson and Suresh Krishnan for informed initial
>>     thoughts on bringing this idea to the community.
>>
>> Author's Address
>>
>>     Mallory Knodel
>>     Center for Democracy and Technology
>>     Email: mknodel@cdt.org
>>
>> --
>> Gendispatch mailing list
>> Gendispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/gendispatch
>>
>> --
>> Gendispatch mailing list
>> Gendispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/gendispatch