Re: IESG Statement On Oppressive or Exclusionary Language

John Levine <johnl@taugh.com> Wed, 29 July 2020 20:58 UTC

Return-Path: <johnl@iecc.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 04E913A0DC6 for <ietf@ietfa.amsl.com>; Wed, 29 Jul 2020 13:58:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=PG7eapNg; dkim=pass (1536-bit key) header.d=taugh.com header.b=svIoW7UD
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 c5105bXtQg7h for <ietf@ietfa.amsl.com>; Wed, 29 Jul 2020 13:58:14 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 30B983A0DC5 for <ietf@ietf.org>; Wed, 29 Jul 2020 13:58:13 -0700 (PDT)
Received: (qmail 18111 invoked from network); 29 Jul 2020 20:58:13 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=46bb.5f21e2e5.k2007; bh=LXnwt1nL+003UMO3te4S3253ValCL8dUgxfa2Rlq78M=; b=PG7eapNgWw3wkeANtqympZYAkaxUCn8tfWA1mfK5P5jve5/jxqADHP3EFCJIXauqPpF1hPapl37uXm2XW8zeq6IB6O7fm3UcIF2XojawQKMgX1MVf7+bHPt1bPvkKhP38BzCS3Pi6Zp5qCeRX5lwWgacmsup5hiGOYgcytUsDf4qU1M60QHFD+bpiLC0wQFdfttNH/WheauV2xQRbO/7tiWL+EHqYJVFIiGE+1+MprXTFbWNny12ggYX5X5klzRt
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=46bb.5f21e2e5.k2007; bh=LXnwt1nL+003UMO3te4S3253ValCL8dUgxfa2Rlq78M=; b=svIoW7UD/cFJIsMKtYEY/+HMMZ65+0qU98w5f0bICd18+hH9Pv8za9HJ4u3axeC3YO61lCYxnfivxZzvyYKjwV8tPmGniOFGM/q2OXdOHW08Io0r6rOy91IFk2fBlISRfwEBKLPZqVToPyYxKIxLyyeJDsT3QxDkgJyqLIq9iGNpRXV/HQNQm/dwsT0jU/OM6brWFNmuUm9/fesP7IW3CkQAdABh9VntVOEREJqAAAYgFzT1nYKUenp6gZjyCQJN
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 29 Jul 2020 20:58:12 -0000
Received: by ary.qy (Postfix, from userid 501) id 083171DA26C9; Wed, 29 Jul 2020 16:58:13 -0400 (EDT)
Date: Wed, 29 Jul 2020 16:58:13 -0400
Message-Id: <20200729205813.083171DA26C9@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
In-Reply-To: <028eaeaf25c24469bd1add1b5cbc4554@att.com>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RwSTJ_7wc13muUdfLJX9B4PS5vE>
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: Wed, 29 Jul 2020 20:58:17 -0000

In article <028eaeaf25c24469bd1add1b5cbc4554@att.com> you write:
>-=-=-=-=-=-
>Hi Victor,
>I think I may not have described what I was suggesting clearly enough. I wasn’t proposing any fixed (i.e.,
>MANDATORY or MUST) rules. I was trying to avoid problems caused by the perception that people inside IETF would
>be identifying what words were problematic (using their own subjective criteria, and where the decision makers
>are not members of the demographics perceived to be slighted by the words), and that use of these words would be
>strictly prohibited. ...

Unfortunately, that's much too simplistic. There are lots of words
where the context is crucial. To take a familiar example, Master is a
problem in the sense of someone who owns a slave, but not in the sense
of someone who knows all about a topic. My daughter got a Master of
Arts degree this year and I don't expect her to give it back.

Certainly some words we should never use at all, like **** and !*%&#
but we never use them in I-D's anyway.

R's,
John

PS: Then there's words like "niggardly."