Re: [mpowr] Mailing List Management
Alex Conta <aconta@txc.com> Tue, 23 December 2003 16:35 UTC
Received: from optimus.ietf.org ([132.151.1.19])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26691
for <mpowr-archive@odin.ietf.org>; Tue, 23 Dec 2003 11:35:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AYpV1-00068h-J6
for mpowr-archive@odin.ietf.org; Tue, 23 Dec 2003 11:35:11 -0500
Received: (from exim@localhost)
by www1.ietf.org (8.12.8/8.12.8/Submit) id hBNGZBPB023598
for mpowr-archive@odin.ietf.org; Tue, 23 Dec 2003 11:35:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AYpV1-00068W-CM
for mpowr-web-archive@optimus.ietf.org; Tue, 23 Dec 2003 11:35:11 -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 LAA26630
for <mpowr-web-archive@ietf.org>; Tue, 23 Dec 2003 11:35:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1AYpV0-0004Zh-00
for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 11:35:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1AYpRx-0004S9-00
for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 11:32:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
by ietf-mx with esmtp (Exim 4.12) id 1AYpRx-0004S6-00
for mpowr-web-archive@ietf.org; Tue, 23 Dec 2003 11:32:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20)
id 1AYpRx-000638-8D; Tue, 23 Dec 2003 11:32:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AYpQz-0005zz-Im
for mpowr@optimus.ietf.org; Tue, 23 Dec 2003 11:31:01 -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 LAA26312
for <mpowr@ietf.org>; Tue, 23 Dec 2003 11:30:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1AYpQt-0004J8-01
for mpowr@ietf.org; Tue, 23 Dec 2003 11:30:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1AYpPQ-0004HB-00
for mpowr@ietf.org; Tue, 23 Dec 2003 11:29:25 -0500
Received: from transfire.txc.com ([208.5.237.254] helo=pguin2.txc.com)
by ietf-mx with esmtp (Exim 4.12) id 1AYpPQ-0004H8-00
for mpowr@ietf.org; Tue, 23 Dec 2003 11:29:24 -0500
Received: from txc.com ([172.18.253.131])
by pguin2.txc.com (8.11.2/8.11.2) with ESMTP id hBNGTK013268;
Tue, 23 Dec 2003 11:29:20 -0500
Message-ID: <3FE86D59.8060201@txc.com>
Date: Tue, 23 Dec 2003 11:29:13 -0500
From: Alex Conta <aconta@txc.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.6b) Gecko/20031208
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: James Kempf <kempf@docomolabs-usa.com>, MPowr <mpowr@ietf.org>
Subject: Re: [mpowr] Mailing List Management
References: <011901c3c654$24fdc830$5b6015ac@dclkempt40>
<383969298.1071956717@localhost>
In-Reply-To: <383969298.1071956717@localhost>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature";
micalg=sha1; boundary="------------ms010304050802080006070709"
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.0 required=5.0 tests=none autolearn=no version=2.60
Harald, Harald Tveit Alvestrand wrote: > James, > > in my opinion Alex Conta and Scott Bradner are wrong. I will describe this as a difference in opinion rather than using terms of right and wrong. I think the current rule regarding managing the IETF mailing is wise, and a needed checks and balances mechanism. Here is why: WG chairs are NOT process and people managers ONLY. WG chairs can be a directly interested party in a technical debate, and therefore, they may directly benefit from the power of removing one or more people from the WG mailing list. > > 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. > "Being disruptive to the WG" cannot be measured in absolute terms. If the WG chair is to decide that, and act on it, it may vary from one to another. > 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. > What does "orderly" mean? IETF should be proud of having multi-voice, aggressive, and perhaps sometimes long debates. That's what makes it very different from a "sanitized", one-voice environment. Dictatorial environments are known to be more orderly than democratic ones. > 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. > No problem with clarity of "procedure, and responsibility on decision". > 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. "Improper conduct" is also sort of relative up to a certain point. What is the status of the "IETF code of conduct"? > [...] > But there are cases where the WG chair needs to have this power, and > needs to be able to apply it quickly. > If WG chairs were process and people managers ONLY, I would not have a problem. Replacing a checks and balances mechanism, with a rule of "power to apply it quickly" makes it like a "state of emergency". > The rabble-rousers of the world are free to rabble-rouse wherever they > want. But no IETF participant should be obliged to listen. > For instance, nobody forces you to read my message. If my message is disruptive to you, you could have: - ignore it, and further - configure a filter to send my messages on this thread, on this list, in this WG, etc.... directly to the TRASH folder. Alex > Harald > > _______________________________________________ > 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