Re: IESG Statement On Oppressive or Exclusionary Language

Christian Huitema <huitema@huitema.net> Fri, 07 August 2020 17:32 UTC

Return-Path: <huitema@huitema.net>
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 56E043A0EA3 for <ietf@ietfa.amsl.com>; Fri, 7 Aug 2020 10:32:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level:
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.949, SPF_HELO_NONE=0.001, SPF_PASS=-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 S1kMma9FDaBF for <ietf@ietfa.amsl.com>; Fri, 7 Aug 2020 10:32:52 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 31E5F3A0E7C for <ietf@ietf.org>; Fri, 7 Aug 2020 10:32:50 -0700 (PDT)
Received: from xse46.mail2web.com ([66.113.196.46] helo=xse.mail2web.com) by mx166.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1k46EH-000qii-Nx for ietf@ietf.org; Fri, 07 Aug 2020 19:32:39 +0200
Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 4BNXSn632Yz24mQ for <ietf@ietf.org>; Fri, 7 Aug 2020 10:30:49 -0700 (PDT)
Received: from [10.5.2.17] (helo=xmail07.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1k46Cf-0004hC-Nz for ietf@ietf.org; Fri, 07 Aug 2020 10:30:49 -0700
Received: (qmail 26242 invoked from network); 7 Aug 2020 17:30:49 -0000
Received: from unknown (HELO [192.168.1.107]) (Authenticated-user:_huitema@huitema.net@[172.58.43.61]) (envelope-sender <huitema@huitema.net>) by xmail07.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 7 Aug 2020 17:30:49 -0000
To: Nico Williams <nico@cryptonector.com>, Dan Harkins <dharkins@lounge.org>
Cc: IETF discussion list <ietf@ietf.org>
References: <5692e18e-afbb-9294-1074-3b81dafe8803@network-heretics.com> <59C4CA26-A1EB-4CF4-B973-BC2BBF53A094@gmail.com> <CAL02cgTZt-9+QWPT1aWXcOgpEwuNV2uHnVi5dGm7V5y_8_U1SQ@mail.gmail.com> <0cceb0f2-b5fe-a194-7ce8-68cc537f9cd1@lounge.org> <CAL02cgTV-cfTPO2wrKz0H2E=FLhagu-qs7fwx6jXeJDH-2cSHA@mail.gmail.com> <C4A6E144-1F1E-4568-8EFC-9FD62E69F50A@akamai.com> <e0070427-9995-4a96-0f40-24603e823f09@lounge.org> <20200807165347.GR3100@localhost>
From: Christian Huitema <huitema@huitema.net>
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mDMEXtavGxYJKwYBBAHaRw8BAQdA1ou9A5MHTP9N3jfsWzlDZ+jPnQkusmc7sfLmWVz1Rmu0 J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PoiWBBMWCAA+FiEEw3G4 Nwi4QEpAAXUUELAmqKBYtJQFAl7WrxsCGwMFCQlmAYAFCwkIBwIGFQoJCAsCBBYCAwECHgEC F4AACgkQELAmqKBYtJQbMwD/ebj/qnSbthC/5kD5DxZ/Ip0CGJw5QBz/+fJp3R8iAlsBAMjK r2tmyWyJz0CUkVG24WaR5EAJDvgwDv8h22U6QVkAuDgEXtavGxIKKwYBBAGXVQEFAQEHQJoM 6MUAIqpoqdCIiACiEynZf7nlJg2Eu0pXIhbUGONdAwEIB4h+BBgWCAAmFiEEw3G4Nwi4QEpA AXUUELAmqKBYtJQFAl7WrxsCGwwFCQlmAYAACgkQELAmqKBYtJRm2wD7BzeK5gEXSmBcBf0j BYdSaJcXNzx4yPLbP4GnUMAyl2cBAJzcsR4RkwO4dCRqM9CHpVJCwHtbUDJaa55//E0kp+gH
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
Message-ID: <fb303190-f14c-ef21-eba9-23bf083647ff@huitema.net>
Date: Fri, 07 Aug 2020 10:30:49 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <20200807165347.GR3100@localhost>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
X-Originating-IP: 66.113.196.46
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.46/32
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.46/32@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0fni+3cnVNNYyS96zEouVZ2pSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDAzc5Jb/eaE0k3pqeq35lKbgN zB/4Jkrw1eDLcif59ftdDCI1+a0n9+SwyHx/R6MBU7Tmz6iKnkQL9gqsxD347235Nhqq+/HvroPq 8GSPg+60/QPNqXybIny9WGhadIo/FqANMYqm8+U1ocMliIzyKbyme9ldZJ7uNXfg/GfS8fUvP/L5 rCqHDsKZM+xa1iwJX+gRCHfMVnsAk591zk0uilUI+ZL4xWiN8NS6C+dmX6OEdA4u1aThyWrQ/ou2 +v/lmX4Em37yFgrCB6NHRn1g+f3uncIqYSL3lhh5c81YyJqFoLZMmkWsaurVZfvqROaDnDtHb8z5 dpPkEuJ8Snwqla7jUnW3hy14Yji8fo+4xCnSRo4Rcu5Z37rMuDjCny5fE9ykbJ7I9co1MAEE3ruN Xsm8UJsAPvDcVSKtDCYkioPY5Qx4fJOk03R5fJtf/Dv/dkIzS7m4GUpXCY1Y3j3ilZpnfSx1WjM8 Y221ho/pD394mWepawqbJhSWXDEVBtSw+QMzzfi0SisE2iHeMZyCsm9eEaq2+aKc0q1cJ/98E+8k 6Q9V9YO5wBS5yaTKclLkwFxGP5PlmfRKgzOGJ8361xg66gs5OuzYxJgw5atIxePaw4mGPOB1lCDk b7ANR1sPEpkwRl9BWWaU47pUusALURqf27VeHOkXe82afzWlDIvBJO4F7RXO+GjvlVdsJEdyHHAS JNUmoOHSoqgqxfHmWfZIwxxhwvMcWh0MGcvUtQjJp9T8pISzjS9/5NaFQbqi1vEjHyvS2QZiR+AZ YvfxEvZFKu+ZM2mB1CpThxyaBpbeNHk15VolAGHS5rCXQKDyCQUljhSWDhWh87HBSLhNUo4qiB0X MVQG2R7iUfOzATaF5R3hQJk8CwyURYKQ0Ye0iR3bHfnMCIEU+nrglojKwJanfcoq9IsR6l/OZb9V MEM=
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6I_v6EwAO9zcpL0HpRgOvbEgT7c>
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, 07 Aug 2020 17:32:53 -0000

On 8/7/2020 9:53 AM, Nico Williams wrote:

> On Fri, Aug 07, 2020 at 09:37:43AM -0700, Dan Harkins wrote:
>>   Speaking for myself, I won't stop contributing until something or someone
>> stops me and this isn't going to stop me. I don't think I have used
>> "master-slave"
>> in a draft or RFC but I have used the term "master key". And while I know no
>> one
>> is demanding that term be changed _right now_ it's only a matter of time.
> I haven't used offensive terminology in my RFCs.
>
> That's the thing: do we even have a problem?  I've asked in this thread
> that the author do a modicum of research to demonstrate that we do (or
> do not).  To my knowledge there has been no acknowledgement of the lack
> of evidence for the need for this proposal, let alone actual evidence.
> It's really not a lot to ask.
>
> I've also proposed that we use existing mechanisms to deal with
> offensive language in RFCs.  There's no need to have this self-DDoS
> except maybe as a way to broadcast that we're doing it (which might well
> be the whole point of the exercise for all I know).

Where I grew up in France, we did study the history of the French
Revolution. We studied it in primary school, and then in high school.
There was a very different take on the "reign of terror". In high
school, we were using the official manuals that explained terror by the
need to defend the republic. They acknowledged the regrettable excesses,
but moved on quickly. In the catholic primary school on the other end,
the memory of these "excesses" was still raw. The ritual murders and the
wanton cruelty of the representatives, the genocidal repression of the
peasantry that dared to rebel against the draft and the religious
repression, six generations later the memory was still very much alive.
Want it or not, that still inform my instinctive resistance against
imposition of language, let alone the references to guillotines by some
of the radical protesters. I understand that my colleagues of Russian
origin have similar memories, only more vivid.

I do understand that many have the same reaction to "master-slave" as me
to "guillotine". Such terms are better avoided in technical
specifications. But at the same time, I shudder at the idea of any
"purity of speech" committee. Such committees tend to discard checks and
balances because of "purity", and that leads to detestable behaviors.
That's why I would rather rely on a shared culture that goes for clear
specification than on a power structure that dictates language.

-- Christian Huitema