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

Toerless Eckert <tte@cs.fau.de> Sat, 25 July 2020 02:34 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 6300A3A1107 for <ietf@ietfa.amsl.com>; Fri, 24 Jul 2020 19:34:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.119
X-Spam-Level:
X-Spam-Status: No, score=-1.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779] autolearn=no 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 4O_YgtzOYheM for <ietf@ietfa.amsl.com>; Fri, 24 Jul 2020 19:34:54 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 732C13A0496 for <ietf@ietf.org>; Fri, 24 Jul 2020 19:34:53 -0700 (PDT)
Received: from faui48f.informatik.uni-erlangen.de (faui48f.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:52]) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTP id 87F5D548440; Sat, 25 Jul 2020 04:34:49 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id 7F367440043; Sat, 25 Jul 2020 04:34:49 +0200 (CEST)
Date: Sat, 25 Jul 2020 04:34:49 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: USA dominion: Re: IESG Statement On Oppressive or Exclusionary Language
Message-ID: <20200725023449.GF43465@faui48f.informatik.uni-erlangen.de>
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> <CABmDk8=g=nqAGADGuUmL-GmLQQ-kOi5P2mjtbxVN+NhJwxe3mA@mail.gmail.com> <20200725001454.GE43465@faui48f.informatik.uni-erlangen.de> <DC4B5029-DA11-4455-9499-68EF3AB71AA9@akamai.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <DC4B5029-DA11-4455-9499-68EF3AB71AA9@akamai.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Co2PX5Vex8cdjKpzdR0MD6bYaUU>
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: Sat, 25 Jul 2020 02:34:56 -0000

On Sat, Jul 25, 2020 at 12:52:43AM +0000, Salz, Rich wrote:
> >    What specifically do you think we should do to have
>     sufficient diversity for deciding on IETF document language evolution ?
> 
> We don't have to "solve" all the problems.  We should address known issues.  And then, when language changes, or another group comes up and says "this is hurtful/eclusionary" we should continue the process.

The question i have is more about who makes the decision. From
what you are saying it sounds as if its fine if just the interested
small set of people who are vocal enough chiming into the issue
should be the ones making the decision. My argument is that that
group has not enough diversity to represent the diversity of the
target audience of RFCs across the globe. I gave examples
of pain points in my prior email.

> Based on your postings, I have come to the conclusion that you seem to think that, ideally, this is a one-time thing:  We fix a few words and then we're done.  I don't see it that way.  We start a process, and address those terms we know about.

I don't know how you think this is what i said. I meant that i
see the risk of this happening because i see the initiative being
brought up by a specific, quite focussed social issue originating
from a single country. As i proposed, i would be happy if we
first agreed on what the goal is, and i proposed one (no feedback
received for that), and i don't think that a predominant USA
group should decide how to make such determinations for the IETF.

> >    What does it say about the self proclaimed inclusiveness goal of the
>     IETF if it does imvolve 70% or more USA centric contributors ?
> 
> I don't know, but that's kind of a leading question. I'll answer similarly: if the first part of the process is done by mostly US contributors, that's could be okay because it is mostly US contributors that have used words we now want to avoid, and who seem to be in the most civil unrest over it. Put another way, "look those folks over there are getting rid of problematic terminology, maybe I can mention some words that hurt"  It is up to the privilege to provide a "safe space" for others.  I speak from experience on that.

I am sure that in this climate the IETF mailing lists are a safe
space for others to chime in in the way you describe it, but
a real safe space would have to be one equally safe for all
reasonable opinions. And then there is the question how
to even best determine the best outcome for the target audience.

Cheers
    toerless