[mpowr] bookkeeping

Dave Crocker <dhc@dcrocker.net> Mon, 16 February 2004 18:03 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 NAA09305 for <mpowr-archive@odin.ietf.org>; Mon, 16 Feb 2004 13:03:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Asn5U-00027s-2V for mpowr-archive@odin.ietf.org; Mon, 16 Feb 2004 13:03:20 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i1GI3Kab008171 for mpowr-archive@odin.ietf.org; Mon, 16 Feb 2004 13:03:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Asn5T-00027i-O2 for mpowr-web-archive@optimus.ietf.org; Mon, 16 Feb 2004 13:03:19 -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 NAA09153 for <mpowr-web-archive@ietf.org>; Mon, 16 Feb 2004 13:03:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Asn5R-0006Jd-00 for mpowr-web-archive@ietf.org; Mon, 16 Feb 2004 13:03:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Asn3s-00062G-00 for mpowr-web-archive@ietf.org; Mon, 16 Feb 2004 13:01:41 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com) by ietf-mx with esmtp (Exim 4.12) id 1Asn2t-0005xM-01 for mpowr-web-archive@ietf.org; Mon, 16 Feb 2004 13:00:39 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by mx2.foretec.com with esmtp (Exim 4.24) id 1Asmtb-0001Qw-Oe for mpowr-web-archive@ietf.org; Mon, 16 Feb 2004 12:51:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AsmtZ-0001O8-Ln; Mon, 16 Feb 2004 12:51:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1Asmt1-0001Ek-5O for mpowr@optimus.ietf.org; Mon, 16 Feb 2004 12:50:27 -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 MAA08840 for <mpowr@ietf.org>; Mon, 16 Feb 2004 12:50:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1Asmsz-0005Xr-00 for mpowr@ietf.org; Mon, 16 Feb 2004 12:50:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AsmsH-0005TP-00 for mpowr@ietf.org; Mon, 16 Feb 2004 12:49:42 -0500
Received: from joy.songbird.com ([208.184.79.7]) by ietf-mx with esmtp (Exim 4.12) id 1AsmrJ-0005CT-00 for mpowr@ietf.org; Mon, 16 Feb 2004 12:48:41 -0500
Received: from bbprime (jay.songbird.com [208.184.79.253]) by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i1GHudd30516; Mon, 16 Feb 2004 09:56:39 -0800
Date: Mon, 16 Feb 2004 09:48:00 -0800
From: Dave Crocker <dhc@dcrocker.net>
Reply-To: Dave Crocker <dcrocker@brandenburg.com>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <36725270.20040216094800@brandenburg.com>
To: Harald Tveit Alvestrand <harald@alvestrand.no>
CC: mpowr@ietf.org
In-Reply-To: <171920638.1076920805@localhost>
References: <126800950.1076875685@localhost> <1801091131.20040215214531@brandenburg.com> <171920638.1076920805@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [mpowr] bookkeeping
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.7 required=5.0 tests=AWL,PRIORITY_NO_NAME autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Harald,


>> Except that most of the formative BOFs that I've been to in the last few
>> years have had little or no prior activity.

HTA> Dave, at the risk of beating an old, tired drum once again:
HTA> Can you name some of these BOFs, so that we can check whether all of us 
HTA> have the same perception of whether there was prior activity?

No.

It would distract from the discussion.

However your query highlights a basic difference in views about
discussing and resolving strategic issues in the IETF.

Either there is rough consensus that we have a problem with working
groups and BOFs that are unproductive, or we don't. If we don't, then
let's move on. I'll shut up. If we do have rough consensus about this,
then we do not need to cite statistics.

Let me repeat:  If there is rough consensus that BOF time is generally
well spent, then everyone should please ignore my suggestion.

On the other hand, if there is rough consensus that BOF time is too
often wasted or, at least, inefficient, then we can focus on the nature
of my suggestions rather than on bookeeping.

Similarly, there is a basic difference in views, between "empowering"
groups to self-form and demonstrate capabilities, versus tasking
volunteer management with "fixing" those groups that lack the
capabilities.

If there is rough consensus that IETF management fixes things well, then
again, ignore my suggestion and let's move on.

If there is rough consensus that problematic working groups do not get
fixed all that well and do constitute a problem, then let's talk about
solutions.

One solution is to expect IETF management to do a better job of fixing
things, or of generally "managing" things better.

Another is to look for ways to prevent the problems in the first place,
or at least to move the problems to be outside the IETF.


HTA> But the point I was trying to make was a completely different one - that we
HTA> make BOFs for many reasons. For some types of BOFs, it's appropriate to ask 
HTA> for prior activity on a mailing list.

That's nice.  My own focus has been on pre-chartering BOFs.


HTA>  or we have to trust someone's judgment on when to require
HTA> proof of prior activity.

HTA> Which one is the best use of resources?

That sounds like the status quo.  Forgive me, but I thought that that
was not working very well.  As in, it has not been working at all.  So
why will it work in the future>?

Rather than trivialize this as a labeling excercise, I suggest we look
at real problems and pursue real solutions.

"Trust someone's judgement" has not been working. I believe we have
community consensus on this point. That means we need to look for
changes to make.

If you are suggesting a change, I'm not understanding what it is.

d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>


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