Re: Describing which behavior is appropriate or not (was: Last Call: <draft-eggert-bcp45bis-06.txt> (IETF Discussion List Charter) to Best Current Practice)

S Moonesamy <sm+ietf@elandsys.com> Fri, 05 November 2021 18:00 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 BC1303A1323 for <ietf@ietfa.amsl.com>; Fri, 5 Nov 2021 11:00:09 -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 M-lUpq1wKkU2 for <ietf@ietfa.amsl.com>; Fri, 5 Nov 2021 11:00:05 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 392363A1300 for <ietf@ietf.org>; Fri, 5 Nov 2021 11:00:05 -0700 (PDT)
Received: from DESKTOP-K6V9C2L.elandsys.com ([102.116.86.51]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id 1A5600lv006944 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Nov 2021 23:00:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1636092012; x=1636178412; i=@elandsys.com; bh=r1H+zZ1grtOZLna86V5Z/s3HbQqqI22V2c3RO6Je81g=; h=Date:To:From:Subject:In-Reply-To:References; b=0pY+jylX3eO8yRjV7+m3FPqh+S4fVjU+DJNuOsZcHMYollYi6mOguDnc20OiMdNUo hhEpmBINZeDDSA0Bp92iZwEttjYIg5/whxRBJXh/SY1UXu9sA0BecG+68sBHCsWgc6 dxKf9YZquqkILxmDc8J3uokgipj7EqgBC3hE+26U=
Message-Id: <6.2.5.6.2.20211104212116.0d122290@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 04 Nov 2021 22:36:57 -0700
To: Bron Gondwana <brong@fastmailteam.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Describing which behavior is appropriate or not (was: Last Call: <draft-eggert-bcp45bis-06.txt> (IETF Discussion List Charter) to Best Current Practice)
In-Reply-To: <265608bb-9d71-42ff-a56a-4e8ee5174da8@dogfood.fastmail.com>
References: <163465875866.13316.15860075014903480611@ietfa.amsl.com> <EA85619D-83D6-409B-AAE7-C13850B18BA0@yahoo.co.uk> <CALaySJKeHDr7EJy4hf5GyS9W0PwpQ0C05TGtS4Gc_ihEFeQtsA@mail.gmail.com> <34ec2302-edc3-e180-be00-4d7200372d5f@network-heretics.com> <6.2.5.6.2.20211030023629.075c8550@elandnews.com> <47db1859-8201-9f37-0efd-aa09f4b1379b@network-heretics.com> <0F85A716-1371-4222-9DAE-23CCBD6E5382@ietf.org> <2bbef9bf-04b7-1862-5334-55aa1ee2ae43@cs.tcd.ie> <CAMm+LwiWaPbe59NE1qtbZ0uc-_NqCCA2=ReciJokt53-RoHQLA@mail.gmail.com> <a4fbed09-258d-5e80-5fa1-c7b9851bac3d@network-heretics.com> <46d3c3ed-8e92-4a35-a546-a6c8bdf0bbee@dogfood.fastmail.com> <6.2.5.6.2.20211104154153.15771868@elandnews.com> <265608bb-9d71-42ff-a56a-4e8ee5174da8@dogfood.fastmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/F5NbsArHM0kVHY0x8WFYc8UWSGY>
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, 05 Nov 2021 18:00:11 -0000

Hi Bron,
At 05:05 PM 04-11-2021, Bron Gondwana wrote:
>There is another issue with asking for discussions to slow down, 
>which is that mailing lists have people from many different 
>timezones and with other things going on in their lives.  It's quite 
>unfair for those who aren't awake at the time for the conversation 
>to move on so fast that they don't get a chance to have any input.

Yes.

>So it's quite reasonable to say "you're allowed to send up to three 
>messages per day and then back off and let somebody else 
>speak".  This is more obvious in an in-person meeting, where it's 
>pretty clear if a couple of people are monopolising the room and not 
>giving anybody else a chance to speak.

It would be difficult to enforce a message limit rule on a working 
group mailing list.

>Likewise, if a couple of people are yelling at each other in an 
>in-person meeting, the body language of everybody else makes it 
>quite clear that they are getting out of line - but a similar 
>escalation of emotionality on a mailing list doesn't have that 
>real-time dampener effect of the audience feedback you get in a real 
>room - so a more explicit "let's take a pause, go away and think 
>about what's important here" does need to happen.

The yelling is risky (please see RFC 7776).

>The problem, and I think you identify it well here, is when that 
>"let's take a pause" is used with an underlying "and hopefully 
>you'll just go away because I don't like the point you're trying to make".
>
>Using a pause as a way to make people go away is not cool - but 
>using it to stop somebody saying the same thing over and over, 
>forcefully, and not waiting for others (who might not be awake or 
>paying attention right now) to have a chance to contribute to the 
>conversation first - that's reasonable.  Conversations shouldn't be 
>dominated by those who have the time to write a lot of email at all 
>hours of the day.

The purpose of the pause is to give everyone enough time to read the 
"Note Well".  I would  not use it to prevent someone from repeating 
his/her arguments or to make people go away.

The last sentence (quoted above) is related to the breath of 
consensus.  A process dominated by a few persons or companies is not 
a consensus-based process.

Regards,
S. Moonesamy