Re: Harassment, abuse, accountability. and IETF mailing lists

Phillip Hallam-Baker <phill@hallambaker.com> Mon, 13 June 2022 23:06 UTC

Return-Path: <hallam@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 B3D2FC15AAF4 for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2022 16:06:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.409
X-Spam-Level:
X-Spam-Status: No, score=-6.409 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N5crMhNle0EA for <ietf@ietfa.amsl.com>; Mon, 13 Jun 2022 16:06:51 -0700 (PDT)
Received: from mail-yw1-f180.google.com (mail-yw1-f180.google.com [209.85.128.180]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F38DFC14CF0A for <ietf@ietf.org>; Mon, 13 Jun 2022 16:06:50 -0700 (PDT)
Received: by mail-yw1-f180.google.com with SMTP id 00721157ae682-30c2f288f13so13099527b3.7 for <ietf@ietf.org>; Mon, 13 Jun 2022 16:06:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=d0oGy2KVo1phtiRPAAm0vPnEDKpkit9FJ6ZNx/tfHPA=; b=U97AFiIUjSRJFyBahaobMC5598DtDnsloIf9QnahSIvN28Zts/uz4By3crct1wFxUT BHhBRjToJpnsSyU8KbnejR3oP5d4OHkEzZq30YC9oJE0f6YWwqma8VS41QdkK6cUcWxu xRQswGR4x8NwkBXemMMKXgcK9Rg+8gjCOhlmvOxlb3gvG049ZfNSTMymbhHlMB5hTzZ4 VYFlUHUQA7LTd1Ye5ha0JXaLoXkM5nI1FXhfe8fQjbUnMze4tu2MrTQOgv9sbIWT0kYI nIoxpY0KUFMG/RQ9nCkJBYz20HzRzYKWSuV1YxDVBE3qKIDr78PTFGmjMZ1V3Ue8D4OE frdg==
X-Gm-Message-State: AJIora8VURaystCXzVD312yE0YpuFgy1XGmWlbhEgsh/5yns8jJKYQ6A tpnzpj74SBsGN5xUDiUJHO+KMTt5Xd+8HuHBp60=
X-Google-Smtp-Source: AGRyM1uJy5wMmYp1dRqhZm9KwCIoJrDz2rZipxiVNbHzKhJ/wAHhWZBuur/6g6YV5FjrgRKkHUC6gjPjXP99fsE4pgw=
X-Received: by 2002:a05:690c:297:b0:30f:b472:5ff1 with SMTP id bf23-20020a05690c029700b0030fb4725ff1mr2401213ywb.31.1655161610048; Mon, 13 Jun 2022 16:06:50 -0700 (PDT)
MIME-Version: 1.0
References: <16C5EC99A155D55344E1F195@PSB> <0325E09B-3B8D-47B5-83B8-ACA5A028B464@episteme.net> <629A3680.9010002@btconnect.com> <b97e7721-ae59-ab49-7f27-b427e2ef7bc6@gmail.com> <3A57F3D797B85E2F0A862687@PSB> <629B4ACB.8010308@btconnect.com> <A62BB706DDC6044CA7676E0B@PSB> <629DB8E5.7070206@btconnect.com> <a0556611-dc43-9280-1ab1-1ae747b21eff@network-heretics.com> <cba4c1b9-772f-8baa-d0fc-c94701747ec0@gmail.com> <C6E2D9FD91539FC17B7AD498@PSB> <8CD09EF0-A825-4539-9B3F-38B881BA4F2D@ietf.org> <6410e897-4a1a-35d7-9564-fe1b9445b2c5@network-heretics.com> <82ACFD06-E4C4-4DB5-A3DE-6543E41F8CB3@ietf.org> <2b247525-b651-1292-940e-fc98c2df84d0@network-heretics.com> <6.2.5.6.2.20220612063104.15cf60b0@elandnews.com> <aaebeec0-3b9b-5821-a3a2-f29259cac5c2@network-heretics.com> <CAHw9_iJGU=msLrfvXtdMhuE8icTaU+AhV1Cw+3hjC=kZkRWYxg@mail.gmail.com> <cbabb17d-b99c-0d1e-966c-d3240068acfe@network-heretics.com> <CAC4RtVA6SNR12vcz2v0VF0X-yh-73aBHufnQyu_66ih=axmyAw@mail.gmail.com> <e60ab74c-4a22-46ef-82f9-2d76fe08965c@network-heretics.com> <CAHBU6itHz5kV-CjueVKQuWrnh_TwL2=GkF4g8s53b8akG+-JHQ@mail.gmail.com>
In-Reply-To: <CAHBU6itHz5kV-CjueVKQuWrnh_TwL2=GkF4g8s53b8akG+-JHQ@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Mon, 13 Jun 2022 19:06:47 -0400
Message-ID: <CAMm+LwiQ58NkNSdJ-nJ5QMqe7ZFV75mkaeJ1HY+e+9+pUQPXcw@mail.gmail.com>
Subject: Re: Harassment, abuse, accountability. and IETF mailing lists
To: Tim Bray <tbray@textuality.com>
Cc: Keith Moore <moore@network-heretics.com>, Barry Leiba <barryleiba@computer.org>, IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d0195605e15c57af"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/y-EQEzbF3Gu3MKqr4qYt9XdxJ4A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
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, 13 Jun 2022 23:06:51 -0000

I am mostly in agreement with Tim except that I have also met the 'reverse
victim' tactic where the person whose general unpleasantness and aggressive
behavior caused the code of conduct to be introduced in the first place
weaponizes it by making a series of challenges.

The issue I think we need to focus on is what are the criteria that
maximize the scope for open discussion without people being shut down by
deliberate rudeness or for that matter unintentional rudeness or people
playing political games.

I know that when I make a proposal and the first four responses are of the
form 'that is already being done by <new proposal>' that this is the result
of someone involved in <new proposal> seeing a potential competitor and
sending an email round to their mates telling them to jump on the thread
quick in the hope of squashing the threat.

I also know that when someone says my proposal is good but it absolutely
MUST be built on top of some scheme that was developed years back but never
made it to deployment that they are trying to make me carry their boat
anchor for them.

I also know that whenever someone says 'we can't spend time considering
alternative design proposals because it is absolutely essential that this
be deployed in 12 months' that the proposed WG is doomed and I can expect
to be the SECDIR reviewer for something pretty similar to what was rejected
on the grounds of insufficient time roughly 8 years later.

But most folk don't know to expect that sort of behavior.




On Mon, Jun 13, 2022 at 1:31 PM Tim Bray <tbray@textuality.com> wrote:

>
> On Mon, Jun 13, 2022 at 10:19 AM Keith Moore <moore@network-heretics.com>
> wrote:
>
>> I am not sure that I agree.   I can certainly see how what you describe
>> could happen.  But the Politeness Police have themselves discouraged
>> participation in IETF, at least in part because some of them were every
>> bit as arrogant and demeaning as your example statement above, and
>> worse, AND they had the backing of the organizational leaders.
>>
>
> What we have is at best anecdata, but I strongly disagree.  I have
> personal experience with wonderful people who have walked away saying some
> variation on "all those pissy greybeards waiting to pounce".  Don't
> personally know anyone who (a) has walked away because of the "politeness
> police" and (b) is regretted.
>
> Be kind. It doesn’t hurt.
>
>
>>