Re: IESG Statement On Oppressive or Exclusionary Language

Toerless Eckert <tte@cs.fau.de> Fri, 24 July 2020 16:12 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 316E23A0ECC for <ietf@ietfa.amsl.com>; Fri, 24 Jul 2020 09:12:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 rz8_zwtEIlPk for <ietf@ietfa.amsl.com>; Fri, 24 Jul 2020 09:12:45 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B93413A0F43 for <ietf@ietf.org>; Fri, 24 Jul 2020 09:12:41 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [131.188.34.52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 13B68548047; Fri, 24 Jul 2020 18:12:37 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 0BCA7440043; Fri, 24 Jul 2020 18:12:37 +0200 (CEST)
Date: Fri, 24 Jul 2020 18:12:37 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: Mark Nottingham <mnot@mnot.net>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
Message-ID: <20200724161236.GF10435@faui48f.informatik.uni-erlangen.de>
References: <159552214576.23902.6025318815034036362@ietfa.amsl.com> <E00B0B8E-434A-486D-AB0D-8BE12ECE30BD@mnot.net> <20200724151459.GD10435@faui48f.informatik.uni-erlangen.de> <A0CE866D-575C-4A32-B009-F26447C11013@akamai.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <A0CE866D-575C-4A32-B009-F26447C11013@akamai.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VYdj2FLuP2iwkENsm71OM3MWIes>
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, 24 Jul 2020 16:12:47 -0000

On Fri, Jul 24, 2020 at 03:24:10PM +0000, Salz, Rich wrote:
> >    and 20 years from now we're sitting on exactly the same mail thread and argue
>     about replacing min and sec.
> 
> That's fine.  Language evolves.  As do standards.  Nobody will ever need more than 640Kb.  Nobody will ever need more than 32bits of IP address.  Why should a document be different?

But that's different. The problem is to recurringly changing the words for
the same subject because a prior word was abused AFTER it was choosen to
address the subject.

There is a good amountd of justice for this euphemism treadmill when a new
word is picked as a euphemism without the problematic nature of the underlying
subject to be resolved. But in our case the situation is different. Our
subjects are never the ones with problematic subject matter. Its only that
our words are typically metaphors for subjects where either the original subject
is problematic, or the use of the word for the original subject has attained
_some_ negative connotations.

Cheers
---
tte@cs.fau.de