Re: RFC Errata proposals -- a missing piece

Paul Hoffman <paul.hoffman@vpnc.org> Mon, 02 June 2008 22:23 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 901153A6BD3; Mon, 2 Jun 2008 15:23:40 -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 5711B3A6BD1 for <ietf@core3.amsl.com>; Mon, 2 Jun 2008 15:23:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.415
X-Spam-Level:
X-Spam-Status: No, score=-2.415 tagged_above=-999 required=5 tests=[AWL=0.184, 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 ZCz7NdYiWYhL for <ietf@core3.amsl.com>; Mon, 2 Jun 2008 15:23:38 -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 4473728C184 for <ietf@ietf.org>; Mon, 2 Jun 2008 15:18:33 -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 m52MIWQx073705 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Mon, 2 Jun 2008 15:18:33 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p0624080dc46a20a3f465@[10.20.30.162]>
In-Reply-To: <g21p40$hc9$1@ger.gmane.org>
References: <57024274DF0B1306D64011FC@p3.JCK.COM> <p06240804c46a09156f43@[10.20.30.162]> <g21p40$hc9$1@ger.gmane.org>
Date: Mon, 02 Jun 2008 15:18:30 -0700
To: ietf@ietf.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 11:37 PM +0200 6/2/08, Frank Ellermann wrote:
>If what you propose boils down to "the errata should have a
>backlink to the HTML version and/or to the RFC meta data"
>it is of course fine, that is one simple global fix to the
>errata user interface.

That works for me.

>Apparently John's proposal was about the at least 60 days
>between the approval of an obsoleting / updating RFC, and
>the time when it gets its number.  For RFCs blocked by a
>MISSREF that could be years or forever.  For RFCs killed
>by an appeal it is forever, intentionally.

The RFC metadata referred to above could be updated at the time a new 
RFC is approved in its stream, not at the time the RFC itself is 
published.

--Paul Hoffman, Director
--VPN Consortium
_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf