Re: [mpowr] Mailing List Management
"James Kempf" <kempf@docomolabs-usa.com> Fri, 19 December 2003 21:24 UTC
Received: from optimus.ietf.org ([132.151.1.19])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27761
for <mpowr-archive@odin.ietf.org>; Fri, 19 Dec 2003 16:24:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AXS6V-0003oH-Q3
for mpowr-archive@odin.ietf.org; Fri, 19 Dec 2003 16:24:12 -0500
Received: (from exim@localhost)
by www1.ietf.org (8.12.8/8.12.8/Submit) id hBJLOBV0014636
for mpowr-archive@odin.ietf.org; Fri, 19 Dec 2003 16:24:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AXS6V-0003nt-FS
for mpowr-web-archive@optimus.ietf.org; Fri, 19 Dec 2003 16:24: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 QAA27637
for <mpowr-web-archive@ietf.org>; Fri, 19 Dec 2003 16:24:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1AXS6T-0003GW-00
for mpowr-web-archive@ietf.org; Fri, 19 Dec 2003 16:24:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1AXS6O-0003FC-00
for mpowr-web-archive@ietf.org; Fri, 19 Dec 2003 16:24:09 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
by ietf-mx with esmtp (Exim 4.12) id 1AXS6N-0003F9-00
for mpowr-web-archive@ietf.org; Fri, 19 Dec 2003 16:24:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20)
id 1AXS6O-0003i0-4d; Fri, 19 Dec 2003 16:24:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AXRCP-00028v-Hd
for mpowr@optimus.ietf.org; Fri, 19 Dec 2003 15:26:13 -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 PAA24868
for <mpowr@ietf.org>; Fri, 19 Dec 2003 15:26:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1AXRCO-0000am-00
for mpowr@ietf.org; Fri, 19 Dec 2003 15:26:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1AXRCN-0000af-00
for mpowr@ietf.org; Fri, 19 Dec 2003 15:26:11 -0500
Received: from key1.docomolabs-usa.com
([216.98.102.225] helo=fridge.docomolabs-usa.com ident=fwuser)
by ietf-mx with esmtp (Exim 4.12) id 1AXRCN-0000ac-00
for mpowr@ietf.org; Fri, 19 Dec 2003 15:26:11 -0500
Message-ID: <022501c3c66e$656c3b80$5b6015ac@dclkempt40>
From: "James Kempf" <kempf@docomolabs-usa.com>
To: "Alex Conta" <aconta@txc.com>
Cc: "MPowr" <mpowr@ietf.org>
References: <011901c3c654$24fdc830$5b6015ac@dclkempt40>
<3FE35B1F.2000308@txc.com>
Subject: Re: [mpowr] Mailing List Management
Date: Fri, 19 Dec 2003 12:26:31 -0800
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
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.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Alex,
Sorry for misspelling your name.
> On the other hand, I think IESG should have helped you resolve the
> crisis in the WG by other means. Have you asked for other type of help
> from IESG, other than stopping Email access? This sounds like a typical
> technical conflict resolution problem, for which there is a science and
> professionals, who would be glad to help.
>
With respect to my experience as a WG chair, the problem had nothing to do
with a technical conflict. The participant who was being disruptive was
sending email about how the AD and the co-chairs were mis-managing the WG,
i.e. it was exclusively process comments. At one point, private email was
sent to someone involved in the WG threatening them with physical violence
at an IETF meeting. After this incident, it was difficult to accomplish any
good technical work in the WG.
In this case, there was no need to involve the IESG. Between the AD, the
other co-chair, and myself, we resolved the problem in a different way. We
didn't appeal to the IESG because, as I said, the IESG's track record of
removing people who are disruptive is not particularly good (though I think
they might have acted in this case).
Frankly, after this experience, I have some amount of difficulty
understanding your position. Such unprofessional, uncivilized behavior is
not tolerated in any other professional group or nonprofessional civil
society in general; yet, we routinely tolerate it on IETF mailing lists, if
not perhaps in the most extreme form I've cited here.
I've advanced this proposal (which I agree with Margaret is perhaps more
complex than necessary) in order to meet your and Scott's concerns.
Personally, I believe WG chairs and ADs should have the right to throw
anybody off the list they agree is being disruptive. If anybody thinks they
are being treated unfairly, they can always appeal.
jak
_______________________________________________
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