Re: [mpowr] Mailing List Management

Harald Tveit Alvestrand <harald@alvestrand.no> Sun, 21 December 2003 17:52 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00328 for <mpowr-archive@odin.ietf.org>; Sun, 21 Dec 2003 12:52:16 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AY7k5-0006WH-FJ for mpowr-archive@odin.ietf.org; Sun, 21 Dec 2003 12:51:49 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBLHpn72025055 for mpowr-archive@odin.ietf.org; Sun, 21 Dec 2003 12:51:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AY7k5-0006W2-B3 for mpowr-web-archive@optimus.ietf.org; Sun, 21 Dec 2003 12:51:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00300 for <mpowr-web-archive@ietf.org>; Sun, 21 Dec 2003 12:51:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AY7k3-0004fV-00 for mpowr-web-archive@ietf.org; Sun, 21 Dec 2003 12:51:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AY7jc-0004fB-00 for mpowr-web-archive@ietf.org; Sun, 21 Dec 2003 12:51:21 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AY7jc-0004ey-00 for mpowr-web-archive@ietf.org; Sun, 21 Dec 2003 12:51:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AY7jJ-0006U5-1p; Sun, 21 Dec 2003 12:51:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AY7iU-0006TN-9Y for mpowr@optimus.ietf.org; Sun, 21 Dec 2003 12:50:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00252 for <mpowr@ietf.org>; Sun, 21 Dec 2003 12:50:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AY7iI-0004cs-00 for mpowr@ietf.org; Sun, 21 Dec 2003 12:49:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AY7hr-0004cF-00 for mpowr@ietf.org; Sun, 21 Dec 2003 12:49:32 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx with esmtp (Exim 4.12) id 1AY7hr-0004aU-00 for mpowr@ietf.org; Sun, 21 Dec 2003 12:49:31 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id D822E61AA5; Sun, 21 Dec 2003 18:48:31 +0100 (CET)
Date: Sat, 20 Dec 2003 21:45:17 -0800
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: James Kempf <kempf@docomolabs-usa.com>, MPowr <mpowr@ietf.org>
Subject: Re: [mpowr] Mailing List Management
Message-ID: <383969298.1071956717@localhost>
In-Reply-To: <011901c3c654$24fdc830$5b6015ac@dclkempt40>
References: <011901c3c654$24fdc830$5b6015ac@dclkempt40>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Sender: mpowr-admin@ietf.org
Errors-To: mpowr-admin@ietf.org
X-BeenThere: mpowr@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mpowr>, <mailto:mpowr-request@ietf.org?subject=unsubscribe>
List-Id: Management Positions -- Oversight, Work and Results <mpowr.ietf.org>
List-Post: <mailto:mpowr@ietf.org>
List-Help: <mailto:mpowr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mpowr>, <mailto:mpowr-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,DATE_IN_PAST_12_24 autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

James,

in my opinion Alex Conta and Scott Bradner are wrong.

There are cases where, for the good of the working group, a person should 
have his or her posting privilleges revoked - FAST - as on the order of a 
day or three.

This is NOT a free speech issue - it has to do with the ability of the IETF 
to conduct its work in an open and orderly fashion - BOTH open AND orderly.

For these cases, a simple procedure with 100% clarity on who makes the 
decision is needed - not a "three strikes and then wait another month" 
procedure, as any procedure involving the whole IESG is likely to be.

There are other cases where a person is highly disruptive but you have a 
hard time figuring out why it's disruptive or improper; there are still 
other cases where a valid, rational technical argument gradually descends 
into name-calling and truly improper conduct. There will always be 
borderline cases, and because there will be borderline cases, we need 
procedures for consultation, and we need procedures for appeal and review.

But there are cases where the WG chair needs to have this power, and needs 
to be able to apply it quickly.

The rabble-rousers of the world are free to rabble-rouse wherever they 
want. But no IETF participant should be obliged to listen.

                    Harald


_______________________________________________
mpowr mailing list
mpowr@ietf.org
https://www1.ietf.org/mailman/listinfo/mpowr