Re: [Gendispatch] Diversity and Inclusiveness in the IETF

Keith Moore <moore@network-heretics.com> Fri, 26 February 2021 00:21 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 1C7DA3A1280 for <ietf@ietfa.amsl.com>; Thu, 25 Feb 2021 16:21:47 -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 JqJczME-8EZn for <ietf@ietfa.amsl.com>; Thu, 25 Feb 2021 16:21:45 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD2BC3A127D for <ietf@ietf.org>; Thu, 25 Feb 2021 16:21:45 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id DE9B2953 for <ietf@ietf.org>; Thu, 25 Feb 2021 19:21:44 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 25 Feb 2021 19:21:45 -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=MVtCQxJnXjJMPpdbcymBXxSE5ZVjOgaNdDOHmooGg LA=; b=gAK3k5Hb4UAFoiLVy1wWVF9gPpQvVVemtB2gsKCWEEjWqYYtXUry6tDnK zC4vvfV7aR7aUXcTPkwYNFD/4WE2/l1bcnKvr/gaRh3gq50RymnIjphwudfIPJKP qUsU091Axi8N4Ttbkrq4wRXP7u6H1E7qGwiQjV5O1dMQL8oiUA3ttovdAz1m7TaT Pw3h2QbhdqwqJeYohbQnWAqu5Bs7RulbiwFBEE856C0Uf9ytYlWuWr/JOzr0BVk7 tD59XKoFREaKnQq3+N7Q8EKS/c/NbGcihzKNXAKL4teqICfnV89pb1gOqHcnn0Re tY1rjFpRGE5/MbgIRxrd5Ocb/RrcQ==
X-ME-Sender: <xms:GD84YEZaLnwQWg5aNxsB-XoAOVeMMlCspBg_NRV8O0NZ14xel1MZow> <xme:GD84YF7zzNZND-nOEa7_bj3L22awQRmJHTHpFhstz_PrWYdnWdWf03KINQnZ9mNz- B5pWMrgFVpuLg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrledtgddvvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepuffvfhfhkffffgggjggtgfesthekre dttdefjeenucfhrhhomhepmfgvihhthhcuofhoohhrvgcuoehmohhorhgvsehnvghtfiho rhhkqdhhvghrvghtihgtshdrtghomheqnecuggftrfgrthhtvghrnhephefhuedtheefgf efgffhkeehgfeugfeiudeugeejkeefleelueeiffetfeeuudeunecukfhppedutdekrddv vddurddukedtrdduheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrih hlfhhrohhmpehmohhorhgvsehnvghtfihorhhkqdhhvghrvghtihgtshdrtghomh
X-ME-Proxy: <xmx:GD84YM8dfA98lkQnP7dcau57qVr6OUL_Q1le-3m8p3kYZVIW-pFRyQ> <xmx:GD84YBb3HiWb9TshdAp7NMI7VOYn08pYGGD-HetMqhXCkGjjPnt2MA> <xmx:GD84YF7bYvYF1fw_rWhFB2dUqv9n8GI02YNVfVZf2MB9WqLcbFDpzQ> <xmx:GD84YPg9LlCw5h12TVaoXQyD2EUfkiIUWRonlHX2QLbeCH2u0992ig>
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 E448B1080057 for <ietf@ietf.org>; Thu, 25 Feb 2021 19:21:43 -0500 (EST)
Subject: Re: [Gendispatch] Diversity and Inclusiveness in the IETF
To: ietf@ietf.org
References: <37eecb9b-f0eb-e21c-b162-b1f0339e4981@si6networks.com> <446A8D6B-E624-49E0-B67E-D1F8AFC794E2@lastpresslabel.com> <28ac1e86-f641-b9e8-0f61-6ff442feaa90@si6networks.com> <LO2P265MB057322BA95B1B44D4175356BC29E9@LO2P265MB0573.GBRP265.PROD.OUTLOOK.COM> <b24ce0e9-8912-12b1-af8a-6024ae83288f@si6networks.com> <25E1B1D5-E8F1-4053-A1E0-6B2948577E84@akamai.com> <3a8dca6d-0aca-d578-0f7a-3f68e2811bad@si6networks.com> <9FBF7792-8507-45F2-B06C-2173BCDF7D4C@akamai.com> <4fc62af0-cbf0-c923-5e24-fc0dfc1de996@si6networks.com> <B8DDE7D2-0105-45D5-93FB-34FF8561D888@akamai.com> <d5854cb1-ff93-6284-5106-93dd8a06f6f1@si6networks.com> <F758F440-55ED-44DE-A613-C19C3BE14160@akamai.com> <CABcZeBMutHGPKyAS+Apq-zAUjXRcpfEvAGPDuB6oejGkfkEtCw@mail.gmail.com> <b478aa64-43cd-e0f7-1913-974f7c8a191b@si6networks.com> <8B649927-DC39-4E59-95F9-A83C3CD8F494@akamai.com> <3c5b4c2a-e770-6809-5649-76adf15c67ba@si6networks.com> <7E0F4F4E-8BD2-4D1A-B998-2F4B09DA1DF4@akamai.com>
From: Keith Moore <moore@network-heretics.com>
Message-ID: <cec1266c-cda7-9e71-6b18-23d874aa037f@network-heretics.com>
Date: Thu, 25 Feb 2021 19:21:43 -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: <7E0F4F4E-8BD2-4D1A-B998-2F4B09DA1DF4@akamai.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/MuhwR8m6UqgEpAROU_LXlM8Q5UM>
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: Fri, 26 Feb 2021 00:21:47 -0000

On 2/25/21 6:49 PM, Salz, Rich wrote:

>>     So... mailing list are seen as a problematic mechanism to carry our work?
>>
>> For some people I think the answer is yes.  It seems that overall use of email is declining, but it's hard to get real numbers without getting tangled up in email marketing newsletter business.

Some people prefer other ways of collaborating, and email also seems 
worse than it used to be.   As far as I can tell there are many reasons 
for that: mobile devices have resulted in reduced attention spans (who 
wants to read and mark up an Internet-Draft over a phone?), increasingly 
inconsistent user experience from one user to another, poor support for 
plain text, spam, a tendency of lots of different programs to clutter 
email with low-value notifications, etc.

It's still hard to beat email for IETF's purposes, though: it's very 
accessible and inclusive, low cost, doesn't require proprietary 
interfaces, easy to archive (and allows storage of arbitrary metadata in 
the message header), searchable, can use it without risk of vendor 
lockin, and seems to offer less risk to participants' privacy than other 
collaboration tools.

More generally I think the very nature of IETF - collaboration between 
large numbers of individuals from all over the planet and working in a 
wide variety of environments - inevitably requires some compromises.   
We will sometimes need to use tools that aren't our first choices, and 
we may need to use those tools differently than we'd use, say, with 
co-workers at our employers.   We can probably adapt and improve those 
interfaces over time, but some balance will need to be maintained 
because the same tool that optimizes one person's experience is likely 
to pessimize someone else's.

Keith