RE: [mpowr] Mailing List Management

Margaret.Wasserman@nokia.com Tue, 23 December 2003 19:40 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04498 for <mpowr-archive@odin.ietf.org>; Tue, 23 Dec 2003 14:40:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYsO0-0005YF-UK for mpowr-archive@odin.ietf.org; Tue, 23 Dec 2003 14:40:08 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id hBNJe8rj021323 for mpowr-archive@odin.ietf.org; Tue, 23 Dec 2003 14:40:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYsNz-0005Xj-WA for mpowr-web-archive@optimus.ietf.org; Tue, 23 Dec 2003 14:40:08 -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 OAA04469 for <mpowr-web-archive@ietf.org>; Tue, 23 Dec 2003 14:40:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYsNx-0007Td-00 for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 14:40:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYsMr-0007Ka-00 for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 14:38:58 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AYsKx-0006zm-00 for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 14:36:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYsKz-00058h-GC; Tue, 23 Dec 2003 14:37:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AYsKE-00057V-1o for mpowr@optimus.ietf.org; Tue, 23 Dec 2003 14:36:14 -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 OAA03802 for <mpowr@ietf.org>; Tue, 23 Dec 2003 14:36:10 -0500 (EST)
From: Margaret.Wasserman@nokia.com
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AYsKB-0006qZ-00 for mpowr@ietf.org; Tue, 23 Dec 2003 14:36:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AYsHT-0006Jc-00 for mpowr@ietf.org; Tue, 23 Dec 2003 14:33:24 -0500
Received: from mgw-x1.nokia.com ([131.228.20.21]) by ietf-mx with esmtp (Exim 4.12) id 1AYsEi-0005nC-00 for mpowr@ietf.org; Tue, 23 Dec 2003 14:30:32 -0500
Received: from esvir05nok.ntc.nokia.com (esvir05nokt.ntc.nokia.com [172.21.143.37]) by mgw-x1.nokia.com (Switch-2.2.8/Switch-2.2.8) with ESMTP id hBNJUU025161 for <mpowr@ietf.org>; Tue, 23 Dec 2003 21:30:31 +0200 (EET)
Received: from daebh001.NOE.Nokia.com (unverified) by esvir05nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.5) with ESMTP id <T66b167bf16ac158f25a13@esvir05nok.ntc.nokia.com>; Tue, 23 Dec 2003 21:30:30 +0200
Received: from bsebe001.NOE.Nokia.com ([172.19.160.13]) by daebh001.NOE.Nokia.com with Microsoft SMTPSVC(5.0.2195.6747); Tue, 23 Dec 2003 11:30:27 -0800
x-mimeole: Produced By Microsoft Exchange V6.0.6487.1
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [mpowr] Mailing List Management
Date: Tue, 23 Dec 2003 14:30:26 -0500
Message-ID: <E320A8529CF07E4C967ECC2F380B0CF9027E46C4@bsebe001.americas.nokia.com>
Thread-Topic: [mpowr] Mailing List Management
Thread-Index: AcPI+D759d6NtHk4Suiq3gACNec3PQAkZr3Q
To: <john-ietf@jck.com>, <harald@alvestrand.no>, <mpowr@ietf.org>
X-OriginalArrivalTime: 23 Dec 2003 19:30:27.0566 (UTC) FILETIME=[381E68E0:01C3C98B]
Content-Transfer-Encoding: quoted-printable
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.3 required=5.0 tests=NO_REAL_NAME autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi John,

> So, the needed rules here are:
> 
> 	(1) A WG Chair can eject someone from a meeting or
> 	mailing list or take any other reasonable action, if it
> 	is reasonably and sensibly required to prevent or
> 	eliminate disruptive activities so that the WG can get
> 	work done.  In exercising that authority, the WG Chair
> 	is expected to consult as necessary and reflect current
> 	community culture and judgment as to what actions are
> 	appropriate under what types of circumstances.
> 	
> 	(2) Someone who has been ejected from a mailing list or
> 	otherwise subjected to WG Chair discipline has the right
> 	to appeal and has the right to expect a timely review
> 	and response to the first stage appeal to the relevant
> 	AD.  ADs who do not respond to such appeals on a timely
> 	basis are a menace to the smooth and efficient workings
> 	of the IETF and should be swiftly recalled.
> 
> What is interesting about those rules, of course, is that they
> don't require any changes to existing written formal rules and
> procedures, only the application of common sense to those
> rules... and changes to some of our habits and assumptions about
> how we do business.

I don't agree that these rules can be enacted without any changes to 
our written formal rules.

RFC 2418 says:

   As with face-to-face sessions occasionally one or more individuals
   may engage in behavior on a mailing list which disrupts the WG's
   progress.  In these cases the Chair should attempt to discourage the
   behavior by communication directly with the offending individual
   rather than on the open mailing list.  If the behavior persists then
   the Chair must involve the Area Director in the issue.  As a last
   resort and after explicit warnings, the Area Director, with the
   approval of the IESG, may request that the mailing list maintainer
   block the ability of the offending individual to post to the mailing
   list. (If the mailing list software permits this type of operation.)
   Even if this is done, the individual must not be prevented from
   receiving messages posted to the list.  Other methods of mailing list
   control may be considered but must be approved by the AD(s) and the
   IESG.

In other words, it explicitly requires IESG approval to revoke
the posting privileges of a disruptive participant, or to enact 
any other type of mailing list control.

Margaret



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