Re: Progressing I-Ds Immediately Before Meetings

ned+ietf@mauve.mrochek.com Sun, 20 July 2008 01:22 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 C2D793A6A4B; Sat, 19 Jul 2008 18:22:46 -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 A5EED3A6A62 for <ietf@core3.amsl.com>; Sat, 19 Jul 2008 18:22:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.655
X-Spam-Level:
X-Spam-Status: No, score=-0.655 tagged_above=-999 required=5 tests=[AWL=0.007, 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 bB8SnXUk-8Yd for <ietf@core3.amsl.com>; Sat, 19 Jul 2008 18:22:45 -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 E0F3C3A6A19 for <ietf@ietf.org>; Sat, 19 Jul 2008 18:22:44 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01MXCL879GTC00D87W@mauve.mrochek.com> for ietf@ietf.org; Sat, 19 Jul 2008 18:23:18 -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 18:23:16 -0700 (PDT)
Date: Sat, 19 Jul 2008 18:01:28 -0700
From: ned+ietf@mauve.mrochek.com
Subject: Re: Progressing I-Ds Immediately Before Meetings
In-reply-to: "Your message dated Sun, 20 Jul 2008 12:56:27 +1200" <48828D3B.4050006@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-id: <01MXCL869C4K00007A@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>
Cc: ned+ietf@mauve.mrochek.com, 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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

> Ned,

> ...
> > Frankly, I think it is more about trusting groups to be able to manage
> > themselves than anything else.

> I don't think that's quite fair. If you think about a participant
> who is tracking several WGs and/or topics that cut across many WGs,
> that person needs to be able to read everything relevant before > arriving.

Really? The vast majority of document revisions I see don't make significant
changes, so even when I'm tracking a bunch of groups it is exceptionally rare
for me to have to read more than a few entirely new or substantially revised
documents. The rest I just check to see what's changed, which takes very little
time. (It also highlights another thing that's changed for us - the ready
availability of tools that compare document revisions.)

Again, you appear to assume that all groups have similar document loads and
similar work patterns. This is simply not true.

> A cutoff about two weeks in advance does make that feasible.

It does nothing of the sort. Again, it is pretty common for documents that miss
the deadline to be made available through other means.

Whether you want to admit it or not, the fact is that individuals see this rule
as damaging and are routing around it.

> (Let's see - I still have about 12 drafts to read - is that unusual
> with one week to go?) I would much rather have that situation, so
> that I can prioritize the drafts, than have them arriving until
> after I'm already in the air, which would be the inevitable result
> of relaxing the cutoff rules.

> 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?

				Ned
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf