Re: IESG Statement On Oppressive or Exclusionary Language

Nico Williams <nico@cryptonector.com> Fri, 07 August 2020 16:53 UTC

Return-Path: <nico@cryptonector.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 7B0623A0BF5 for <ietf@ietfa.amsl.com>; Fri, 7 Aug 2020 09:53:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 xLwg7Fwi_Yel for <ietf@ietfa.amsl.com>; Fri, 7 Aug 2020 09:53:55 -0700 (PDT)
Received: from black.elm.relay.mailchannels.net (black.elm.relay.mailchannels.net [23.83.212.19]) (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 17BD13A0BCB for <ietf@ietf.org>; Fri, 7 Aug 2020 09:53:54 -0700 (PDT)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id 0786C9219CB; Fri, 7 Aug 2020 16:53:54 +0000 (UTC)
Received: from pdx1-sub0-mail-a66.g.dreamhost.com (100-96-8-55.trex.outbound.svc.cluster.local [100.96.8.55]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 80D0B921308; Fri, 7 Aug 2020 16:53:53 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|nico@cryptonector.com
Received: from pdx1-sub0-mail-a66.g.dreamhost.com (pop.dreamhost.com [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.8); Fri, 07 Aug 2020 16:53:53 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|nico@cryptonector.com
X-MailChannels-Auth-Id: dreamhost
X-Tasty-Well-Made: 3d53c4943e94acb7_1596819233774_2985670814
X-MC-Loop-Signature: 1596819233774:3070130682
X-MC-Ingress-Time: 1596819233773
Received: from pdx1-sub0-mail-a66.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a66.g.dreamhost.com (Postfix) with ESMTP id 16F647F09F; Fri, 7 Aug 2020 09:53:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to:content-transfer-encoding; s= cryptonector.com; bh=2+InLAaOXCMUyCw3pSoHHiLvozg=; b=ndS/azUDIPQ 6SWf59EwhMJG5WdcQ8wM9JUUh1G6kUYpqcdkPnPEibj8oMovb1QZEVzPkITtECbO ytmNR824Vz8aocVDDoIvQr07u88qGRyKQ40IDBm5AdRWFLwVzLywYWQHe5iVPp0s +/WCNG8LxLMLZf9A4OzOwXb4lyawdOVc=
Received: from localhost (unknown [24.28.108.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by pdx1-sub0-mail-a66.g.dreamhost.com (Postfix) with ESMTPSA id 00BC17F09E; Fri, 7 Aug 2020 09:53:50 -0700 (PDT)
Date: Fri, 07 Aug 2020 11:53:48 -0500
X-DH-BACKEND: pdx1-sub0-mail-a66
From: Nico Williams <nico@cryptonector.com>
To: Dan Harkins <dharkins@lounge.org>
Cc: IETF discussion list <ietf@ietf.org>
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
Message-ID: <20200807165347.GR3100@localhost>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
In-Reply-To: <e0070427-9995-4a96-0f40-24603e823f09@lounge.org>
User-Agent: Mutt/1.9.4 (2018-02-28)
X-VR-OUT-STATUS: OK
X-VR-OUT-SCORE: -100
X-VR-OUT-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduiedrkedvgddutddvucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuggftfghnshhusghstghrihgsvgdpffftgfetoffjqffuvfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepfffhvffukfhfgggtugfgjggfsehtkeertddtredunecuhfhrohhmpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqnecuggftrfgrthhtvghrnhepveelleelteeutdetieeltdeutefhteffheetveduveevtdfhveffhfdttddtheelnecukfhppedvgedrvdekrddutdekrddukeefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhppdhhvghloheplhhotggrlhhhohhsthdpihhnvghtpedvgedrvdekrddutdekrddukeefpdhrvghtuhhrnhdqphgrthhhpefpihgtohcuhghilhhlihgrmhhsuceonhhitghosegtrhihphhtohhnvggtthhorhdrtghomheqpdhmrghilhhfrhhomhepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomhdpnhhrtghpthhtohepnhhitghosegtrhihphhtohhnvggtthhorhdrtghomh
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IVLfTzkqpcSLFyxJrPOS-D_VH0E>
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 16:53:57 -0000

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).

Nico
--