Re: IESG Statement On Oppressive or Exclusionary Language

S Moonesamy <sm+ietf@elandsys.com> Mon, 10 August 2020 23:24 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 1FF473A0DE9 for <ietf@ietfa.amsl.com>; Mon, 10 Aug 2020 16:24:37 -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 LI2aelZftjrO for <ietf@ietfa.amsl.com>; Mon, 10 Aug 2020 16:24:35 -0700 (PDT)
Received: from mx.elandsys.com (mx.elandsys.com [162.213.2.210]) by ietfa.amsl.com (Postfix) with ESMTP id 7FA2A3A0DE5 for <ietf@ietf.org>; Mon, 10 Aug 2020 16:24:29 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.115.166.42]) (authenticated bits=0) by mx.elandsys.com (8.15.2/8.14.5) with ESMTPSA id 07ANNuD2015802 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Aug 2020 16:24:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1597101849; x=1597188249; i=@elandsys.com; bh=b/odWiZH3Fe8ILk3y4qOVFf4KBYHVQWgo8zi9Rcktlo=; h=Date:To:From:Subject:In-Reply-To:References; b=lOF/Fui8BitNnL6n4GQw8M+6/k6oOaLZbZD3/9sfftPmtiT6e5sVeWN3S8Me7U0X6 KxaKm9sNIaa5BKxRh8MmU2mYbiGKhcJ62kumJ3MEI12ReSfnlP502n2wvhvX+oZ7Yy snhe0fUOo0UnYSwlWevjXRDxaBxvceEnbv6GVMfA=
Message-Id: <6.2.5.6.2.20200810144545.0a8c50b0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 10 Aug 2020 16:23:34 -0700
To: Toerless Eckert <tte@cs.fau.de>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
In-Reply-To: <20200810112739.GB55080@faui48f.informatik.uni-erlangen.de>
References: <20200809151507.C3DCB1E74E58@ary.local> <5427551B-0521-4CA3-AF8C-9A74961E852E@gmail.com> <aa4292e-79a6-3df4-9bc3-18558ba2c190@taugh.com> <6AC5DDA2-2C4E-4B74-B4F3-6B9E94D198B5@tzi.org> <20200809171326.GA28320@faui48f.informatik.uni-erlangen.de> <6.2.5.6.2.20200809110135.11057460@elandnews.com> <20200810112739.GB55080@faui48f.informatik.uni-erlangen.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ft8FHS1ymzmetPEpWM30yCR3qRw>
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: Mon, 10 Aug 2020 23:24:37 -0000

Hi Toerless,
At 04:27 AM 10-08-2020, Toerless Eckert wrote:
>I was primarily thinking about the the fact that the whole community should
>be able to claim to have a say in the policies, eve if they are non-native
>english speaker.
>
>I fully agree that the execution of the policies through just current
>feedback to last-call mailing list would just result in randomn subsets of
>the community getting involved, and primarily native english speakers.
>
>Hence i think the policy should be to
>ensure that there is a neutral, community selected set of language experts
>that executive the community desired policy. I was recommending a nomcom
>style election process for them as one possible way to achieve this. I
>could perfectly think of pairs of native english speakers in the community
>that would cancel each others extreme views of lanugage out, thinking it
>could result in good compromise language....

On reading your reply I was reminded of a recommendation (made 
several years ago) to get more non-native English-speaking people in 
one of the review teams.  It was probably not implemented for unknown 
reasons.  The language experts are actually the people within the RFC 
Editor Function (it is not the RSE who does that work).

In theory, the whole community has a say in policies.  That is not 
how it worked in practice.  I don't know whether the idea which you 
proposed would work as I am not involved in execution.

>IMHO not much different from what i was saying. I just took the means of

Yes.

>gaming the process also into account. Aka: selective aggregation of
>received opinions from the list, moving decisions to different forums than
>email where the weight of pro/con would be known different, etc. pp.

It is up to the IESG to decide about the above.

Regards,
S. Moonesamy