Re: [mpowr] Mailing List Management
Alex Rousskov <rousskov@measurement-factory.com> Fri, 19 December 2003 18:48 UTC
Received: from optimus.ietf.org ([132.151.1.19])
by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19583
for <mpowr-archive@odin.ietf.org>; Fri, 19 Dec 2003 13:48:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AXPfP-0006EF-FG
for mpowr-archive@odin.ietf.org; Fri, 19 Dec 2003 13:48:06 -0500
Received: (from exim@localhost)
by www1.ietf.org (8.12.8/8.12.8/Submit) id hBJIm3D4023937
for mpowr-archive@odin.ietf.org; Fri, 19 Dec 2003 13:48:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AXPfP-0006E0-9r
for mpowr-web-archive@optimus.ietf.org; Fri, 19 Dec 2003 13:48:03 -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 NAA19544
for <mpowr-web-archive@ietf.org>; Fri, 19 Dec 2003 13:48:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1AXPfN-00046F-00
for mpowr-web-archive@ietf.org; Fri, 19 Dec 2003 13:48:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1AXPfL-00045y-00
for mpowr-web-archive@ietf.org; Fri, 19 Dec 2003 13:48:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
by ietf-mx with esmtp (Exim 4.12) id 1AXPfL-00045u-00
for mpowr-web-archive@ietf.org; Fri, 19 Dec 2003 13:47:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20)
id 1AXPfM-0006DB-UX; Fri, 19 Dec 2003 13:48:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by optimus.ietf.org with esmtp (Exim 4.20) id 1AXPea-0006Cb-7z
for mpowr@optimus.ietf.org; Fri, 19 Dec 2003 13:47:12 -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 NAA19521
for <mpowr@ietf.org>; Fri, 19 Dec 2003 13:47:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12)
id 1AXPeY-00044T-00
for mpowr@ietf.org; Fri, 19 Dec 2003 13:47:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
id 1AXPeW-00044M-00
for mpowr@ietf.org; Fri, 19 Dec 2003 13:47:09 -0500
Received: from measurement-factory.com ([206.168.0.5])
by ietf-mx with esmtp (Exim 4.12) id 1AXPeW-00044I-00
for mpowr@ietf.org; Fri, 19 Dec 2003 13:47:08 -0500
Received: from measurement-factory.com (localhost [127.0.0.1])
by measurement-factory.com (8.12.9/8.12.9) with ESMTP id hBJIksk3030995;
Fri, 19 Dec 2003 11:46:54 -0700 (MST)
(envelope-from rousskov@measurement-factory.com)
Received: (from rousskov@localhost)
by measurement-factory.com (8.12.9/8.12.9/Submit) id hBJIksmK030994;
Fri, 19 Dec 2003 11:46:54 -0700 (MST) (envelope-from rousskov)
Date: Fri, 19 Dec 2003 11:46:54 -0700 (MST)
From: Alex Rousskov <rousskov@measurement-factory.com>
To: James Kempf <kempf@docomolabs-usa.com>
cc: MPowr <mpowr@ietf.org>
Subject: Re: [mpowr] Mailing List Management
In-Reply-To: <011901c3c654$24fdc830$5b6015ac@dclkempt40>
Message-ID: <Pine.BSF.4.53.0312191127010.24835@measurement-factory.com>
References: <011901c3c654$24fdc830$5b6015ac@dclkempt40>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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
On Fri, 19 Dec 2003, James Kempf wrote: > Suppose that in order to join an IETF WG mailing list, a person > would have to agree to a mailing list "Code of Conduct" ... And it > would mean that the mailing list would need to be hosted somewhere > that could support a more elaborate signup procedure than today. I believe the above would be a step in the right direction: having formal IETF membership. From technical point of view, this does not preclude anonymous membership; I am not sure about the legal point of view. This does not imply membership fees, from any point of view. For many automation tools, such as ID publication and review management, formal membership is essential. It is also a shame and a problem that IETF does not seem to know how many informal members it has, even approximately; not to mention their technical background and country of origin. Thus, if the legal burden is low, formal membership (i.e., registration) is a good thing, IMO. However, I would be [pleasantly] surprised if you can get consensus on the formal membership issue. You do not have to call it formal membership, but what your propose is, essentially, formal membership. > Then, when a WG chair believes that a participant is being > disruptive, (s)he would send three email messages privately to the > particpant, cc'ing the AD, with specific evidence, in the form of > emails, posting statistics (for people who are spamming the list), > etc., requesting the participant to cease. If the three email > messages don't work, the WG chair would then discuss the matter with > the AD and, with the AD's approval (sent as an email message to the > WG chair), the chair would send email to the participant that > his/her posting privileges were being revoked Sounds reasonable to me. To protect the innocent better, I would require that the suspect being CCed on all related correspondence with the AD. > for a three month period. This should be decided on a case-by-case basis. The rule should have a maximum suspension period and no minimum. The rule can recommend a 15 day suspension for first time offenders (10 day suspension for children; sorry, could not resist). > The participant could appeal to the IESG if (s)he felt that (s)he > was being treated unfairly. As always. Alex. _______________________________________________ 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