Re: Diversity and Inclusiveness in the IETF

Keith Moore <moore@network-heretics.com> Tue, 23 February 2021 04:34 UTC

Return-Path: <moore@network-heretics.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 D311A3A25D6 for <ietf@ietfa.amsl.com>; Mon, 22 Feb 2021 20:34:02 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=messagingengine.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 1HmI5I8b5W8u for <ietf@ietfa.amsl.com>; Mon, 22 Feb 2021 20:34:01 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 303BF3A25D5 for <ietf@ietf.org>; Mon, 22 Feb 2021 20:34:01 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 3A0655C0215 for <ietf@ietf.org>; Mon, 22 Feb 2021 23:34:00 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Mon, 22 Feb 2021 23:34:00 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=grexzZYBjfDtf7i7JLf8BHIFPCatjD0XrzgsbJ7gz yY=; b=cwGUf9dhN8fvmE8qu/etHTDHMMSgwG8nnGnlTlJ55ilv5/jzVu7DmB0Ms FqZU6Kq+mjRvNBtlssIqtOVg91Soy3Fajml32m3pFPtLLVbcYXkCfpM1NV+MrSmm dE2mMSLRpt4clRFCB91GS0ekN8Gi8/onsPO8WUJzTfB/mOXf5YnyAqgPMXfZqkan uevR04Woj8HG7qp6CAa6j4RWcjmpjDTsiK5RU+lrvLh67SFgFco59mYSr+snLwM/ de+ub3pQH2G1QuPhRhvKyfRrVk9JY/JJU3R91WLIq4L1eIYZlmDMcOFpw/FGpON4 dl8poqZSqJnf4bXNbaAeQtPn5sUUA==
X-ME-Sender: <xms:t4U0YMzGDyH-0q95vwc4yPkmv8LWVaE1favzT08nnkVDvr4IM8R2KA> <xme:t4U0YANu2NRRbMOLA0F1LUNb9eEcJbUqgmK0JkjLmALvVEYEGQWZo9t7wASvZmCuC U4-ldnhcr0Q0g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrkeeggdejvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthekre dttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhephefhuedtheefgf efgffhkeehgfeugfeiudeugeejkeefleelueeiffetfeeuudeunecukfhppedutdekrddv vddurddukedtrdduheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:t4U0YLN-5rhyhlMPH5LMLmfRKXzfnSFkR25GpR4pa4kbI-gMIoY9RA> <xmx:t4U0YCSxp5hueeWdey3TXqa9dq1twXuf85tL2qajDYv7a3GIveslYQ> <xmx:t4U0YNDNuzxNtB6Puglv1fdA5IaDspYTfk67Q95DVeltQDn5q6_iQg> <xmx:uIU0YC4-_ZExw3Z9MdHHKVEIwnxQuvzZjPXy4qriIK7CV6mWHtRvFA>
Received: from [192.168.1.90] (108-221-180-15.lightspeed.knvltn.sbcglobal.net [108.221.180.15]) by mail.messagingengine.com (Postfix) with ESMTPA id B97E91080059 for <ietf@ietf.org>; Mon, 22 Feb 2021 23:33:59 -0500 (EST)
Subject: Re: Diversity and Inclusiveness in the IETF
To: ietf@ietf.org
References: <37eecb9b-f0eb-e21c-b162-b1f0339e4981@si6networks.com> <3c2d646d-f18d-4d88-b458-29dbd486432b@beta.fastmail.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <c946eb86-6c67-0711-eb6b-19aa8173b5be@network-heretics.com>
Date: Mon, 22 Feb 2021 23:33:58 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <3c2d646d-f18d-4d88-b458-29dbd486432b@beta.fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kiAn8k3xEm0rXhtSd4UNHIw6bBA>
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: Tue, 23 Feb 2021 04:34:03 -0000

On 2/22/21 11:19 PM, Bron Gondwana wrote:

> One of the biggest barriers to entry in the IETF is stumbling across 
> an area in which no work is able to progress due to entrenched issues 
> within that area.

+1

> But it's hard to get started if you don't already have the connections 
> to have your work sponsored by somebody who already knows their way 
> around the IETF's idiosyncrasies.
Agree.  And yet, you shouldn't be required to work with any specific 
person to get around those idiosyncrasies.   Perhaps we need better ways 
for new contributors to identify experienced people who can help them 
navigate those treacherous waters?  Or maybe we could do a better job of 
documenting those idiosyncrasies?

Conditions do change over time.  Sometimes people keep fighting old 
battles that made sense at one time based on an old set of conditions, 
but may keep fighting those battles after those conditions have changed 
and the old concerns no longer apply.

Keith