Re: IESG Statement On Oppressive or Exclusionary Language

John C Klensin <john-ietf@jck.com> Sun, 09 August 2020 17:08 UTC

Return-Path: <john-ietf@jck.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 E36203A0D63 for <ietf@ietfa.amsl.com>; Sun, 9 Aug 2020 10:08:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 DGgOt6Ul0keS for <ietf@ietfa.amsl.com>; Sun, 9 Aug 2020 10:08:33 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A61FD3A0D61 for <ietf@ietf.org>; Sun, 9 Aug 2020 10:08:33 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1k4ooB-000CNN-MK; Sun, 09 Aug 2020 13:08:31 -0400
Date: Sun, 09 Aug 2020 13:08:25 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, ietf@ietf.org
Subject: Re: IESG Statement On Oppressive or Exclusionary Language
Message-ID: <01DA17AE9467CA40963588C1@PSB>
In-Reply-To: <ae46e43a-e5db-0f57-0b01-6c2c2ff7a1ed@joelhalpern.com>
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>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Be6-1PJl5ZQb-P0nfeP5oJ5WiVc>
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:08:35 -0000

--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