Re: RFC Errata proposals -- a missing piece
Paul Hoffman <paul.hoffman@vpnc.org> Mon, 02 June 2008 20:34 UTC
Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE4DB3A68C7; Mon, 2 Jun 2008 13:34:50 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82F723A68C0 for <ietf@core3.amsl.com>; Mon, 2 Jun 2008 13:34:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.322
X-Spam-Level:
X-Spam-Status: No, score=-2.322 tagged_above=-999 required=5 tests=[AWL=0.277, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aAZbf1paKMnb for <ietf@core3.amsl.com>; Mon, 2 Jun 2008 13:34:48 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 4BB6D3A6783 for <ietf@ietf.org>; Mon, 2 Jun 2008 13:34:48 -0700 (PDT)
Received: from [10.20.30.162] (dsl-63-249-108-169.cruzio.com [63.249.108.169]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m52KYjeI038606 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 2 Jun 2008 13:34:48 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240804c46a09156f43@[10.20.30.162]>
In-Reply-To: <57024274DF0B1306D64011FC@p3.JCK.COM>
References: <57024274DF0B1306D64011FC@p3.JCK.COM>
Date: Mon, 02 Jun 2008 13:34:44 -0700
To: ietf@ietf.org, rfc-editor@rfc-editor.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: RFC Errata proposals -- a missing piece
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
At 6:51 AM -0400 6/2/08, John C Klensin wrote: > 5. Standards change: When a document has been approved > (via Protocol Action Notice or equivalent) that updates > or obsoletes an existing Standards Track or BCP > document, an erratum entry may be added that points to > the action notice and the approved Internet-Draft. This > is intended to be a short-lived entry, providing > information to the community for important cases during > the period between IESG approval and publication of the > new RFC. These notices are intended to exceptional > circumstances and will be added at the discretion of the > RFC Editor (e.g., in circumstances when it appears that > RFC publication of the new document will be delayed) or > at the request of the IESG or a relevant Area Director. The idea that updates appear in the Errata database is a good one. As to your proposal: why make it temporary? In normal publishing, errata are for corrections of errors *and other changes*. Clearly, an update to an RFC is a change worth noting forever. Right now, someone who wants to know what has changed in an RFC has to read the errata list *and* look at some view of the the RFC database to determine if the RFC has been updated, obsoleted, made historic, and so on. Having that notation in the errata list will help more readers, and hurt no one. --Paul Hoffman, Director --VPN Consortium _______________________________________________ IETF mailing list IETF@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Re: RFC Errata proposals -- a missing piece SM
- RFC Errata proposals -- a missing piece John C Klensin
- Re: RFC Errata proposals -- a missing piece John C Klensin
- Re: RFC Errata proposals -- a missing piece Bob Braden
- Re: RFC Errata proposals -- a missing piece Paul Hoffman
- Re: RFC Errata proposals -- a missing piece Frank Ellermann
- Re: RFC Errata proposals -- a missing piece Paul Hoffman