Another document series?

Michael StJohns <mstjohns@mindspring.com> Tue, 30 November 2004 17:37 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 MAA11654; Tue, 30 Nov 2004 12:37:43 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZC1o-0001Wa-AV; Tue, 30 Nov 2004 12:43:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZBpJ-00070p-CB; Tue, 30 Nov 2004 12:30:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZBa2-000124-VG for ietf@megatron.ietf.org; Tue, 30 Nov 2004 12:14:22 -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 MAA08311 for <ietf@ietf.org>; Tue, 30 Nov 2004 12:14:18 -0500 (EST)
Received: from smtpauth09.mail.atl.earthlink.net ([209.86.89.69]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZBfB-0000jR-5j for ietf@ietf.org; Tue, 30 Nov 2004 12:19:41 -0500
Received: from [69.143.212.105] (helo=stjohns-lap2.mindspring.com) by smtpauth09.mail.atl.earthlink.net with asmtp (TLSv1:AES256-SHA:256) (Exim 4.34) id 1CZBZN-0002MA-NW for ietf@ietf.org; Tue, 30 Nov 2004 12:13:41 -0500
Message-Id: <6.2.0.14.2.20041130121330.05125640@localhost>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Tue, 30 Nov 2004 12:13:41 -0500
To: ietf@ietf.org
From: Michael StJohns <mstjohns@mindspring.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-ELNK-Trace: 9f6ded143da542dc9c7f779228e2f6aeda0071232e20db4d3afa81706daa6a090bded5183b9c1813350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 69.143.212.105
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Subject: 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.1 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034

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

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.

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.

*sigh*

Mike


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