Re: Terminology discussion threads

Benjamin Kaduk <kaduk@mit.edu> Fri, 14 August 2020 17:42 UTC

Return-Path: <kaduk@mit.edu>
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 DFAC33A100E for <ietf@ietfa.amsl.com>; Fri, 14 Aug 2020 10:42:54 -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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 HN6KZOodaZKp for <ietf@ietfa.amsl.com>; Fri, 14 Aug 2020 10:42:53 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 C4B813A0FF3 for <ietf@ietf.org>; Fri, 14 Aug 2020 10:42:53 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 07EHglq1017177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 14 Aug 2020 13:42:50 -0400
Date: Fri, 14 Aug 2020 10:42:47 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Christian Huitema <huitema@huitema.net>
Cc: ietf <ietf@ietf.org>
Subject: Re: Terminology discussion threads
Message-ID: <20200814174247.GH92412@kduck.mit.edu>
References: <6AA0BCBB-D95B-4036-B94D-5E79E7B94D75@ietf.org> <F15E387D-9FDC-4A76-8002-78B85F6D16BE@nohats.ca> <CABcZeBNitWbdPO4Y2WfCzjy10Z+s27px6cGT1uRHmtGHa5iX+Q@mail.gmail.com> <ed227fd5-3277-d7a9-f93d-b259944009d6@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <ed227fd5-3277-d7a9-f93d-b259944009d6@huitema.net>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/T5PjcWEpt7Jwe3m5cHBHLSkS_Ao>
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: Fri, 14 Aug 2020 17:42:55 -0000

On Fri, Aug 14, 2020 at 10:30:14AM -0700, Christian Huitema wrote:
> 
> On 8/14/2020 9:44 AM, Eric Rescorla wrote:
> > Thanks Paul. Well, said.
> >
> > Despite the long history of the IETF discussion list being awful, I've
> > felt an obligation to stay on it. However, it has now become so bad
> > that I can longer do so.
> >
> > I would like to thank the IESG for creating the last call list so
> > that it is still possible to participate in the business of the IETF
> > without being part of this toxic environment. I'll see you there
> > and in the WGs.
> 
> There is something systemic here. We see that behavior too many times. I
> was at the receiving end of similar abuses during the RFC-ED discussions
> last year and I feel the pain for Alissa, but there are many more
> examples. The IETF list functions as some kind of general assembly, but
> without any rules of order. The loudest voices dominate the stream and
> skew the consensus, which encourages a loudest-voice behavior and
> discourages consensus building.
> 
> The question is, what to do?

The IETF way would seem to be to write up several drafts with various
proposals and solicit comments.  Options could include:

- just shut it down
- rate-limit all posters
- create a new role specifically tasked with deescalation and
  consensus-building
- your idea here

-Ben