Re: Progressing I-Ds Immediately Before Meetings

ned+ietf@mauve.mrochek.com Sun, 20 July 2008 03:41 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1A0EF3A67FF; Sat, 19 Jul 2008 20:41:25 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D36EF3A6804 for <ietf@core3.amsl.com>; Sat, 19 Jul 2008 20:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.658
X-Spam-Level:
X-Spam-Status: No, score=-0.658 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HOST_EQ_STATIC=1.172]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BfItqKr88IBn for <ietf@core3.amsl.com>; Sat, 19 Jul 2008 20:41:21 -0700 (PDT)
Received: from mauve.mrochek.com (dsl-66-59-230-40.static.linkline.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 866923A67FF for <ietf@ietf.org>; Sat, 19 Jul 2008 20:41:21 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01MXCQ32FTYO00DQZ3@mauve.mrochek.com> for ietf@ietf.org; Sat, 19 Jul 2008 20:41:57 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01MXB1HLX5YO00007A@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 19 Jul 2008 20:41:54 -0700 (PDT)
Date: Sat, 19 Jul 2008 20:34:51 -0700
From: ned+ietf@mauve.mrochek.com
Subject: Re: Progressing I-Ds Immediately Before Meetings
In-reply-to: "Your message dated Sat, 19 Jul 2008 19:27:57 -0700" <4882A2AD.8040405@dcrocker.net>
To: Dave Crocker <dhc2@dcrocker.net>
Message-id: <01MXCQ316FVY00007A@mauve.mrochek.com>
MIME-version: 1.0
References: <043101c8e8ec$fa67c650$0200a8c0@your029b8cecfe> <200807181819.m6IIJCIR025085@mta6.iomartmail.com> <048401c8e924$ab2ce600$0200a8c0@your029b8cecfe> <XFE-SJC-211BBtNtxy0000033b7@xfe-sjc-211.amer.cisco.com> <4881CFF5.3090008@piuha.net> <1EFD708A-8509-42A6-BBC9-824C27A7DCFA@multicasttech.com> <6BA8110C64663A4908066554@p3.JCK.COM> <48821469.4050907@employees.org> <20080719191556.567F03A6A32@core3.amsl.com> <48826DC0.8000307@dcrocker.net> <01MXCGZDHDXW000078@mauve.mrochek.com> <48828D3B.4050006@gmail.com> <01MXCL869C4K00007A@mauve.mrochek.com> <4882A2AD.8040405@dcrocker.net>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org


> ned+ietf@mauve.mrochek.com wrote:
> >> That said, exceptions should definitely be possible, and I would
> >> delegate that to WG Chair level.
> >
> > Well, that's a step forward, but instead of delgating an exception process
> > why not delegate the authority to decide on an appropriate draft handling
> > policy?

> Oddly, I think it really doesn't.  By keeping the view that it is an
> "exception", it enforces a cumbersome, IETF-wide, Procrustean model with
> an exception, rather than a simple model with no need for exceptions.

Sigh. Point taken. I retract my previous assessment that this would be a real
step forward.

> Either working groups know how to run themselves on a daily basis --
> that is, excepting real crises -- or they don't.

Yep.

> If they do. then we do not need one-size-fits-all-except-when-it-doesn't
> rules.  If they don't, then we need to be much, much better about
> writing and enforcing rules. (And all the evidence says that we won't be.)

Indeed. Past efforts to drag groups out of the weeds have not been all that
successful, have they?

> ...

> What we really need to be is reasonable, open and accountable, with
> "local" control for local activities.

> Fewer rules, more working group self-management.

Exactly.

				Ned

P.S. It really isn't fair that you used the term "Procrustean" - one of my
favorites - to blow away my argument ;-)
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf