Re: Progressing I-Ds Immediately Before Meetings

ned+ietf@mauve.mrochek.com Sun, 20 July 2008 01:50 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 3CDDB3A6960; Sat, 19 Jul 2008 18:50:19 -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 2404C3A68F8 for <ietf@core3.amsl.com>; Sat, 19 Jul 2008 18:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.657
X-Spam-Level:
X-Spam-Status: No, score=-0.657 tagged_above=-999 required=5 tests=[AWL=0.006, 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 3ijjGcUJHReg for <ietf@core3.amsl.com>; Sat, 19 Jul 2008 18:50:17 -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 4572D3A6960 for <ietf@ietf.org>; Sat, 19 Jul 2008 18:50:17 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01MXCM7CD8W000C7Y3@mauve.mrochek.com> for ietf@ietf.org; Sat, 19 Jul 2008 18:50:52 -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:50:49 -0700 (PDT)
Date: Sat, 19 Jul 2008 18:42:04 -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 13:36:12 +1200" <4882968C.5090800@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-id: <01MXCM7B6YVG00007A@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> <4882968C.5090800@gmail.com>
Cc: ned+ietf@mauve.mrochek.com, Ned Freed <ned.freed@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

> No, I' not assuming that. I'm talking (selfishly) about the inflow of drafts
> that one participant may need to read regardless of source, and I (selfishly)
> want that inflow to stop a couple of weeks in advance.

But that's exactly the problem - the documents keep changing, you're just
walling yourself off from the current versions.

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

> Yes, and it's also permissible and does happen for people in the WG
> session to object to drafts being discussed that have arrived too
> late to be read.

Never seen it happen myself.

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

> True, but other individuals disagree.

Disagree as to the facts? This was happened. I can dig up the postings to lists
if necessary to prove 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?

> Because I fear that the resulting temptation for each WG to consider
> only its own needs, plus the human tendency to work to deadlines,
> would result in ~300 drafts arriving on the Friday before the IETF
> starts.

And what's your evidence supporting such a thing being likely to happen? Given
that the gate opens at the start of the week, a strong tendencdy towards an
onslaught of premetting drafts would surely have already translated into a
bunch  being posted on Monday. AFAIK that has not happened.

I thknk we have enough real and pressing concerns to worry about without
manufacturing unlikely scenarios like this.

And more to the point, nothing prevents us from dealing with that problem in
the unlikely event it actually arises.

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