Re: [mpowr] WG Formation

Thomas Narten <narten@us.ibm.com> Fri, 20 February 2004 19:18 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 OAA07580 for <mpowr-archive@odin.ietf.org>; Fri, 20 Feb 2004 14:18:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuGA6-0006ax-Bq for mpowr-archive@odin.ietf.org; Fri, 20 Feb 2004 14:18:10 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1KJIAWq025345 for mpowr-archive@odin.ietf.org; Fri, 20 Feb 2004 14:18:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuGA6-0006aZ-5e for mpowr-web-archive@optimus.ietf.org; Fri, 20 Feb 2004 14:18:10 -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 OAA07575 for <mpowr-web-archive@ietf.org>; Fri, 20 Feb 2004 14:18:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuGA3-0001OU-00 for mpowr-web-archive@ietf.org; Fri, 20 Feb 2004 14:18:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuG9B-0001Lo-00 for mpowr-web-archive@ietf.org; Fri, 20 Feb 2004 14:17:14 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1AuG8w-0001IJ-00 for mpowr-web-archive@ietf.org; Fri, 20 Feb 2004 14:16:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuG8y-0006Mw-Fk; Fri, 20 Feb 2004 14:17:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AuG8A-0006J2-Dw for mpowr@optimus.ietf.org; Fri, 20 Feb 2004 14:16:10 -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 OAA07497 for <mpowr@ietf.org>; Fri, 20 Feb 2004 14:16:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AuG87-0001Ge-00 for mpowr@ietf.org; Fri, 20 Feb 2004 14:16:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AuG7D-0001D7-00 for mpowr@ietf.org; Fri, 20 Feb 2004 14:15:12 -0500
Received: from e34.co.us.ibm.com ([32.97.110.132]) by ietf-mx with esmtp (Exim 4.12) id 1AuG6Y-000167-00 for mpowr@ietf.org; Fri, 20 Feb 2004 14:14:30 -0500
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e34.co.us.ibm.com (8.12.10/8.12.2) with ESMTP id i1KJDpvC506726; Fri, 20 Feb 2004 14:13:51 -0500
Received: from rotala.raleigh.ibm.com (d03av02.boulder.ibm.com [9.17.193.82]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.6) with ESMTP id i1KJDoDC024908; Fri, 20 Feb 2004 12:13:50 -0700
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.12.8/8.12.5) with ESMTP id i1KJDo7c025082; Fri, 20 Feb 2004 14:13:50 -0500
Received: from rotala.raleigh.ibm.com (narten@localhost) by rotala.raleigh.ibm.com (8.12.8/8.12.8/Submit) with ESMTP id i1KJDnD9025078; Fri, 20 Feb 2004 14:13:49 -0500
Message-Id: <200402201913.i1KJDnD9025078@rotala.raleigh.ibm.com>
To: Dave Crocker <dcrocker@brandenburg.com>
cc: mpowr@ietf.org
Subject: Re: [mpowr] WG Formation
In-Reply-To: Message from dcrocker@brandenburg.com of "Wed, 18 Feb 2004 18:08:48 PST." <1209179081.20040218180848@brandenburg.com>
Date: Fri, 20 Feb 2004 14:13:49 -0500
From: Thomas Narten <narten@us.ibm.com>
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.1 required=5.0 tests=AWL autolearn=no version=2.60

Dave,

> As I said, if there is rough consensus that we do not have a problem
> with BOFs (and, yes, working groups) being authorized without sufficient
> preparatory work, then my suggestion should not carry the day.

I don't think the problem with underperforming WGs can be attributed
to something as simple as inadequate preparatory work. Later, you say:

> Importance to the net is, of course... important. However a failure to
> develop a clear working path is a show-stopper. The IETF has
> demonstrated a pretty clear pattern of success only when folks who will
> work on a problem have a clear, shared sense of the problem and the
> approach towards solving it.

I think this is one of the better predictors for success. When the
folks in the WG (and the WG Chair/AD/IESG) are all on the same page in
terms you describe above.

But it is not all that uncommon for an effort (whether BOF or even WG)
for there to be much more diversity in where folks heads are at. The
challenge then is finding a way to steer towards a shared
vision/direction. And in some sense, that is part of the what the WG
process is all about. I.e, finding (or developing) consensus among the
set of participants.

> Does that mean keep the status quo for dealing with BOFs or did you have
> a suggestion for something that will make them more useful?

My own view is that the BOF->WG process does have problems. Namely, as
I recall the original message of the thread mentioning , we have cases
where it just seems to take longer than it should from start to
finish. I don't have any obvious answers.

What I think might be useful though it see if we can understand the
problem better than "it's not working". I.e., it might make sense to
look at 5-10 BOF->WG efforts that happened in the last year or so, and
try to understand how well the system worked (or didn't work) in each
of those cases. There may be some general observations/lessons there
that can be used to improve future efforts.

Thomas

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