Re: Notification to list from IETF Moderators team

Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp> Wed, 22 March 2023 12:12 UTC

Return-Path: <mohta@necom830.hpcl.titech.ac.jp>
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 5A268C1524B2 for <ietf@ietfa.amsl.com>; Wed, 22 Mar 2023 05:12:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.895
X-Spam-Level:
X-Spam-Status: No, score=-6.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jPJl5k57fuAI for <ietf@ietfa.amsl.com>; Wed, 22 Mar 2023 05:12:23 -0700 (PDT)
Received: from necom830.hpcl.titech.ac.jp (necom830.hpcl.titech.ac.jp [131.112.32.132]) by ietfa.amsl.com (Postfix) with SMTP id 40E52C1522C4 for <ietf@ietf.org>; Wed, 22 Mar 2023 05:12:22 -0700 (PDT)
Received: (qmail 93828 invoked from network); 22 Mar 2023 12:02:16 -0000
Received: from necom830.hpcl.titech.ac.jp (HELO ?127.0.0.1?) (131.112.32.132) by necom830.hpcl.titech.ac.jp with SMTP; 22 Mar 2023 12:02:16 -0000
Message-ID: <bbd64b87-678a-e222-fce2-3e9d936be6ed@necom830.hpcl.titech.ac.jp>
Date: Wed, 22 Mar 2023 21:12:19 +0900
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0
Subject: Re: Notification to list from IETF Moderators team
Content-Language: en-US
To: ietf@ietf.org
References: <4545ee83-1c56-4633-05f0-0576ac297884@ietf.org> <108e89fb-a9b9-e4ae-c217-d51ee1be598f@network-heretics.com> <43e94411-441e-93a1-8496-2f1d0a5af67c@gmail.com> <YwVjnrcbO7uUbXHg@husky> <0683a17d-a8c3-1819-d5ad-0eb8fee2421b@network-heretics.com> <29e213c2-5526-44c5-8e1d-74b24d946f7e@necom830.hpcl.titech.ac.jp> <Y0by/yiCnVxGbkU6@faui48e.informatik.uni-erlangen.de> <c6f11c6e-6f3a-76e9-bdfa-d84d15f3284a@necom830.hpcl.titech.ac.jp>
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
In-Reply-To: <c6f11c6e-6f3a-76e9-bdfa-d84d15f3284a@necom830.hpcl.titech.ac.jp>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BaS6oNvCqoTcBbTiAIYTJWixIHM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <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, 22 Mar 2023 12:12:27 -0000

On 2022/10/13 17:22, I wrote:

> Toerless Eckert wrote:
> 
>> Since the last last time you mention, AFAIK, there has been a lot more 
>> focus
>> on language in the IETF including inclusive language which made every 
>> RFC author
>> more involved in considerations about language by being called out on 
>> it by
>> RFC editor.
> 
> As for difficulties with inclusive language, see, for example:
> 
>      https://mailarchive.ietf.org/arch/msg/ietf/szfzLAbV9EmQ7kmz3HGfaLkLhT0/
> 
> As such, insisting on inclusive language with your own idea
> on "inclusive" is rather a problem to be corrected, not a
> good practice to be followed, I think.

Are there anyone who still think, so called, "inclusive"
language, which, IMHO, actually is against inclusiveness only
to authorize/promote/encourage racial discrimination, is a
good practice to follow?

If not, can we conclude that we must ban the false attempt of
inclusiveness coined by a random idea by a some person who was,
but seemingly/hopefully is not, working for twitter?

I really don't want the Lords of the Rings banned merely
because it features "Gandalf the White".

					Masataka Ohta