Re: [Gendispatch] Diversity and the IETF
Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 12 July 2023 21:06 UTC
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE15DC151524; Wed, 12 Jul 2023 14:06:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=gmail.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 zi6q8vr4jcwz; Wed, 12 Jul 2023 14:06:18 -0700 (PDT)
Received: from mail-pf1-x436.google.com (mail-pf1-x436.google.com [IPv6:2607:f8b0:4864:20::436]) (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 09F10C1522C4; Wed, 12 Jul 2023 14:06:18 -0700 (PDT)
Received: by mail-pf1-x436.google.com with SMTP id d2e1a72fcca58-6689430d803so27526b3a.0; Wed, 12 Jul 2023 14:06:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689195977; x=1691787977; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=LeNXYioF73vYrOFYdrB/JjDGvVzflo2EMwSjrRZZri4=; b=rCdrwsEQOIpHYn2LFnScmBlb6wjuOSWTYJvTHW4qdTbY3TEF4UB/kur4YsBZJQ7GMw 6P6bVEIn30TSYTK7R8ukGj5VVHw52zm8ikAFyiCXtfHRvSr7WqWjdtx7JUtcdpi/q3Gc 9g1CGYeFu7f9cx8m6DTrb19nY6UfKy9HnQ/RTJBP2PuNmFI5IEbAlNHccHplgr5FA0De sIls91TIYyTNRh42Bjm/6HrGVEzQT3KF4uhR43e3pLXR731gi5gSS03iTQYkbxFBOWA3 8oSoenXERJVIlqpnG3aZooVAw2U44vYErVvfz3SfePkTXPuvw2jU8xLgScoM0N9sNEhU 8rrg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689195977; x=1691787977; h=content-transfer-encoding:in-reply-to:from:references:cc: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=LeNXYioF73vYrOFYdrB/JjDGvVzflo2EMwSjrRZZri4=; b=Gr2SIHqiyWcMXgKps5T6My7K460uBz8YV9LmTQbfNSy/T1x42KyOTGFVZtMhcxyE/K aha5zYjIEN5pNrWxKtdZxyaD7wzQpapkOH0aTyY7NnevHMcRyGVtvlJqHWGcHvEE5St3 hxB2DWVEpZ4s/95/4vaRVA+isxmtaVjaqoRw9LI4eXA2DDnBPxGcSESgMxtdOwS4kK1y OEx7QR3QYjuXeZ5MjlIpBc6SjKhXxYOqUbS9Bt/aJx8AapgCndQ6J9MnrBHTVoh2/2aG cTJJx6dywGlA40xs6R42d9lK56scE2WSXeHXY7FtLxaG5WiNQVJGXgYu6/jPE9Xqw1Gb G8mQ==
X-Gm-Message-State: ABy/qLbIi3uuK9BnlMjJc7/tSIAmK3mKLG54iI2HXIIiY06y9MDBfj0R NGlyXgwNnrGjcHkckkhjdlE=
X-Google-Smtp-Source: APBJJlEhFz19EaAPDyJD5c2P31YvkDr3bmQm9kOwNxhP3OFZoMgrUcVWakDnRTN+j+3pfx3mfuqMCw==
X-Received: by 2002:a05:6a00:15c6:b0:682:4c9f:aa1 with SMTP id o6-20020a056a0015c600b006824c9f0aa1mr22492314pfu.5.1689195977065; Wed, 12 Jul 2023 14:06:17 -0700 (PDT)
Received: from ?IPV6:2406:e003:10cc:9901:b2e1:1101:7ba7:19fd? ([2406:e003:10cc:9901:b2e1:1101:7ba7:19fd]) by smtp.gmail.com with ESMTPSA id g8-20020aa78188000000b006783ee5df8asm3996389pfi.189.2023.07.12.14.06.14 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 12 Jul 2023 14:06:16 -0700 (PDT)
Message-ID: <1813bd19-ce80-2689-e01e-ec1fab6b4e85@gmail.com>
Date: Thu, 13 Jul 2023 09:06:12 +1200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Andrew Campling <andrew.campling@419.consulting>, Andrew Alston <Andrew.Alston@liquidtelecom.com>, John Levine <johnl@taugh.com>, "gendispatch@ietf.org" <gendispatch@ietf.org>
Cc: "vittorio.bertola@open-xchange.com" <vittorio.bertola@open-xchange.com>, "eodir@ietf.org" <eodir@ietf.org>
References: <1581018401.44788.1687878647487@appsuite-gw1.open-xchange.com> <20230627195853.5B3AFFCFA856@ary.qy> <AM7PR03MB6451721EF8A6998A7B81CDDCEE30A@AM7PR03MB6451.eurprd03.prod.outlook.com> <CWXP265MB5153ED063C597FB565123799C230A@CWXP265MB5153.GBRP265.PROD.OUTLOOK.COM>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <CWXP265MB5153ED063C597FB565123799C230A@CWXP265MB5153.GBRP265.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/3AEWOb87GurniuKPBNSzweu4XqA>
Subject: Re: [Gendispatch] Diversity and the IETF
X-BeenThere: gendispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: General Area Dispatch <gendispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch/>
List-Post: <mailto:gendispatch@ietf.org>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gendispatch>, <mailto:gendispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Jul 2023 21:06:21 -0000
At the risk of going off topic for both lists, I have a few comments below:
On 11-Jul-23 00:59, Andrew Campling wrote:
> (Changing the subject line to reflect a broadening of the topic)
>
> The IETF community has a diversity problem, whether that is terms of more obvious categories like gender, ethnicity or geographic origin, or in terms of diversity of thought and experience. In addition to policy makers, we appear to lack people such as CISOs and others in the end-user community, have pretty limited involvement from civil society, even a relative dearth of network operators etc. This is a problem because I firmly believe that a diverse community is more likely to make better standards.
Yes, in the abstract, but it all depends on what kind of diversity we achieve.
>
> Whilst it is true that the IETF is open, there are more than a few unintended barriers to entry, coupled with what is perceived by some as an adversarial culture that deters participation [1].
However, if what we want is the best technical solution (i.e., avoiding absurd diplomatic compromises like the two different OSI network layers or the 48 byte ATM cell size), the adversarial approach and the *rough* consensus model that it requires are actually desirable.
> Note for example the relatively high percentage of people that only participate in a single in-person meeting – some of these may well be taking advantage of the meeting being held in their home town but the numbers are nevertheless high.
>
> Because of the relatively homogenous nature of the community, while I agree that we need to be sure that people are clear they are attending as individuals, making efforts to proactively reach out beyond the tech sector in order to diversify our participant base seems to me to be an entirely reasonable thing to do (hence my involvement in EODIR).
Whether it's reasonable depends on the type of diversity we seek. This is an engineering organisation and its outputs are engineering documents. I'd strongly welcome engineers from a wider range of countries and user communities (as an example, at the last IETF a document I'm working on got extremely valuable input from the National Marine Electronics Association). There are of course good reasons why we might want more input from (and output to) public policy people, rights advocates, sustainability experts, law enforcement people, even sigint people, but it needs to be input that has engineering relevance. The day we lose engineering focus will be the day that the IETF becomes a waste of space. That's why we also need to divert discussion to ISOC (or elsewhere) when it ceases to be an engineering discussion.
Regards
Brian
> We can avoid any suggestion of one group being given precedence by broadening the outreach to encompass others, the exact targeting could potentially be a topic for the next EODIR meeting if the co-chairs agree.
>
> Andrew
>
> [1] Cath-Speth, C, 2021, “/Changing Minds and Machines: A Case Study of Human Rights Advocacy in the Internet Engineering Task Force (IETF)”/, Oxford Internet Institute
>
> *From:*Andrew Alston <Andrew.Alston@liquidtelecom.com>
> *Sent:* Monday, July 10, 2023 7:56 AM
> *To:* John Levine <johnl@taugh.com>; gendispatch@ietf.org
> *Cc:* vittorio.bertola@open-xchange.com
> *Subject:* Re: [Gendispatch] Updated draft: Policy experts are IETF stakeholders
>
> So,
>
> Speaking with no hats,
>
> I have deep concern about starting to state explicitly that any group of people are welcome, because the instant you do that, it has implications that some people aren’t welcome. The IETF works on the principle that people participate in their individual capacities. The way I have always viewed this is that, if people have something to contribute, let them contribute, the email lists are open, and the mic lines do not restrict who can stand up and have their voice heard.
>
> When we start saying “Policy makers are welcome” – what follows? Do we start to single out other groups of people in further documents? The reality is that anyone who can provide meaningful contributions to documents is – and should continue to be – welcome, and I feel that the moment you start to single out one group over another, it opens a door that is probably best left shut and creates a potentially very slippery slope. We potentially create a situation where all are equal, but some are more equal than others. That cannot happen, it would be disastrous in my opinion.
>
> I wish to draw attention to Section 2 of the IETF TAO, which states:
>
> “The IETF welcomes all interested individuals: IETF participants come from all over the world and from many different parts of the Internet industry.”
>
> Further to this – RFC3935 (Section 1) states:
>
> Open process - any interested person can participate in the work,
>
> know what is being decided, and make his or her voice heard on the
>
> issue.
>
> As such – I believe that we have already stated that the stakeholders are those who participate, and the participation is open to all, and no group should be given precedence over any other group. And while I do not believe that the intention of the authors of this document intends to give anyone precedence, I have concern that the adoption of this document could unintentionally do exactly that – by implication.
>
> Thanks
>
> Andrew
>
> **
>
> Internal All Employees
>
> *From: *Gendispatch <gendispatch-bounces@ietf.org <mailto:gendispatch-bounces@ietf.org>> on behalf of John Levine <johnl@taugh.com <mailto:johnl@taugh.com>>
> *Date: *Tuesday, 27 June 2023 at 22:59
> *To: *gendispatch@ietf.org <mailto:gendispatch@ietf.org> <gendispatch@ietf.org <mailto:gendispatch@ietf.org>>
> *Cc: *vittorio.bertola@open-xchange.com <mailto:vittorio.bertola@open-xchange.com> <vittorio.bertola@open-xchange.com <mailto:vittorio.bertola@open-xchange.com>>
> *Subject: *Re: [Gendispatch] Updated draft: Policy experts are IETF stakeholders
>
> It appears that Vittorio Bertola <vittorio.bertola@open-xchange.com <mailto:vittorio.bertola@open-xchange.com>> said:
>>you will encounter people who are not "policy experts", but just want to bring the view of some stakeholders and ensure that their needs are
>>considered. In other words, not all people participate because of their policy-making skills or experience; some just participate because
>>they have a stake in the topic. This is why I would steer away from words like expert or specialist if possible.
>
> Well, OK, but I would also want to be clear that policy experts are welcome,
> policy lobbyists less so.
>
> R's,
> John
>
> --
> Gendispatch mailing list
> Gendispatch@ietf.org <mailto:Gendispatch@ietf.org>
> https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fgendispatch&data=05%7C01%7CAndrew.Alston%40liquidtelecom.com%7C0058f560743e4c0962b108db7748f6bc%7C687926120f0e46cbb16afcb82fd80cb1%7C0%7C0%7C638234927496446764%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=uM5mA7g2UySTSHD6Y%2FiuSSapor3A25ScNM06DK5%2FWyU%3D&reserved=0 <https://www.ietf.org/mailman/listinfo/gendispatch>
>
>
- [Gendispatch] Updated draft: Policy experts are I… Stacie Hoffmann
- Re: [Gendispatch] Updated draft: Policy experts a… Stephen Farrell
- Re: [Gendispatch] Updated draft: Policy experts a… Joel Halpern
- Re: [Gendispatch] Updated draft: Policy experts a… Stephen Farrell
- Re: [Gendispatch] Updated draft: Policy experts a… Brian E Carpenter
- Re: [Gendispatch] Updated draft: Policy experts a… Christian Huitema
- Re: [Gendispatch] Updated draft: Policy experts a… Stacie Hoffmann
- Re: [Gendispatch] Updated draft: Policy experts a… Stephen Farrell
- Re: [Gendispatch] Updated draft: Policy experts a… John Levine
- Re: [Gendispatch] Updated draft: Policy experts a… Vittorio Bertola
- Re: [Gendispatch] Updated draft: Policy experts a… Stephen Farrell
- Re: [Gendispatch] Updated draft: Policy experts a… Livingood, Jason
- Re: [Gendispatch] Updated draft: Policy experts a… Bob Hinden
- Re: [Gendispatch] Updated draft: Policy experts a… Adrian Farrel
- Re: [Gendispatch] Updated draft: Policy experts a… Phillip Hallam-Baker
- Re: [Gendispatch] Updated draft: Policy experts a… John R Levine
- Re: [Gendispatch] Updated draft: Policy experts a… Phillip Hallam-Baker
- Re: [Gendispatch] Updated draft: Policy experts a… Martin Thomson
- Re: [Gendispatch] Updated draft: Policy experts a… Eric Rescorla
- Re: [Gendispatch] Updated draft: Policy experts a… Eric Rescorla
- Re: [Gendispatch] Updated draft: Policy experts a… Eliot Lear
- Re: [Gendispatch] Updated draft: Policy experts a… Christian Huitema
- Re: [Gendispatch] Updated draft: Policy experts a… Eliot Lear
- Re: [Gendispatch] Updated draft: Policy experts a… Colin Perkins
- Re: [Gendispatch] Updated draft: Policy experts a… Vittorio Bertola
- Re: [Gendispatch] Updated draft: Policy experts a… Jay Daley
- Re: [Gendispatch] Updated draft: Policy experts a… Eric Rescorla
- [Gendispatch] savage beasts at IETF meetings Jim Reid
- Re: [Gendispatch] Updated draft: Policy experts a… Mallory Knodel
- Re: [Gendispatch] Updated draft: Policy experts a… Phillip Hallam-Baker
- Re: [Gendispatch] Updated draft: Policy experts a… Brian E Carpenter
- Re: [Gendispatch] Updated draft: Policy experts a… John Levine
- Re: [Gendispatch] Updated draft: Policy experts a… Stacie Hoffmann
- Re: [Gendispatch] Updated draft: Policy experts a… Vittorio Bertola
- Re: [Gendispatch] Updated draft: Policy experts a… John Levine
- Re: [Gendispatch] Updated draft: Policy experts a… Rob Sayre
- Re: [Gendispatch] Updated draft: Policy experts a… Andrew Alston
- Re: [Gendispatch] Updated draft: Policy experts a… Andrew Alston
- Re: [Gendispatch] Updated draft: Policy experts a… Tony Rutkowski
- Re: [Gendispatch] Updated draft: Policy experts a… Salz, Rich
- Re: [Gendispatch] Updated draft: Policy experts a… Andrew Alston
- [Gendispatch] Diversity and the IETF Andrew Campling
- Re: [Gendispatch] Updated draft: Policy experts a… Vittorio Bertola
- Re: [Gendispatch] Updated draft: Policy experts a… Rob Sayre
- Re: [Gendispatch] Updated draft: Policy experts a… Tony Rutkowski
- Re: [Gendispatch] Updated draft: Policy experts a… Rob Sayre
- Re: [Gendispatch] Updated draft: Policy experts a… Phillip Hallam-Baker
- Re: [Gendispatch] Updated draft: Policy experts a… Mallory Knodel
- Re: [Gendispatch] Diversity and the IETF Brian E Carpenter
- Re: [Gendispatch] Updated draft: Policy experts a… Eliot Lear
- Re: [Gendispatch] Updated draft: Policy experts a… Stacie Hoffmann