Re: How long does it take on an average for WG I-Ds?

Bill Fenner <fenner@research.att.com> Sat, 14 June 2003 06:33 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 CAA19806 for <wgchairs-archive@lists.ietf.org>; Sat, 14 Jun 2003 02:33:25 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 19R42A-0005Jb-Ei for wgchairs-list@asgard.ietf.org; Sat, 14 Jun 2003 01:57:02 -0400
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 19R3YE-0004yo-Cr for wgchairs@asgard.ietf.org; Sat, 14 Jun 2003 01:26:06 -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 BAA07133 for <wgchairs@ietf.org>; Sat, 14 Jun 2003 01:26:05 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19R3W7-0004PR-00 for wgchairs@ietf.org; Sat, 14 Jun 2003 01:23:55 -0400
Received: from h-135-207-24-16.research.att.com ([135.207.24.16] helo=linux.research.att.com) by ietf-mx with esmtp (Exim 4.12) id 19R3W6-0004PI-00 for wgchairs@ietf.org; Sat, 14 Jun 2003 01:23:54 -0400
Received: from unixmail.research.att.com (unixmail.research.att.com [135.207.26.71]) by linux.research.att.com (8.12.8/8.12.8) with ESMTP id h5E5VkEI028506; Sat, 14 Jun 2003 01:31:46 -0400
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by unixmail.research.att.com (8.12.8+Sun/8.8.7) with ESMTP id h5E5NtXs010007; Sat, 14 Jun 2003 01:23:55 -0400 (EDT)
From: Bill Fenner <fenner@research.att.com>
Received: (from fenner@localhost) by windsor.research.att.com (8.11.6+Sun/8.8.5) id h5E5PUs25593; Fri, 13 Jun 2003 22:25:30 -0700 (PDT)
Message-Id: <200306140525.h5E5PUs25593@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
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
Versions: dmail (solaris) 2.5a/makemail 2.9d
Sender: owner-wgchairs@ietf.org
Precedence: bulk

>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.
See http://rtg.ietf.org/~fenner/iesg/analyze-rfcq.txt .  (This analysis
assumes that the rfc-editor queue reflects the current state of a document
at any given time; I take a daily snapshot of the rfc-editor queue and
log the deltas.)

  Bill