[mpowr] Re: Fwd: I-D ACTION:draft-wasserman-rfc2418-ml-update-00.txt
John C Klensin <john-ietf@jck.com> Wed, 11 February 2004 19:10 UTC
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14818 for <mpowr-archive@odin.ietf.org>; Wed, 11 Feb 2004 14:10:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqzkE-00032K-Sc for mpowr-archive@odin.ietf.org; Wed, 11 Feb 2004 14:09:58 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1BJ9weh011666 for mpowr-archive@odin.ietf.org; Wed, 11 Feb 2004 14:09:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqzkE-000325-Nr for mpowr-web-archive@optimus.ietf.org; Wed, 11 Feb 2004 14:09:58 -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 OAA14770 for <mpowr-web-archive@ietf.org>; Wed, 11 Feb 2004 14:09:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AqzkC-0000C4-00 for mpowr-web-archive@ietf.org; Wed, 11 Feb 2004 14:09:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AqzjJ-00002M-00 for mpowr-web-archive@ietf.org; Wed, 11 Feb 2004 14:09:02 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AqziI-0007i1-00 for mpowr-web-archive@ietf.org; Wed, 11 Feb 2004 14:07:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqziK-0002oZ-D4; Wed, 11 Feb 2004 14:08:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AqzhS-0002aM-IT for mpowr@optimus.ietf.org; Wed, 11 Feb 2004 14:07:06 -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 OAA14583 for <mpowr@ietf.org>; Wed, 11 Feb 2004 14:07:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AqzhQ-0007a8-00 for mpowr@ietf.org; Wed, 11 Feb 2004 14:07:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AqzgX-0007Sb-00 for mpowr@ietf.org; Wed, 11 Feb 2004 14:06:10 -0500
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx with esmtp (Exim 4.12) id 1Aqzfi-0007Kj-00 for mpowr@ietf.org; Wed, 11 Feb 2004 14:05:18 -0500
Received: from [209.187.148.215] (helo=scan.jck.com) by bs.jck.com with esmtp (Exim 4.10) id 1Aqzfi-000ISj-00; Wed, 11 Feb 2004 14:05:18 -0500
Date: Wed, 11 Feb 2004 14:05:18 -0500
From: John C Klensin <john-ietf@jck.com>
To: Margaret Wasserman <margaret@thingmagic.com>
cc: mpowr@ietf.org
Message-ID: <19793531.1076508318@scan.jck.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
Subject: [mpowr] Re: Fwd: I-D ACTION:draft-wasserman-rfc2418-ml-update-00.txt
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
Margaret, I think this summarizes what I have gotten out of the discussions, with one qualification, noted below. I'd love to see this be a candidate for either an immediate IETF Last Call or the procedure outlined in draft-klensin-process-july14-00.txt, since I have no reason to imagine that more debates about charters, or debates within a WG, would tell us anything we don't know already. (1) Qualification/ Substantive Issue: If you are going to be precise here, the last sentence should read something like "Other methods of mailing list control, and longer or additional suspensions, must be approved by the IESG or carried out in accordance with other IESG-approved procedures." This makes two changes, one of which I think is clearly consistent with mailing list discussions. The other is too, although less clearly because there has been less discussion: (i) The intent, as I understand it, is to permit a WG chair to rather quickly suspend posting privileges in an abusive situation and for a short period of time. Even the possibility of attaching a second 30 day suspension to the end of the first one smells like abuse, and was not what seems to be intended. So the WG Chair gets one 30 day suspension as specified, but longer or additional ones need some additional consultation, up through and including application of draft-mrose-ietf-posting-04.txt. (ii) Driven partially by the frustration and thinking that went into the above-cited "process-july15" draft, I note that the mailing list discussions identified a rather large space between "maybe shutting someone out for 30 days is ok" and "shutting someone off forever". I think we need to view that 30 days largely as a "cooling off" period and an opportunity for further consultation about what might happen next, if needed, and under what circumstances. At the same time, I believe that the IESG ought to be able to tailor the "what next" to the circumstances -- which might include giving guidance to the WG Chair about appropriate responses to different actions -- and then delegate authority, either to the Chair, an AD, an IESG-designated committee or subcommittee, or some combination of them that made sense. If we try to figure out those circumstances and rules in advance, we will end up with very long procedural documents that will always be responding to previous battles and wars. (2) The -01 version of this, if there is one, needs spell-checking. (3) The procedural change I'd most like to see --not, in any sense, the one that is the most important, but one of those I find most irritating -- would result in an Internet Draft with two or three pages of substance not ending up nine pages long. I think those 8 1/2 pages are yet another symptom that things have gotten somewhat out of hand. john _______________________________________________ mpowr mailing list mpowr@ietf.org https://www1.ietf.org/mailman/listinfo/mpowr
- [mpowr] Fwd: I-D ACTION:draft-wasserman-rfc2418-m… Margaret Wasserman
- [mpowr] Re: Fwd: I-D ACTION:draft-wasserman-rfc24… John C Klensin
- [mpowr] Re: Fwd: I-D ACTION:draft-wasserman-rfc24… Margaret Wasserman
- [mpowr] Re: Fwd: I-D ACTION:draft-wasserman-rfc24… John C Klensin
- Re: [mpowr] Re: Fwd: I-D ACTION:draft-wasserman-r… Henrik Levkowetz
- [mpowr] Attagirl on draft-wasserman-rfc2418-ml-up… Spencer Dawkins
- Re: [mpowr] Attagirl on draft-wasserman-rfc2418-m… Harald Tveit Alvestrand
- Re: [mpowr] Attagirl on draft-wasserman-rfc2418-m… Spencer Dawkins
- Re: [mpowr] Attagirl on draft-wasserman-rfc2418-m… Harald Tveit Alvestrand