Preposterous claim

Bob Braden <braden@ISI.EDU> Mon, 16 June 2003 15:52 UTC

Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18522 for <wgchairs-archive@lists.ietf.org>; Mon, 16 Jun 2003 11:52:36 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 19RvyX-0005Tg-GD for wgchairs-list@asgard.ietf.org; Mon, 16 Jun 2003 11:32:53 -0400
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 19RJRS-0000eK-Ao for wgchairs@asgard.ietf.org; Sat, 14 Jun 2003 18:24:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06724 for <wgchairs@ietf.org>; Sat, 14 Jun 2003 18:24:07 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RJPJ-0000WF-00 for wgchairs@ietf.org; Sat, 14 Jun 2003 18:21:57 -0400
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 19RJPJ-0000WC-00 for wgchairs@ietf.org; Sat, 14 Jun 2003 18:21:57 -0400
Received: (from braden@localhost) by boreas.isi.edu (8.11.6p2/8.11.2) id h5EMO2c18472; Sat, 14 Jun 2003 15:24:02 -0700 (PDT)
Date: Sat, 14 Jun 2003 15:24:02 -0700
From: Bob Braden <braden@ISI.EDU>
Message-Id: <200306142224.h5EMO2c18472@boreas.isi.edu>
To: fenner@research.att.com
Subject: Preposterous claim
Cc: pekkas@netcore.fi, aboba@internaut.com, wgchairs@ietf.org
X-Sun-Charset: US-ASCII
Sender: owner-wgchairs@ietf.org
Precedence: bulk

  *>
  *> >From: Bill Fenner <fenner@research.att.com>
  *> >To: pekkas@netcore.fi
  *> >Subject: Re: How long does it take on an average for WG I-Ds?
  *> >Cc: aboba@internaut.com, wgchairs@ietf.org
  *> >Date: Fri, 13 Jun 2003 22:25:29 -0700
  *> >
  *> >
  *> > >Unfortunately, the RFC editor's *current* publication queue does not tell
  *> > >which states the document has been in before the current "RFC-EDITOR"
  *> > >state.
  *> > >
  *> > >What I'd really like to know is the effective time rfc-editor takes;
  *> > >excluding time taken in states like REF, AUTH, AUTH48, or IESG.
  *> >
  *> >You mean like
  *> >
  *> >draft-ietf-aaa-transport 20021213 current status EDIT
  *> >draft-ietf-aaa-transport 20021213 entered queue at 2002/12/12 (1 days in
  *> >unknown state)
  *> >draft-ietf-aaa-transport 20021213 is version 09
  *> >draft-ietf-aaa-transport 20030107 changed from EDIT to AUTH
  *> >draft-ietf-aaa-transport 20030107 changed version from 09 to 11
  *> >draft-ietf-aaa-transport 20030107 was in EDIT since 20021213 (25 days)
  *> >draft-ietf-aaa-transport 20030108 changed from AUTH to EDIT
  *> >draft-ietf-aaa-transport 20030108 changed version from 11 to 09
  *> >draft-ietf-aaa-transport 20030108 was in AUTH since 20030107 (1 days)
  *> >draft-ietf-aaa-transport 20030304 changed from EDIT to IESG
  *> >draft-ietf-aaa-transport 20030304 was in EDIT since 20030108 (55 days)
  *> >draft-ietf-aaa-transport 20030414 changed from IESG to EDIT
  *> >draft-ietf-aaa-transport 20030414 changed version from 09 to 12
  *> >draft-ietf-aaa-transport 20030414 was in IESG since 20030304 (41 days)
  *> >draft-ietf-aaa-transport 20030424 changed from EDIT to RFC-EDITOR
  *> >draft-ietf-aaa-transport 20030424 was in EDIT since 20030414 (10 days)
  *> >draft-ietf-aaa-transport 20030612 changed from RFC-EDITOR to AUTH48
  *> >draft-ietf-aaa-transport 20030612 was in RFC-EDITOR since 20030424 (49 days)
  *> >draft-ietf-aaa-transport 20030613 current status AUTH48 since 20030612 (1
  *> >days)
  *> >
  *> >so the time this document spent in EDIT + RFC-EDITOR seems to be 139 days.


Bill,

I find your 139 day statement astonishing.  Your own record shows that
the document in publication first reached the RFC Editor on April 14.
I sent a message 12 hours earlier detailing the history of this
document.  I find it hard to see how to fit 139 days between April 14
and June 13, but maybe time runs differently in the Bay Area.

Bob Braden