Re: [mpowr] Re: Getting Bad Ideas to Fail Early
Alex Rousskov <rousskov@measurement-factory.com> Tue, 13 January 2004 20:56 UTC
Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12550 for <mpowr-archive@odin.ietf.org>; Tue, 13 Jan 2004 15:56:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgVaK-0002eJ-RF for mpowr-archive@odin.ietf.org; Tue, 13 Jan 2004 15:56:25 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0DKuOSv010182 for mpowr-archive@odin.ietf.org; Tue, 13 Jan 2004 15:56:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgVaJ-0002e4-9X for mpowr-web-archive@optimus.ietf.org; Tue, 13 Jan 2004 15:56:24 -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 PAA12510 for <mpowr-web-archive@ietf.org>; Tue, 13 Jan 2004 15:56:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AgVaH-0004Yi-00 for mpowr-web-archive@ietf.org; Tue, 13 Jan 2004 15:56:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AgVYQ-0004VG-00 for mpowr-web-archive@ietf.org; Tue, 13 Jan 2004 15:54:27 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 1AgVX3-0004T5-00 for mpowr-web-archive@ietf.org; Tue, 13 Jan 2004 15:53:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgVX4-0002NA-Kd; Tue, 13 Jan 2004 15:53:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AgVWT-0002Li-5f for mpowr@optimus.ietf.org; Tue, 13 Jan 2004 15:52:25 -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 PAA12383 for <mpowr@ietf.org>; Tue, 13 Jan 2004 15:52:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AgVWR-0004RM-00 for mpowr@ietf.org; Tue, 13 Jan 2004 15:52:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AgVUX-0004Os-00 for mpowr@ietf.org; Tue, 13 Jan 2004 15:50:25 -0500
Received: from measurement-factory.com ([206.168.0.5]) by ietf-mx with esmtp (Exim 4.12) id 1AgVTX-0004NC-00 for mpowr@ietf.org; Tue, 13 Jan 2004 15:49:23 -0500
Received: from measurement-factory.com (localhost [127.0.0.1]) by measurement-factory.com (8.12.9/8.12.9) with ESMTP id i0DKnIk3080204; Tue, 13 Jan 2004 13:49:18 -0700 (MST) (envelope-from rousskov@measurement-factory.com)
Received: (from rousskov@localhost) by measurement-factory.com (8.12.9/8.12.9/Submit) id i0DKnIRW080203; Tue, 13 Jan 2004 13:49:18 -0700 (MST) (envelope-from rousskov)
Date: Tue, 13 Jan 2004 13:49:18 -0700
From: Alex Rousskov <rousskov@measurement-factory.com>
To: "David Partain (LI/EAB)" <david.partain@ericsson.com>
cc: mpowr@ietf.org
Subject: Re: [mpowr] Re: Getting Bad Ideas to Fail Early
In-Reply-To: <200401131136.03482.david.partain@ericsson.com>
Message-ID: <Pine.BSF.4.58.0401131223240.67107@measurement-factory.com>
References: <020601c3d6fe$9a5513d0$606015ac@dclkempt40> <006401c3d8a5$25f4ceb0$606015ac@dclkempt40> <Pine.BSF.4.58.0401121520270.15125@measurement-factory.com> <200401131136.03482.david.partain@ericsson.com>
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=AWL autolearn=no version=2.60
On Tue, 13 Jan 2004, David Partain (LI/EAB) wrote: > Who will a working group listen to? From process point of view, the working group does not have to listen to any reviewer. They can, technically, mark each submitted review with "we disagree" and let IESG resolve all the conflicts. > They currently must listen to the IESG. Is the IETF willing to > invest reviewers with similar weight? IETF should be willing and able to design exit criteria that allow some documents to get published without IESG involvement. This does not assign same weight to reviewers as to IESG, but it does assign some weight. In other words, reviewers can "clear" a document (if all reviewers and the WG agrees and there is sufficient coverage). However, reviewers cannot kill the document. Only IESG can. > Where are these fabled reviewers? Does nomcom have to find > them? Do they volunteer and go through a screening process? Can > they be "fired"? This is where proposals differ a lot. I advocate an open pool of volunteers without a special screening process, but with "trusted by AD", "trusted by IESG" or similar flags that are assigned to _some_ fabled reviewers by ADs, IESG, etc. > What do we do if the WG refuses to acknowledge that an idea is > "bad" and forges ahead? Wait for IESG to decide. It would be nice to design some procedure for IESG to decide sooner (early) rather than at PS stage. > Won't that likely mean it'll just get bounced back by the IESG? Yes, it is likely. However, we can only have a single vetoing entity for each document. Having two vetoing entities (one for each document category or whatever) seems too complicated to me. So IESG remains the final conflict resolution entity. > What role do(es) the chair(s) have in all of this? Are they simply > the messenger between the reviewers and the working group? The > advocate of the consensus decision? The chair has no special role in this process, IMO. I do not see a need for messenger here. If there is a human messenger, we need to care about the message integrity and delivery. Instead, each document has a single point of contact: a dedicated WG e-mail address (or author's address for individual submissions). Notification of submitted reviews or any status changes are automatically sent to that address. > To reiterate: I think we need this. I just don't know if we (the > IETF) are willing to do what it seems to imply -- give someone > besides the IESG veto power. I do not think review implies that reviewer has a veto power. A reviewer is an analyst or an advisor. A reviewer does not have to be a decision maker. Alex. _______________________________________________ mpowr mailing list mpowr@ietf.org https://www1.ietf.org/mailman/listinfo/mpowr
- Re: [mpowr] SUMMARY: Mailing List Management Disc… David Partain (LI/EAB)
- [mpowr] SUMMARY: Mailing List Management Discussi… Margaret Wasserman
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Pekka Savola
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Joel M. Halpern
- Re: [mpowr] SUMMARY: Mailing List Management Disc… David Meyer
- RE: [mpowr] SUMMARY: Mailing List Management Disc… Robert Snively
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Rousskov
- Re: [mpowr] SUMMARY: Mailing List Management Disc… David Meyer
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Margaret Wasserman
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Pekka Savola
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Rousskov
- Re: [mpowr] SUMMARY: Mailing List Management Disc… David Meyer
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Rousskov
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Rousskov
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Rousskov
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Rousskov
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Melinda Shore
- [mpowr] Gauging consensus during disruptions Alex Rousskov
- [mpowr] Re: Gauging consensus during disruptions Melinda Shore
- Re: [mpowr] Re: Gauging consensus during disrupti… Dave Crocker
- [mpowr] Re: Gauging consensus during disruptions Alex Rousskov
- [mpowr] Re: Gauging consensus during disruptions James Kempf
- [mpowr] Experiment design Harald Tveit Alvestrand
- Re: [mpowr] Experiment design Alex Rousskov
- [mpowr] Re: Experiment design Pekka Savola
- clarifications Re: [mpowr] SUMMARY: Mailing List … Alex Conta
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Conta
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Margaret Wasserman
- Re: [mpowr] Re: Gauging consensus during disrupti… Alex Conta
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Conta
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Conta
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early Eric Rosen
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Spencer Dawkins
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Margaret Wasserman
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Margaret Wasserman
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- [mpowr] Getting Bad Ideas to Fail Early Margaret Wasserman
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Margaret Wasserman
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early Alex Rousskov
- [mpowr] Re: Getting Bad Ideas to Fail Early James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James Kempf
- Re: [mpowr] SUMMARY: Mailing List Management Disc… David Partain (LI/EAB)
- Re: [mpowr] SUMMARY: Mailing List Management Disc… Alex Rousskov
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early Alex Rousskov
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early David Meyer
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early David Meyer
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early David Partain (LI/EAB)
- Re: [mpowr] Experiment design John C Klensin
- Re: [mpowr] SUMMARY: Mailing List Management Disc… James M Galvin
- Re: [mpowr] Experiment design Spencer Dawkins
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early Mark Allman
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early Spencer Dawkins
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early David Partain (LI/EAB)
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early David Partain (LI/EAB)
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early James Kempf
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early Mark Allman
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early Spencer Dawkins
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early David Partain
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early David Partain
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early David Partain
- Re: [mpowr] Re: Getting Bad Ideas to Fail Early Spencer Dawkins