Re: IESG Statement On Oppressive or Exclusionary Language

Barry Leiba <barryleiba@computer.org> Tue, 28 July 2020 17:48 UTC

Return-Path: <barryleiba@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 2690E3A0A83; Tue, 28 Jul 2020 10:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_MSPIKE_H2=-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 zPT96X0ALB_o; Tue, 28 Jul 2020 10:48:25 -0700 (PDT)
Received: from mail-io1-f48.google.com (mail-io1-f48.google.com [209.85.166.48]) (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 56A8A3A0A64; Tue, 28 Jul 2020 10:48:25 -0700 (PDT)
Received: by mail-io1-f48.google.com with SMTP id l17so21658010iok.7; Tue, 28 Jul 2020 10:48:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VxrfU7sMM1cTzukYBbnXdKaoA88JBPx02w/r7mA5Bmw=; b=nySgSLM0FyewIicMDwaIaKoUHfPITeGMdnntU0eg+MIzG75jszKc1GXBEZOfDTf/ME URvd/iRMEHGUayJpyBjQTSl4ScPb950RIHOYj2UW+7SmavpHHYH0I6Piz3zGMcE3Ooi8 vxP5+vKTGv17oS/r0FkjJVT0FINFd4zuLmNwbsnl5zEPObQy6FBauQvxlS8RKnpOQfZW u2xADPXUz9wEPERoSXsvDsvV2yY58k2fOSKjalpbnaP0JWrN2cvErUs84yVgLFrob5m8 7m92g3i2pI/S7aAldrXjQCDySrAkAH+RnMQha1IjmjHIFKO3wA2Wyt/b85gSmuwy5+VR GQdA==
X-Gm-Message-State: AOAM531qH1yA3JjXkWvucNIBK7kfPAzaRf1hNdsrX9wdLxj/lmbYBddc blkfUam0mB8vdCTS9rEW6Ly40UOYhaeJ2/TURViocA==
X-Google-Smtp-Source: ABdhPJzf72gdyCtsp63q2Xjl7pbfVX5YM1cXF7ougwkmifkzeQSoaNTdKEh3VyFlKmYUeVwfFFe5Vh0mFiS7kwUveHg=
X-Received: by 2002:a5e:dd02:: with SMTP id t2mr16695673iop.90.1595958504181; Tue, 28 Jul 2020 10:48:24 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <c18fc227-7da0-1487-a2ae-74de1ac73759@necom830.hpcl.titech.ac.jp>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 28 Jul 2020 13:48:12 -0400
Message-ID: <CALaySJ+UbSP5nJungBae053q7W_VQ-8yx2pr+KP6S+G81_1_VA@mail.gmail.com>
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Cc: IETF Best Practices <ietf@ietf.org>, The IESG <iesg@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_cn0vWb6JzSeOtQZf90bYFIRyAQ>
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: Tue, 28 Jul 2020 17:48:27 -0000

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
>