IETF Logo Mail Archive

Re: [rfc-i] some thoughts about errata

"John Levine" <johnl@taugh.com> Wed, 08 February 2017 15:26 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEA0F129BBD for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 8 Feb 2017 07:26:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BVSvb3t2EaZK for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Wed, 8 Feb 2017 07:26:44 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C186C120724 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Wed, 8 Feb 2017 07:26:44 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 70EDFB803EA; Wed, 8 Feb 2017 07:26:44 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 6028AB803E9 for <rfc-interest@rfc-editor.org>; Wed, 8 Feb 2017 07:26:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Of7l4MfB2BGC for <rfc-interest@rfc-editor.org>; Wed, 8 Feb 2017 07:26:38 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by rfc-editor.org (Postfix) with ESMTPS id 06775B803E4 for <rfc-interest@rfc-editor.org>; Wed, 8 Feb 2017 07:26:37 -0800 (PST)
Received: (qmail 90493 invoked from network); 8 Feb 2017 15:26:36 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 8 Feb 2017 15:26:36 -0000
Date: 8 Feb 2017 15:26:14 -0000
Message-ID: <20170208152614.14827.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: rfc-interest@rfc-editor.org
In-Reply-To: <198B8E82-B049-4535-A854-8F5BFE55826D@vpnc.org>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Subject: Re: [rfc-i] some thoughts about errata
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: paul.hoffman@vpnc.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>

>>> 1) Each erratum should have a stable URI that can be used for 
>>> citations.

That would be nice, and I expect pretty easy.  This works now:

https://www.rfc-editor.org/errata_search.php?eid=nnnn

Perhaps we could add an alternate URL with a slightly cleaner syntax
and promise it's stable, e.g.

https://www.rfc-editor.org/erratum/nnnn


>>> 2) For each RFC, there should be a machine-readable (*) HTTP resource
>>> (**) offering status information about the set of erratas present for
>>> that RFC. 

That's not much harder.  Agaim we already have this:

https://www.rfc-editor.org/errata_search.php?rfc=nnnn

The current result is formatted to look nice in a browser, but since
it's all generated on the fly from a database, a cleaner URL that
returned the result in XML or JSON would be straightforward.

R's,
John
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest

v2.8.10 | Report a Bug | By Email