Re: IESG Statement On Oppressive or Exclusionary Language

John Levine <johnl@taugh.com> Sun, 09 August 2020 15:15 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 9E71B3A0CCC for <ietf@ietfa.amsl.com>; Sun, 9 Aug 2020 08:15:11 -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 (2048-bit key) header.d=iecc.com header.b=fL/R5CzK; dkim=pass (2048-bit key) header.d=taugh.com header.b=AJ9v51k+
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 X8x2PqfLKZjf for <ietf@ietfa.amsl.com>; Sun, 9 Aug 2020 08:15:10 -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 DA06E3A09F6 for <ietf@ietf.org>; Sun, 9 Aug 2020 08:15:09 -0700 (PDT)
Received: (qmail 78945 invoked from network); 9 Aug 2020 15:15:07 -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=1345e.5f3012fb.k2008; bh=Qmu61vzwR9dNt5ecFjIhfk842SFNKp6WxuOKXrUARh4=; b=fL/R5CzKpmqbOFlk95u//z8lH+CbnB2jZilln2cJ7wkcX5NNeh9g1P9SOjCUSZuYHzIkKyI4JBFYxZOFHnl0T5gtkpNGxpRGY/A4k2qBtGofdj1SRfcEcbWJSS1DFjMLslhfPwVRdA/zf3+oIdCkBa+hOKyvSWr9qsK60GXZNuf2FlRXPxjFUU25dPzzTw/ayQx4b7EZx3z+1Ug6fs8tYtserThBLRqyfTDZs7w2A8OUokWPV7VPnKdpjwhlIPpnS9vhrU1+FXOssMxJDlGx/jOgIdGGEH5WCkEewhszPlhQt5YSbz5E0SeoWa2LPExrdZz/o3AQi9TO2Oex+UT/gw==
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=1345e.5f3012fb.k2008; bh=Qmu61vzwR9dNt5ecFjIhfk842SFNKp6WxuOKXrUARh4=; b=AJ9v51k+rh2wlqPN1RdlST4yaxZf5qdjgaCvYGfelKAVAFMfDwNnlRH/fEXSrPsqSQViBv8BSgp1fGK1YcJP9qffz6BnQuKr6MN6YfiFTvMaOMlcjENv81DaBW5J6kAKyaCKO5JXZsCv8/Ko+F56+6e/elDHKjMHiDW7nf8diSxkKHAQelk0Jz9M0g6aBKo1xdkhoOmHCykMBDmcKCj6HA62c+8xJ1Fz1rzSMQyqMCKbnRmIcqnwmCpxmITmhAxrAAV0mWeJeEsCJskhkLV+MMfRbWO5dLqvClhi0sEaPOH6G5sxrNtbl6/l2WodeyVKJPe6DJVvRhlNNLgSJGk1cg==
Received: from ary.local ([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; 09 Aug 2020 15:15:07 -0000
Received: by ary.local (Postfix, from userid 501) id C3DCB1E74E58; Sun, 9 Aug 2020 11:15:07 -0400 (EDT)
Date: Sun, 09 Aug 2020 11:15:07 -0400
Message-Id: <20200809151507.C3DCB1E74E58@ary.local>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
In-Reply-To: <B5969C0B-EF25-40CF-BFB4-8E062C90CA24@gmail.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/7DHkGQa-dc9MY8967PkgqeJ8hyg>
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: Sun, 09 Aug 2020 15:15:18 -0000

In article <B5969C0B-EF25-40CF-BFB4-8E062C90CA24@gmail.com> you write:
>I disagree with this approach.
>
>We should ask the RFC Series Editor to consult international experts on technical language and the editors of other major standards
>such as IEEE, ETSI and ITU and report back to us with a recommendation.

I have no idea where one might find international experts on technical
language, if such people even exist.

The IETF really needs to address this problem itself.

R's,.
John