Re: USA dominion: Re: IESG Statement On Oppressive or Exclusionary Language

S Moonesamy <sm+ietf@elandsys.com> Sun, 26 July 2020 16:33 UTC

Return-Path: <sm@elandsys.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 D5F523A0FF9 for <ietf@ietfa.amsl.com>; Sun, 26 Jul 2020 09:33:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.697
X-Spam-Level:
X-Spam-Status: No, score=-1.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.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 G0oxuGlBoEwC for <ietf@ietfa.amsl.com>; Sun, 26 Jul 2020 09:33:50 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id A9B7A3A0FF6 for <ietf@ietf.org>; Sun, 26 Jul 2020 09:33:44 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.47.174]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 06QGXUUE002712 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Jul 2020 09:33:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1595781222; x=1595867622; i=@elandsys.com; bh=qJsRVpAZea84ckcK+AZyR3LigVZnSWGSmhTOdcQXEa4=; h=Date:To:From:Subject:In-Reply-To:References; b=e/rEZ2l6JsPB3007AOo18PlSj9P2GHFs6o2rXcgOzKyxFgdzYKnIKPJqSdbnvwMs9 O7zkMdWIj9h6jLZWlQd60AqITYNLxA3nP9Pjec5rKwC3gbluT2ryf0zeiT5LwGBZo/ oCPPUTKRqXg+odW7yJj//1L93hZ97+SwSIBYLMes=
Message-Id: <6.2.5.6.2.20200726072909.110ce380@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 26 Jul 2020 09:32:27 -0700
To: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: USA dominion: Re: IESG Statement On Oppressive or Exclusionary Language
In-Reply-To: <9bc160ec-a038-b90a-4b93-0b668f9137c1@necom830.hpcl.titech. ac.jp>
References: <35BE966B-63A2-438F-BD61-570E86ED2E1A@strayalpha.com> <297BF899-553D-44DB-AB56-04280F776F7A@employees.org> <6646575A-E6EA-4B4E-AC1B-F8B84B5A1203@strayalpha.com> <20200724225654.GB43465@faui48f.informatik.uni-erlangen.de> <6.2.5.6.2.20200725130205.0bc4e420@elandnews.com> <9bc160ec-a038-b90a-4b93-0b668f9137c1@necom830.hpcl.titech.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nW-k9Uu3nRkTh2jgmurVewiqiqo>
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, 26 Jul 2020 16:33:57 -0000

Hello,
At 05:57 AM 26-07-2020, Masataka Ohta wrote:
>A problem is that, even with US local wordings, "slave" does not
>specifically mean [removed] slaves unless otherwise mentioned from
>the context, which should be the reason why US people, long
>after the era of slavery of [removed], coined and accepted the
>terminologies with "master/slave".
>
>So, I think it's just temporal instability in US to be better
>ignored.

RFC 1034 was written by Mr Mockapetris, ISI, and published in 
1987.  There isn't any occurrence of the word "slave" in that 
technical specification.  The word was introduced in technical 
specifications after that date.  I would not use the word in a 
technical specification as I would have to assess whether the word 
would be considered as derogatory (or injurious) in the jurisdiction 
where I reside.

I would not use the terminology as a figure of speech as there is a 
high probability that it could be considered as offensive nowadays.

The opinions expressed in 2018 were that the terminologies were 
acceptable.  My reading of the latest round of discussions is that 
the opinions have moved to not acceptable.  In my opinion, it was 
influenced by events in the United States [1].  Nowadays, those 
opinions spread quickly to other countries through Facebook or 
Twitter.  It is difficult to ignore that.

Regards,
S. Moonesamy

1. 
https://www.reuters.com/article/us-minneapolis-police-jp-morgan-race-exc/exclusive-jpmorgan-drops-terms-master-slave-from-internal-tech-code-and-materials-idUSKBN2433E4