Re: Another document series?

Harald Tveit Alvestrand <harald@alvestrand.no> Tue, 30 November 2004 18:08 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15431; Tue, 30 Nov 2004 13:08:37 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZCVj-0002Tj-Rt; Tue, 30 Nov 2004 13:14:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZCCw-00058z-Bx; Tue, 30 Nov 2004 12:54:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZC8u-0003qh-MR for ietf@megatron.ietf.org; Tue, 30 Nov 2004 12:50:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13216 for <ietf@ietf.org>; Tue, 30 Nov 2004 12:50:21 -0500 (EST)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZCE2-0001tW-H7 for ietf@ietf.org; Tue, 30 Nov 2004 12:55:44 -0500
Received: from localhost (localhost.localdomain [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 6EE9661BEE; Tue, 30 Nov 2004 18:49:51 +0100 (CET)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20851-07; Tue, 30 Nov 2004 18:49:49 +0100 (CET)
Received: from [192.168.1.145] (162.80-203-220.nextgentel.com [80.203.220.162]) by eikenes.alvestrand.no (Postfix) with ESMTP id 4394161BDE; Tue, 30 Nov 2004 18:49:49 +0100 (CET)
Date: Tue, 30 Nov 2004 18:49:47 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Michael StJohns <mstjohns@mindspring.com>, ietf@ietf.org
Message-ID: <8A1A2B07C32CAF7D5481EBEC@gloppen.hjemme.alvestrand.no>
In-Reply-To: <6.2.0.14.2.20041130121330.05125640@localhost>
References: <6.2.0.14.2.20041130121330.05125640@localhost>
X-Mailer: Mulberry/3.1.6 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit
Subject: Re: Another document series?
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.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://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit


--On tirsdag, november 30, 2004 12:13:41 -0500 Michael StJohns 
<mstjohns@mindspring.com> wrote:

> Folks -
>
> I've recently been asked to review a number of works in progress related
> to restructuring and other similar things.  Those documents were
> liberally splattered with references to various IDs
> (http://www.ietf.org/internet-drafts/draft-ietf-newtrk-cruft-00.txt,
> http://www.ietf.org/internet-drafts/draft-ietf-newtrk-repurposing-isd-00.
> txt, http://www.ietf.org/internet-drafts/draft-wasserman-iasa-bcp-01.txt
> etc).  Its unclear that either the work in progress or the cited drafts
> will ever be published as RFCs.

The answer is yes-if-successful, yes-if-consensus, yes-with-namechange for 
those three particular documents. Not much different from the I-Ds of any 
given working group.

> Its also unclear that this
> (restructuring etc) will be resolved within the 6 month lifetime of any
> given ID.  Its also unclear that we can afford to either have these
> expire, or continually resubmit them.  And finally, we NEED to have this
> set of documents as permanent archivable documents to maintain the
> historical record.

Query: What purpose do you see the historical record as having?
I'm serious - "visibility to serious historians", "historical sunshine law" 
and "armoury for lawyers in court cases" are very different things to 
design for.

> It seems to me that neither ID status nor RFC status are appropriate for
> these documents.  The ID series is, by design, ephemeral and generally
> not citeable.  The RFC series is stable and citeable, but the lead time
> for introducing an RFC is somewhat north of 30 days or more.

Optimist.... the current queue time (approval to publication) is closer to 
4 months for IETF standards track. The effort at speeding up the IESG 
approval process has had ripple effects :-(
(that's why the RFC Editor's 2006 budget shows a hefty increase, btw...)

> I hate to open Pandora's box, but what I think we need is a citable,
> stable document series that has a production lead time similar to that of
> the IDs.  I would probably limit this to the non-technical administrivia
> we've been recently inundated with.

Unfortunately, almost the same arguments can be made for anything that has 
received serious attention in the I-D series. See the NEWTRK discussion 
about "working group snapshot".

                    Harald


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