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

Toerless Eckert <tte@cs.fau.de> Sat, 25 July 2020 21:11 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 EB4AC3A0AF1 for <ietf@ietfa.amsl.com>; Sat, 25 Jul 2020 14:11:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=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 0Jj2mI2R9x5A for <ietf@ietfa.amsl.com>; Sat, 25 Jul 2020 14:11:48 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.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 A1ED23A0AEF for <ietf@ietf.org>; Sat, 25 Jul 2020 14:11:48 -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 EB496548047; Sat, 25 Jul 2020 23:11:41 +0200 (CEST)
Received: by faui48f.informatik.uni-erlangen.de (Postfix, from userid 10463) id E2830440043; Sat, 25 Jul 2020 23:11:41 +0200 (CEST)
Date: Sat, 25 Jul 2020 23:11:41 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: Joseph Touch <touch@strayalpha.com>
Cc: "Salz, Rich" <rsalz@akamai.com>, "<ietf@ietf.org>" <ietf@ietf.org>
Subject: Re: USA dominion: Re: IESG Statement On Oppressive or Exclusionary Language
Message-ID: <20200725211141.GK43465@faui48f.informatik.uni-erlangen.de>
References: <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> <20200725023449.GF43465@faui48f.informatik.uni-erlangen.de> <F84FE09E-9AB8-4496-9A7C-B39A15A124F0@akamai.com> <20200725204052.GI43465@faui48f.informatik.uni-erlangen.de> <038653DA-02EF-42CC-B881-CE36E6F874E3@strayalpha.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <038653DA-02EF-42CC-B881-CE36E6F874E3@strayalpha.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zJhEdgAAkAgQnx-4th8Iu3tv54E>
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 21:11:51 -0000

On Sat, Jul 25, 2020 at 01:45:44PM -0700, Joseph Touch wrote:
> 
> 
> > On Jul 25, 2020, at 1:40 PM, Toerless Eckert <tte@cs.fau.de> wrote:
> > 
> > For example, one could create a questionaire about language used in RFCs
> > and pass that to all ISOC chapters for feedback, and then analyze that feedback.
> 
> ISOC chapters have little to nothing to do with RFCs.

What do you mean ? If i join an ISOC chapter, i am not allowed anymore to read RFCs ?

Or have no opinions about what technical words would most likely be desirable
for network engineers in my country (RFC text terms matching other educational material
for example) ? Or whether avoiding specific words isin RFC would be seen as culturally
benefical in my country ?

The IETF community is not the customer (readers of RFCs), even though we are a subset
of it. All i am saying is that if you change the product you should be interested
to understand what the customer thinks. How would you propose to do that ?

Cheers
   Toerless

> They serve a different purpose, as described here:
> https://www.internetsociety.org/chapters/ <https://www.internetsociety.org/chapters/>

> Joe
> 

-- 
---
tte@cs.fau.de