IETF Logo Mail Archive

Re: IESG Statement On Oppressive or Exclusionary Language

Stewart Bryant <stewart.bryant@gmail.com> Sun, 09 August 2020 15:49 UTC

Return-Path: <stewart.bryant@gmail.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 D35113A0CD0 for <ietf@ietfa.amsl.com>; Sun, 9 Aug 2020 08:49:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, FREEMAIL_FROM=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 (2048-bit key) header.d=gmail.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 k9_5JvIigbIW for <ietf@ietfa.amsl.com>; Sun, 9 Aug 2020 08:49:22 -0700 (PDT)
Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C2143A0B5A for <ietf@ietf.org>; Sun, 9 Aug 2020 08:49:22 -0700 (PDT)
Received: by mail-wm1-x32b.google.com with SMTP id x5so5629468wmi.2 for <ietf@ietf.org>; Sun, 09 Aug 2020 08:49:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YNIYbZzqYwyng6Nz5qvpj52W30g7UTEAbZ+fKF8tLbg=; b=BkXyURRdiBSfyysOW8Nxlc7qO+yOVhl3SUBZaGEkVdM4AcaiCQ7hHyPt9VIwXVkQVx 7YMcJGATDrChY7lWhreXRYyygtQSCwA6GKI44ksghpaLWyy0KKb/gq7qwNZz+mCg4CGc QUkfZ6SEi1tgoVHcP0d1RHvbN1Ru+wYzIoeFHGmbhE7abOV4a6ynQHnQSHgb7P/QQuKC 9YDFgvodEmNc6aAzWvcyqXffDH0Pexo/ZNXjEJhVJ2yS5+tayfOuQMVs1X7UD6Yt2yQ1 uY6OlHOQSuozBnN1iWFau1T6sPGMu3qbTku0JvmZu8q7bRfl2KzrED/YcDH0z4WDN+fU B+oA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YNIYbZzqYwyng6Nz5qvpj52W30g7UTEAbZ+fKF8tLbg=; b=Jbo7QIq5E6Q6o8vx6YeOI0ahSLq8ZLOsHpr9DCGomwqSI3c0aDZK6BMaFwuhoNqP9W Bt0Qj+i8U5pv67S91sNO4Pw2JVNcSowTMvCsB9XGclFGQc4FATsNyJ0ye9x5KizodKsO eH3DtqtF6kf6ijIdgzYgR+hYXMFLX4l9GYQ3+8LsHiZgaPzCjpfa/9CPR95muzsZy0SP jg+LgCEHyJu7C8vIhx5Fxgzx6o8dsFvvbnM5F8RNFWEiGuzWyMwnpsSSsVThqartpoPN 8JB5p1/Tr1OI08+Mmc1geY7BVcPWyi97w6BIPUTfohBfYIaGLXQwkRnNY+bBiRdK0J25 cNGA==
X-Gm-Message-State: AOAM5303EByRznVpw27dd31EWRPD7ESZjUDzsatm7hOjoD/7hNsKc8cH k58a4jDT9AYwCF1TOkkrylo=
X-Google-Smtp-Source: ABdhPJyCfhpGS36ty3WEmwM6jgkv/aIHWoyLbJ+FrP6Fm2PzM7GVOzWU6Y6ipxio131SJUu5cOESbg==
X-Received: by 2002:a1c:e184:: with SMTP id y126mr20408327wmg.141.1596988161142; Sun, 09 Aug 2020 08:49:21 -0700 (PDT)
Received: from [10.3.193.103] ([82.132.184.255]) by smtp.gmail.com with ESMTPSA id z8sm17588935wmf.10.2020.08.09.08.49.20 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 09 Aug 2020 08:49:20 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (1.0)
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
From: Stewart Bryant <stewart.bryant@gmail.com>
X-Mailer: iPhone Mail (16G183)
In-Reply-To: <20200809151507.C3DCB1E74E58@ary.local>
Date: Sun, 09 Aug 2020 16:49:18 +0100
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <5427551B-0521-4CA3-AF8C-9A74961E852E@gmail.com>
References: <20200809151507.C3DCB1E74E58@ary.local>
To: John Levine <johnl@taugh.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Im9ZSBQsZ_ZAiR69P3mPWb4WH4U>
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:49:24 -0000


> On 9 Aug 2020, at 16:15, John Levine <johnl@taugh.com> wrote:
> 
> 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.
> 
We could ask the OED people if they can point us such experts. It is possible that some of the to University English departments could point us in the right direction.

We can and should consult with the editors of the other major SDOs.

Since we apparently have no RFC editor in the pipeline (a more serious problem in my view) we could appoint an interim editor to work on this problem.


> The IETF really needs to address this problem itself.
> 
We have the world leading expertise in the design of Internet protocols, but expertise at such a level on the use of the English language and it’s societal implications is not something we can reasonably claim.

Stewart


> R's,.
> John

v2.23.0 | Report a Bug | By Email