Re: IESG Statement On Oppressive or Exclusionary Language

Stewart Bryant <stewart.bryant@gmail.com> Wed, 29 July 2020 10:26 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 1E14D3A07F2; Wed, 29 Jul 2020 03:26:03 -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 d_edfsSTRDrs; Wed, 29 Jul 2020 03:26:00 -0700 (PDT)
Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) (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 9E0853A07EC; Wed, 29 Jul 2020 03:25:59 -0700 (PDT)
Received: by mail-wr1-x430.google.com with SMTP id z18so17551362wrm.12; Wed, 29 Jul 2020 03:25:59 -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=4jchDqNKDMMrIEm2NluPC2ywRuagjrlfh5DnRAb2bZc=; b=EO76NxwUg0TXaJXTgySzzvUxBBjO52KptWr8PWu3VpFNVBq7QxP+FHYpIcXJzTBL95 IHO1ocXkzmf7eNr1Ini1iL/QsUJIppBJCjxSqf/Ba7WZqUoG5xATNTQhZGzZAh/thdA3 n3C4qdO7ayOkTCy9+jAwzlq7w4Gfty5e33sL1zDIuJKC2VIWni9lf0SlmhRdcXHIQHtl iM9dYU0oMrTqttasDexjTS+oJ1+GNBepZzAYdOpvl6NXKI4RKDmJghU+D8ZL13OthXnd hzcUQcpkMLHwzsFyATRrvUNiTRsGLNh5L9hzYzLTRiso773oJef3RO7n68iB/S9rEASb CWFQ==
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=4jchDqNKDMMrIEm2NluPC2ywRuagjrlfh5DnRAb2bZc=; b=fHnOVubOGrPM0zfwq6GGs89RM4sNkn46TAl7rpjS1M4QvneEJ+Vq/8LZ4DQc67C0nD /VmyG2G7VXPV0YrCu/rnPv/6uskDMROzd2XdC4h3ah9+StjfDOtpg53j3kXD6l2DcI3t xQ3rKEwRlna+G4KrOdO0LyM7tCX+uUMN+nMZINW7SN7k2SGRwpZA681Yx9PTp4WTd0dg mnllvRYuV35Xbem7HpkBgvDdE4YXg9mYHjY4qnf1v1ZA6uGRJrggqq2MFwcyDryhDGD2 3qB4+zvHBLlGBiI8NPpEe/JMiAIKgIPJi0R9QQ9Y7rmri/fldbrtBMzZB5SZjbFVchW3 Jyww==
X-Gm-Message-State: AOAM5315zajjo0HXON5wTTh2JoFVIDY9KBCytGrJR1CaPpu/Kumw3eSM v508VlIbZpGr3pDaJLyC2VY=
X-Google-Smtp-Source: ABdhPJzBul/AWPrEUgaqi/5i8tFLgeGErJE7V68NQ1g9lo+pwJBuc/G7VKAZ9CjrRhvBhp0iauz/5Q==
X-Received: by 2002:adf:9ed4:: with SMTP id b20mr29204378wrf.206.1596018358025; Wed, 29 Jul 2020 03:25:58 -0700 (PDT)
Received: from broadband.bt.com ([2a00:23a8:4140:0:f0b6:e890:df1a:d776]) by smtp.gmail.com with ESMTPSA id k126sm4441119wme.17.2020.07.29.03.25.56 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Jul 2020 03:25:56 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
From: Stewart Bryant <stewart.bryant@gmail.com>
In-Reply-To: <CALaySJ+UbSP5nJungBae053q7W_VQ-8yx2pr+KP6S+G81_1_VA@mail.gmail.com>
Date: Wed, 29 Jul 2020 11:25:55 +0100
Cc: Stewart Bryant <stewart.bryant@gmail.com>, Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>, IETF Best Practices <ietf@ietf.org>, The IESG <iesg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <29896C76-F631-4E5A-9F42-CB9CEA08ABF8@gmail.com>
References: <933ce8b4-78a5-76bf-55c3-7c5694faffbb@necom830.hpcl.titech.ac.jp> <267BCA35-3A3F-440B-9F5F-2C818D5AE71A@icloud.com> <e7956fd8-2639-3df6-9539-0dd483cafa25@necom830.hpcl.titech.ac.jp> <34CF64D6-10F3-4F45-B592-FA14C911DB0B@chopps.org> <c18fc227-7da0-1487-a2ae-74de1ac73759@necom830.hpcl.titech.ac.jp> <CALaySJ+UbSP5nJungBae053q7W_VQ-8yx2pr+KP6S+G81_1_VA@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RNm4a7p_kH5mdy35S6fZwql7YbE>
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 10:26:03 -0000

I would let authors express their thoughts as they think best, and leave the decision of what words to rephrase with the RFC Editors.

They are our specialist in the English language, they have good judgement on appropriateness, and they have a good understanding of internal and external continuity of expression.

As to this draft I would drop it as it is really unnecessary given that what I describe is what I think the RFC Editors would do anyway.

Stewart


> On 28 Jul 2020, at 18:48, Barry Leiba <barryleiba@computer.org> wrote:
> 
> Masataka-san, I understand what you're saying, but I'm trying to
> understand the details of your objection and what you would like done
> about it.  Please help me.
> 
> I understand and agree that whether certain words and phrases are or
> aren't offensive is very much a cultural issue.  It's clear that any
> plea that we stop using certain terms will necessarily be culturally
> dependent, and, thus <somewhere>-centric.  When people from the U.S.
> make such requests, they are bound to be U.S.-centric, and others in
> this conversation have given examples of things that might be
> bothersome to people from their cultures.
> 
> What I don't understand, and need to ask, are these:
> 
> - Do you think that, in general, it might be reasonable to avoid using
> certain words and phrases because a significantly large group of
> people find them offensive or exclusionary?  Or do you think that it
> is not reasonable to ask people to do that?
> 
> - How does your answer to the above question lead you into a
> recommendation about what to do with this situation in general?
> 
> - What would you want the IETF community to do with respect to the
> Internet draft in question: To expand it to include other terms,
> making it less U.S.-centric?  To change the explanation to make that
> less U.S.-centric?  To abandon the draft because any version of it
> would be too focused on one culture, and it can't be made inclusive
> enough?  Something else?
> 
> Thanks,
> Barry
> 
> On Fri, Jul 24, 2020 at 5:11 AM Masataka Ohta
> <mohta@necom830.hpcl.titech.ac.jp> wrote:
>> 
>> Christian Hopps wrote:
>> 
>>> The document actually talks to these points with some references.
>> 
>> I'm saying the document and the references are all too
>> much US centric ignoring both the original and established
>> meaning of "slave".
>> 
>> As
>> 
>>        https://www.etymonline.com/word/slave
>> 
>>        originally "Slav"
>> 
>>        Grose's dictionary (1785) has under Negroe "A
>>        black-a-moor; figuratively used for a slave,"
>>        without regard to race.
>> 
>> it should be OK to stop using "Negroe", but not "slave",
>> which are originally for Slav, whites.
>> 
>>                                        Masataka Ohta
>> 
>