Re: IESG Statement On Oppressive or Exclusionary Language

Joel Halpern Direct <jmh.direct@joelhalpern.com> Sun, 09 August 2020 17:16 UTC

Return-Path: <jmh.direct@joelhalpern.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 272403A0D6F for <ietf@ietfa.amsl.com>; Sun, 9 Aug 2020 10:16:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.049
X-Spam-Level:
X-Spam-Status: No, score=-3.049 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, NICE_REPLY_A=-0.949, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 63mAGLa9hz8f for <ietf@ietfa.amsl.com>; Sun, 9 Aug 2020 10:16:37 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1652E3A0D6C for <ietf@ietf.org>; Sun, 9 Aug 2020 10:16:36 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4BPm3S6GNGz6G9s6; Sun, 9 Aug 2020 10:16:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1596993396; bh=Ode5oXHyI4mDyTLhEqCY5vEEwZdSx2alYOVEcDh1Dq0=; h=Subject:To:References:From:Date:In-Reply-To:From; b=aY16Ex76G5Gt+boxS48WbbT+BDy5yE7SxNVLKFT3iEaFciarQoyL8B1XgeJkMXWUt VPAmCM5qtCFNB03pOhU7qYVW45JHttlmERU6AcW9esdK13uypLn/BzbgWy5+oN1164 bqJCnkaflwyIyWQjhUizywDRA/pFxxS2UZGfG3ck=
X-Quarantine-ID: <4_uSpOC8YFNV>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 4BPm3S2lWfz6G8pj; Sun, 9 Aug 2020 10:16:36 -0700 (PDT)
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
References: <5692e18e-afbb-9294-1074-3b81dafe8803@network-heretics.com> <59C4CA26-A1EB-4CF4-B973-BC2BBF53A094@gmail.com> <CAL02cgTZt-9+QWPT1aWXcOgpEwuNV2uHnVi5dGm7V5y_8_U1SQ@mail.gmail.com> <0cceb0f2-b5fe-a194-7ce8-68cc537f9cd1@lounge.org> <CAL02cgTV-cfTPO2wrKz0H2E=FLhagu-qs7fwx6jXeJDH-2cSHA@mail.gmail.com> <20200807171546.GP40202@straasha.imrryr.org> <737B9515-C538-4EEB-8A5D-672987A0FE86@akamai.com> <20200807190716.GQ40202@straasha.imrryr.org> <845bd95e-0d95-a164-40f9-e9c45feed6dc@gmail.com> <6D464C5C-D9CB-47A1-A8BB-CD8CAD21B779@cooperw.in> <B5969C0B-EF25-40CF-BFB4-8E062C90CA24@gmail.com> <90fd8bff-c81c-5518-65c6-b929132a4bdd@comcast.net> <44B55324558FD335BADB4165@PSB> <56fd2677-df6a-8ff2-6093-6e8d42442973@joelhalpern.com> <60160A936BE682CEDE0704E1@PSB> <ae46e43a-e5db-0f57-0b01-6c2c2ff7a1ed@joelhalpern.com> <01DA17AE9467CA40963588C1@PSB>
From: Joel Halpern Direct <jmh.direct@joelhalpern.com>
Message-ID: <c04b89e5-2681-91fb-06e9-8f073eed72d8@joelhalpern.com>
Date: Sun, 09 Aug 2020 13:16:35 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <01DA17AE9467CA40963588C1@PSB>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/btVLWKEC9kY4xeWlB40EFVxRZYg>
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: Sun, 09 Aug 2020 17:16:38 -0000

I believe I agree with you in the sense that if we as a community do not 
have rough consensus that this kind of checking should be done, then ADs 
should not be asking reviewers to perform this kind of checking.  (I 
agree that individuals are always free to look for things.)

Personally, I think it would help us on multiple levels if we could, as 
a community, agree that this kind of checking should be done, and the 
issues should be raised.    Neither you nor I have the right to call the 
rough consensus for the IETF list / community.

Yours,
Joel

On 8/9/2020 1:08 PM, John C Klensin wrote:
> --On Saturday, August 8, 2020 23:56 -0400 "Joel M. Halpern"
> <jmh@joelhalpern.com> wrote:
> 
>> Let me approach the quesiton of what i sneeded slightlhy
>> differently.
>>
>> Do you think the General AD has enough support / authority to
>> ask the gen-art reviewers to look for problematic language?
>> If so, what should she point to as examples of what one might
>> look for?  (The gen-art review team has people with a range of
>> language backgrounds.)
> 
> Joel,
> 
> I'm going to answer a slightly different question.  I still
> believe in the IETF principle that we operate bottom-up.  I have
> come doubt recently that others do, especially as we see
> policies of various sorts developed top-down and out of public
> view and them exposed to the community for "consultation" or
> approval.  I hope the changes are just an aberration due to the
> unusual circumstances of the last six months or so and that our
> processes will soon return to normal but wish I were more
> confident about that.
> 
> So I think anyone in the community has the right to ask anyone,
> including a particular review team or any or all WGs, to look
> for problematic language... and to use whatever examples they
> think are important in making that request.  Those participating
> in that team or WG are, presumably, free to treat it as a
> request -- one that they should consider but are not obligated
> to accept and follow.
> 
> Now, to take that a step further and respond to a question you
> definitely did not ask but that seems to be underlying some
> small bits of this discussion (and a few others that are going
> on): Does the General AD/ iETF Chair (or even the entire IESG)
> have sufficient authority to insist that members of a review
> team do a particular type of review --for language, for
> conformity to the AD's views on some particular technical
> matter, or something else -- or to pick/allow only those people
> on the review team whose views are harmonious with theirs?  No,
> I think that would be an abuse of power, a violation of our
> principles of bottom-up decision making and doing things by
> community consensus, and a serious danger.
> 
>   best,
>     john
>