[mpowr] Re: [Solutions] Summary of Discussion on Reforming IETF Quality Control Process

"Joel M. Halpern" <joel@stevecrocker.com> Sat, 10 January 2004 06:50 UTC

Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA12519 for <mpowr-archive@odin.ietf.org>; Sat, 10 Jan 2004 01:50:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AfCwm-0003e6-Gz for mpowr-archive@odin.ietf.org; Sat, 10 Jan 2004 01:50:14 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0A6oCT8014008 for mpowr-archive@odin.ietf.org; Sat, 10 Jan 2004 01:50:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AfCwm-0003dr-D6 for mpowr-web-archive@optimus.ietf.org; Sat, 10 Jan 2004 01:50: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 BAA12511 for <mpowr-web-archive@ietf.org>; Sat, 10 Jan 2004 01:50:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AfCwj-0001rr-00 for mpowr-web-archive@ietf.org; Sat, 10 Jan 2004 01:50:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AfCv0-0001nI-00 for mpowr-web-archive@ietf.org; Sat, 10 Jan 2004 01:48:23 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AfCte-0001h5-00 for mpowr-web-archive@ietf.org; Sat, 10 Jan 2004 01:46:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AfCtg-0003Wa-Ti; Sat, 10 Jan 2004 01:47:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AfCsm-0003VY-3c for mpowr@optimus.ietf.org; Sat, 10 Jan 2004 01:46:04 -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 BAA12384 for <mpowr@ietf.org>; Sat, 10 Jan 2004 01:46:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AfCsi-0001cy-00 for mpowr@ietf.org; Sat, 10 Jan 2004 01:46:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AfCqx-0001Yj-00 for mpowr@ietf.org; Sat, 10 Jan 2004 01:44:12 -0500
Received: from ns.execdsl.net ([208.184.15.238] helo=EXECDSL.COM) by ietf-mx with esmtp (Exim 4.12) id 1AfCpo-0001Ts-00; Sat, 10 Jan 2004 01:43:00 -0500
Received: from [66.95.38.74] (HELO JLaptop.stevecrocker.com) by EXECDSL.COM (CommuniGate Pro SMTP 3.3) with ESMTP id 6063177; Sat, 10 Jan 2004 01:42:52 -0500
Message-Id: <5.1.0.14.0.20040110013737.018ef758@localhost>
X-Sender: joel@stevecrocker.com@localhost
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Sat, 10 Jan 2004 01:42:43 -0500
To: MPowr <mpowr@ietf.org>, icar@ietf.org, solutions@alvestrand.no
From: "Joel M. Halpern" <joel@stevecrocker.com>
In-Reply-To: <Pine.BSF.4.58.0401092229580.93125@measurement-factory.com>
References: <003701c3d737$5b361530$386015ac@dclkempt40> <5.1.0.14.2.20040109203410.04552a28@ms101.mail1.com> <003701c3d737$5b361530$386015ac@dclkempt40>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [mpowr] Re: [Solutions] Summary of Discussion on Reforming IETF Quality Control Process
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

I may be missing something, but the problem I see reading this is that this 
gives the IESG no assistance in deciding which documents it needs to 
review.  There was another proposal which I read to say ~the IESG needs to 
review documents for which there is disagreement about the results of other 
reviews.~  While one can argue about whether that is good or not, it at 
least spells out when the IESG needs to review a document, and when it does 
not need to.
Obviously, if we can lighten the load enough that the IESG has time to 
review more than it needs to, that is great and they should do so.
Equally, some IESG members will review some documents over and above such a 
"requirement", since they will be interested.
But my understanding of one aspect of this discussion is to help replace 
the current ~the IESG must review everything~ with a useful alternative 
review procedure, and a useful definition of which things the IESG needs to 
review.
(Among other things, such a reduction should help enable the necessary IESG 
reviews to occur in a more timely fashion.)
The text below seems to say taht there are no documents the IESG needs to 
review.  While it would be nice to arrive in such a state, I doubt we can 
get there in one jump.

Yours,
Joel M. Halpern

PS: Can we pick one of the three lists for this?

At 10:43 PM 1/9/2004 -0700, Alex Rousskov wrote:
>There should be no "requires full IESG review" flag or state for any
>document. IESG is not a special case when it comes to review. IESG or
>any single AD can submit a review for any document that is up for
>review, at any time. This is no different from any IETF participant
>submitting a review. If IESG feels that a particular document needs
>full IESG review, it is their internal business, invisible and
>unpredictable to others (in general), until they submit a review. In
>general, one does not know a priori whether a document will be
>reviewed by IESG until the IESG submits the review.


_______________________________________________
mpowr mailing list
mpowr@ietf.org
https://www1.ietf.org/mailman/listinfo/mpowr