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

Jacob Uecker <juecker.ietf@gmail.com> Fri, 24 July 2020 23:30 UTC

Return-Path: <juecker.ietf@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 074F23A0B3E for <ietf@ietfa.amsl.com>; Fri, 24 Jul 2020 16:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=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 U1IXaSGskXtm for <ietf@ietfa.amsl.com>; Fri, 24 Jul 2020 16:30:34 -0700 (PDT)
Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) (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 0E8AA3A0B3C for <ietf@ietf.org>; Fri, 24 Jul 2020 16:30:34 -0700 (PDT)
Received: by mail-pg1-x52a.google.com with SMTP id o13so6284581pgf.0 for <ietf@ietf.org>; Fri, 24 Jul 2020 16:30:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=n5XqsiL6upHxF5/BFzaPYDBvBmxz3O0zfUFV1hBX67Y=; b=OHX4nSoPVJJiDfqpp5x6l+xC8m8xOMKV6dmU/60U4Ql02dKNlUKMnu9evUNayegS6Q V6QRDJcIxPp5i9VXBWaD/Hwg0gpBF9CqrkopdDA/Vbl0EoVrntGj6fABiV6oiNuzzhn6 3/Rvk88nI3OSnnggVCbclLsGkMttaTGhXv3I3nkXsjBHQRXiJ17nXc1CyNQq9MG2u7dK 5a6GLZhEgacrEcXQZThKvBb7Yy7l7kcDSe65a+dujwX3/jKPKE042llxPf/PjcvNLX8E qnUAZw++SFNQbmu2rI0pTtNmvcZ7kpfxJetqmuV1MBavXagi/MVF5s9pW3xHU6Uwhjrm YY6g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=n5XqsiL6upHxF5/BFzaPYDBvBmxz3O0zfUFV1hBX67Y=; b=RQ8wJWifNqPzuPkG6hLvjypAiawTFO/MTHcLWhxtFXM176xQVpvEqTLBNcexTkULtX 5oI4Ees+l/EGpmeuzQ2r/PGeK24es3WL4n6Wti6IAHvh5sJ04N1W0o/laEOl3umYq80r VWf9+7Fij6TzSJ/mrqMlr7vbAElHV0h5o+hQxvtH5lMXZBM4ewwxcRNLknS7FWmkDZrW hMVOLkWZQHTI7PL047CDYwHWgSm7X40OBG086DGnRdWcXKbVBqeceBtotj+ZYxSHOkf3 vJqStyeE/MPt99AT6bXkSlcNbm2yBHJ+q21lrGU3xXVKaETxc8jY5a/jPjmZ2thFtv8u xmyg==
X-Gm-Message-State: AOAM530nJleJqVjBFw7ovDAc/Eafk/BIfuNv7nnWs6mNGEhM6kSIWg6H pVVS7y3IaKKzejvQ1ezPDmslK0NevCw=
X-Google-Smtp-Source: ABdhPJwftnJwidS3trz8LgQZif9yI62pxNCbXve69pIaY5qQh/BoNWoU7MCvO0ZLG6XSXKGv3khpcg==
X-Received: by 2002:a62:33c5:: with SMTP id z188mr10868182pfz.180.1595633433401; Fri, 24 Jul 2020 16:30:33 -0700 (PDT)
Received: from [192.168.1.6] (ip68-96-115-4.lv.lv.cox.net. [68.96.115.4]) by smtp.gmail.com with ESMTPSA id y20sm7724939pfo.170.2020.07.24.16.30.32 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 24 Jul 2020 16:30:32 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-C564C44E-812E-43D1-B999-1E667218B126"
Content-Transfer-Encoding: 7bit
From: Jacob Uecker <juecker.ietf@gmail.com>
Mime-Version: 1.0 (1.0)
Subject: Re: USA dominion: Re: IESG Statement On Oppressive or Exclusionary Language
Date: Fri, 24 Jul 2020 16:30:31 -0700
Message-Id: <57D1D29A-001F-449C-B028-0EEFC1E93D93@gmail.com>
References: <CABmDk8=g=nqAGADGuUmL-GmLQQ-kOi5P2mjtbxVN+NhJwxe3mA@mail.gmail.com>
Cc: Toerless Eckert <tte@cs.fau.de>, John Levine <johnl@taugh.com>, "<ietf@ietf.org>" <ietf@ietf.org>
In-Reply-To: <CABmDk8=g=nqAGADGuUmL-GmLQQ-kOi5P2mjtbxVN+NhJwxe3mA@mail.gmail.com>
To: Mary B <mary.h.barnes@gmail.com>
X-Mailer: iPhone Mail (17F80)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gX0nhW46F7AqlZofEblIBcqELeE>
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: Fri, 24 Jul 2020 23:30:37 -0000

+1  

> On Jul 24, 2020, at 4:24 PM, Mary B <mary.h.barnes@gmail.com>
> 
> You might also want to consider that it isn't just a US majority, it's a white male US majority, which is also an issue IMHO.   The same applies for WG chairs etc.  Indeed, I would posit that the lack of diversity when it comes to gender is also a huge issue with the organization.
> 
> Regards,
> Mary. 
> 
>> On Fri, Jul 24, 2020 at 5:57 PM Toerless Eckert <tte@cs.fau.de> wrote:
>> Joe, *:
>> 
>> Here is how i think this whole effort is exclusionary: 
>> 
>> For the mayority of writers and even more so readers of IETF documents,
>> english is not the first language. Even for any non-american native english
>> speaker, i wonder how much they feel that there is a need to update the language
>> used by the IETF for what arguably is primarily a US social problem: Dealing with 
>> a still seemingly not well enough handled history of afro-american racism and slavery. 
>> 
>> This effort of language change if it is then adopted officially in IETF or RFC
>> editor will undoubtedly reconfirm the perception if not reality that the IETF
>> is a strongly USA dominated institution:
>> 
>> - IETF chair lives in USA works for USA company
>> - 12 of 14 IESG members live in the USA and/or work for USA companies.
>> - 10 out of 13 IAB members live in the USA and/or work for USA companies.
>> - Anybody want to take a bet what percentage of WG chairs live in the
>>   USA and/or work for a USA company ?
>> - Any of the other leadership roles ?
>> 
>> While in the past USA leadership was seen as very positive, unfortunately this
>> has changed around the world, and this effort has good chances to also be
>> seen in that light:
>> 
>> In this case, we have a situation where (if i analyze it correctly) not even 
>> the long-term IETF community, but one from outside the IETF brings this USA centric
>> social issue into the IETF, and the USA centric active IETF community is directly
>> jumping on this boat because they confuse whatever might be good for their
>> countries community to be equally good for the supposedly much larger 
>> and supposedly much more diverse and inclusive global IETF community. To me, this
>> is a sign of even stronger USA influence than anything technical we had so far.
>> 
>> IMHO this is NOT going to be perceived well in the worldwide IETF community,
>> instead, this will create more ridicule about bullish USA centric influence
>> and  control of the IETF. 
>> 
>> I for once learned a lot of network/software terminology from german language 
>> books using american terms. For all intent and purpose the mayority of the
>> worldwide IETF community  and even moree so the readers of IETF products (RFCs)
>> uses english ONLY as a technical language in a similar fashion. Why would
>> that community have to care about social issues in the USA in their
>> technical language ? Change english originated technical terms in maybe
>> a hundred foreign language books to match latest IETF documents ?
>> Retrain students all over the world about technical networking terms
>> and having to explain USA history in its wake ? And that going to play positive ??
>> 
>> How about we create an RFC-editor language advisory board: 10 people
>> selected at random from the active community, at most 2 first-language english
>> speakers, at most 2 first-language chinese speaker, at most one first-language
>> speaker for any other language. That would be a good starting point
>> to decide what does and what does not qualify as IETF community relevant
>> RFC language problems.
>> 
>> Otherwise, we could simply replace any english term we do not like as
>> americans with a french term for use in the IETF. They have a long history 
>> of trying to keep their own language freee of english influence, and AFAIK
>> they even have a government oversight board for such terminology, so i am
>> sure they will have a technical terms for anything we need and those
>> terms have been vetted professionally. Might even get lower hotel rates
>> next time in Quebec if we do this ;-)
>> 
>> Cheers
>>     Toerless
>> 
>> On Fri, Jul 24, 2020 at 01:35:37PM -0700, Joseph Touch wrote:
>> > On Jul 24, 2020, at 1:20 PM, Ole Troan <otroan@employees.org> wrote:
>> > > 
>> > > And you think this discussion isn???t exclusionary?
>> > > 
>> > > O. 
>> > 
>> > Just as ???free speech??? cannot include ???speech??? that restricts the speech of others, avoiding exclusionary language cannot avoid excluding those who consider that language appropriate.
>> > 
>> > If that???s what you mean. If not, it would be useful to explain.
>> > 
>> > Joe
>> 
>> -- 
>> ---
>> tte@cs.fau.de
>>