Final proposal for aging-out I-D tombstone files
IETF Chair <chair@ietf.org> Mon, 06 June 2005 07:42 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DfCFL-0005Nz-AO; Mon, 06 Jun 2005 03:42:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DfCFI-0005Nu-UJ for ietf-announce@megatron.ietf.org; Mon, 06 Jun 2005 03:42:04 -0400
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 DAA06660 for <ietf-announce@ietf.org>; Mon, 6 Jun 2005 03:42:03 -0400 (EDT)
Received: from [132.151.6.50] (helo=newodin.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DfCa6-0002Mc-UB for ietf-announce@ietf.org; Mon, 06 Jun 2005 04:03:35 -0400
Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1DfCFI-0006kV-2F for ietf-announce@ietf.org; Mon, 06 Jun 2005 03:42:04 -0400
Content-Type: text/plain;
Mime-Version: 1.0
To: IETF Announcement list <ietf-announce@ietf.org>
From: IETF Chair <chair@ietf.org>
Message-Id: <E1DfCFI-0006kV-2F@newodin.ietf.org>
Date: Mon, 06 Jun 2005 03:42:04 -0400
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024
Subject: Final proposal for aging-out I-D tombstone files
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
Internet-Draft tombstones are dummy files that replace an I-D when it expires. For drafts published as RFCs, they are a permanent historical record. For other drafts, there are about 10000 of these small files, which are viewed by some people as useful information, and by others as a nuisance. The attached message led to comments from about 30 people. As I read the responses that have reached me by various channels, there are approximately equal numbers of people pleading to keep tombstones, to eliminate them, and to do something in between. Reading these responses, it's clear that there is a real need to be able to find out what happened to old drafts. However, that has been possible for some time using the I-D database: https://datatracker.ietf.org/public/idindex.cgi?command=search_id It knows about drafts back to 1992 or so, and can give basic information about most of them. Thus, the informational role of the tombstone files is no longer needed. However, some people do believe that having these files present for some time after a draft expires is useful (e.g. for certain types of automated processing). One person summed up the objections to tombstone files as a pollution of mirror directories: > Out of a total of 12994 files, I see 1886 currently useful files. I therefore propose to ask the Secretariat to delete all tombstones (except those for drafts that became RFCs) over 6 months old, and to delete all future tombstones (except those for drafts that become RFCs) when they reach 6 months old. This is a final call for comments; please reply to me (or to ietf@ietf.org if you want public discussion of your comment). I plan to ask the Secretariat to implement the new procedure a week from now. Brian Carpenter IETF Chair P.S. To those who have asked for expired I-Ds to be archived and visible, I have to quote RFC 2026: An Internet-Draft that is published as an RFC, or that has remained unchanged in the Internet-Drafts directory for more than six months without being recommended by the IESG for publication as an RFC, is simply removed from the Internet-Drafts directory. This has always been taken to mean that the standards process *requires* old I-Ds to be removed from public view on the IETF's servers. Nevertheless, the IETF Tools team is looking at this problem. Brian -------- Original Message -------- Subject: Proposed Elimination of Tombstone Files Date: Tue, 17 May 2005 16:24:02 -0400 From: IETF Secretariat <ietf-secretariat-reply@ietf.org> To: IETF Announcement list <ietf-announce@ietf.org> CC: wgchairs@ietf.org, chair@ietf.org The IETF Chair is considering a proposal to eliminate tombstone files for Internet-Drafts that have expired, or that have been withdrawn or replaced. If the proposal is approved, then tombstones would no longer be created for such documents, and existing tombstones would be deleted from the Internet-Drafts directory. Please note that this proposal would *not* apply to tombstones that are created for Internet-Drafts when they are published as RFCs. Before proceeding, the IETF Chair would like to determine if tombstones continue to be of value to the community, and if there is a compelling reason to retain them. If you have an opinion on this issue and wish to contribute to the discussion, then please send your comments to tombstones@ietf.org by 5:00 P.M. ET on Tuesday, May 31, 2005. The IETF Secretariat _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce