Re: [mpowr] Mailing List Management
John C Klensin <john-ietf@jck.com> Mon, 29 December 2003 22:04 UTC
Received: from optimus.ietf.org ([132.151.1.19])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14409
for <mpowr-archive@odin.ietf.org>; Mon, 29 Dec 2003 17:04:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1Ab5UA-0002P5-Dx
for mpowr-archive@odin.ietf.org; Mon, 29 Dec 2003 17:03:39 -0500
Received: (from exim@localhost)
by www1.ietf.org (8.12.8/8.12.8/Submit) id hBTM3cuR009239
for mpowr-archive@odin.ietf.org; Mon, 29 Dec 2003 17:03:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1Ab5UA-0002Ow-7Q
for mpowr-web-archive@optimus.ietf.org; Mon, 29 Dec 2003 17:03:38 -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 RAA14398
for <mpowr-web-archive@ietf.org>; Mon, 29 Dec 2003 17:03:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1Ab5Tt-00073y-00
for mpowr-web-archive@ietf.org; Mon, 29 Dec 2003 17:03:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1Ab5PM-0006vs-00
for mpowr-web-archive@ietf.org; Mon, 29 Dec 2003 16:58:41 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
by ietf-mx with esmtp (Exim 4.12) id 1Ab5L9-0006nR-00
for mpowr-web-archive@ietf.org; Mon, 29 Dec 2003 16:54:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20)
id 1Ab5Kr-00024I-4J; Mon, 29 Dec 2003 16:54:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1Ab5KD-000240-B2
for mpowr@optimus.ietf.org; Mon, 29 Dec 2003 16:53:21 -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 QAA14142
for <mpowr@ietf.org>; Mon, 29 Dec 2003 16:53:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1Ab5K1-0006kz-00
for mpowr@ietf.org; Mon, 29 Dec 2003 16:53:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1Ab5GI-0006ep-00
for mpowr@ietf.org; Mon, 29 Dec 2003 16:49:18 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com)
by ietf-mx with esmtp (Exim 4.12) id 1Ab5Cj-0006Zp-00
for mpowr@ietf.org; Mon, 29 Dec 2003 16:45:37 -0500
Received: from [209.187.148.215] (helo=scan.jck.com)
by bs.jck.com with esmtp (Exim 4.10)
id 1Ab5Ce-0002Tg-00; Mon, 29 Dec 2003 16:45:32 -0500
Date: Mon, 29 Dec 2003 16:45:32 -0500
From: John C Klensin <john-ietf@jck.com>
To: Alex Rousskov <rousskov@measurement-factory.com>,
Harald Tveit Alvestrand <harald@alvestrand.no>
cc: MPowr <mpowr@ietf.org>
Subject: Re: [mpowr] Mailing List Management
Message-ID: <78624766.1072716332@scan.jck.com>
In-Reply-To: <Pine.BSF.4.53.0312291140100.64996@measurement-factory.com>
References: <011901c3c654$24fdc830$5b6015ac@dclkempt40>
<383969298.1071956717@localhost> <3FE86D59.8060201@txc.com>
<Pine.BSF.4.53.0312230933510.47938@measurement-factory.com>
<2ca901c3c97b$347b1db0$5b6015ac@dclkempt40>
<Pine.BSF.4.53.0312231037030.47938@measurement-factory.com>
<2ccf01c3c97d$b5993ec0$5b6015ac@dclkempt40>
<Pine.BSF.4.53.0312231117340.47938@measurement-factory.com>
<2d7d01c3c987$cfa411f0$5b6015ac@dclkempt40>
<Pine.BSF.4.53.0312231353320.47938@measurement-factory.com>
<902909174.1072475663@localhost>
<Pine.BSF.4.53.0312291140100.64996@measurement-factory.com>
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.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
--On Monday, 29 December, 2003 11:47 -0700 Alex Rousskov <rousskov@measurement-factory.com> wrote: > I suspect that once/if we have easier banning rules, more > people will feel compelled to circumvent them. In fact, even > with the existing rules, IETF participants have faked e-mail, > subscribed to the list with more than one name, and done other > terrible things (as privately confirmed by a senior IETFer who > was working on formalizing the banning process). > > IMO, this means that "easy" rules should be nearly perfect or > should not be. Alex, I can't imagine why you think this follows. In many organizations, and in the IETF in other areas than mailing list management, it is the hard/rigid rules that inspire people to see if they can game them. It is the very specific rules that encourage people to do slightly outrageous things, safe in the knowledge that they can claim unfairness if those things violate the spirit, but not the letter, of the rules. By contrast, whatever the other merits of the idea, "the WG chair can kick someone off a list, at least for a while, for being --in that person's opinion-- disruptive or generally irritating" isn't going to encourage rule-circumvention as an end in itself, if only because that would certainly be "generally irritating". Now, if you had said "if we start kicking people off lists regularly and in large quantities, that would encourage circumvention", I'd probably agree... but suggest that would demonstrate that we have other problems which it would be good to get on the table. The bottom line, it seems to me, is that we need to function, as Dave Crocker has been pointing out (I hope I've correctly understood him), as a collaborative community. No amount of rule-making is going to cause either a sense of collaboration or a sense of community to happen. If we can't keep (or recover) that sense, then we need a rather different set of rules and structures, to the point that debates about mailing list participation is a waste of time. Within such a community, it seems quite rational to me to tell WG Chairs that they have lead responsibility for WG progress. If something or someone is interfering with that progress --including disruptions on mailing lists-- then they should be encouraged to stop it and, if necessary, pushed out of the way. Should the AD be fully informed about such an action? Of course. Should it be appealable? Even more obviously. But the right way to deal with problems of these sorts _within a community_ is to catch them earlier and push back (which, IMO, should include involving the whole WG in a "shunning" process when that seems useful), not to try to solve them by creating ever-more-rigid and complex procedures. Fewer formal procedures, more exercise of good sense, more unambiguous negative reinforcement for failure to exercise good sense.... john _______________________________________________ mpowr mailing list mpowr@ietf.org https://www1.ietf.org/mailman/listinfo/mpowr
- [mpowr] Mailing List Management James Kempf
- RE: [mpowr] Mailing List Management Margaret.Wasserman
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management Alex Conta
- Re: [mpowr] Mailing List Management James Kempf
- Re: [mpowr] Mailing List Management Alex Conta
- RE: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management Spencer Dawkins
- Re: [mpowr] Mailing List Management Harald Tveit Alvestrand
- Re: [mpowr] Mailing List Management John C Klensin
- Re: [mpowr] Mailing List Management Alex Conta
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management Alex Conta
- Re: [mpowr] Mailing List Management James Kempf
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management James Kempf
- Re: [mpowr] Mailing List Management Melinda Shore
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management James Kempf
- RE: [mpowr] Mailing List Management Margaret.Wasserman
- RE: [mpowr] Mailing List Management Margaret.Wasserman
- RE: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management James Kempf
- RE: [mpowr] Mailing List Management John C Klensin
- Re: [mpowr] Mailing List Management Spencer Dawkins
- RE: [mpowr] Mailing List Management Margaret.Wasserman
- Re: [mpowr] Mailing List Management Alex Conta
- Re: [mpowr] Mailing List Management Alex Conta
- Re: [mpowr] Mailing List Management Spencer Dawkins
- RE: [mpowr] Mailing List Management John C Klensin
- RFC Editor doc approvals (RE: [mpowr] Mailing Lis… Harald Tveit Alvestrand
- Re: RFC Editor doc approvals (RE: [mpowr] Mailing… John C Klensin
- Re: RFC Editor doc approvals (RE: [mpowr] Mailing… Harald Tveit Alvestrand
- Re: RFC Editor doc approvals (RE: [mpowr] Mailing… Dave Crocker
- Re: [mpowr] Mailing List Management Harald Tveit Alvestrand
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management Harald Tveit Alvestrand
- Re: [mpowr] Mailing List Management Alex Rousskov
- Re: [mpowr] Mailing List Management John C Klensin
- Re: Re: [mpowr] Mailing List Management Dave Crocker
- Re: [mpowr] Mailing List Management Alex Rousskov