Re: [Errata-design] An example of an erratum that takes time for little value

Ted Lemon <mellon@fugue.com> Thu, 15 January 2015 17:09 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: errata-design@rfc-editor.org
Delivered-To: errata-design@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id EDBB6187E25; Thu, 15 Jan 2015 09:09:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Spam-Flag: NO
X-Spam-Score: -0.01
X-Spam-Level:
X-Spam-Status: No, score=-0.01 tagged_above=-999 required=5 tests=[T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 WELjSfM7iVSo; Thu, 15 Jan 2015 09:09:40 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by rfc-editor.org (Postfix) with ESMTP id 591AA187DBF; Thu, 15 Jan 2015 09:09:40 -0800 (PST)
Received: from divertimento.ddns.nominum.com (divertimento.ddns.nominum.com [64.89.225.68]) by toccata.fugue.com (Postfix) with ESMTPSA id 8682A23808B6; Thu, 15 Jan 2015 12:09:41 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <54B7EE48.9000709@rfc-editor.org>
Date: Thu, 15 Jan 2015 09:09:39 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <30B9C017-A491-4D3A-A325-FF7F3A64BAA4@fugue.com>
References: <54B59B0A.6040809@rfc-editor.org> <2764E343-536F-4BB6-8B0E-801549D76A8A@fugue.com> <54B5A211.5070904@cs.tcd.ie> <7FB05F82-ED83-4C38-91A0-54108A80E3E8@fugue.com> <54B7EE48.9000709@rfc-editor.org>
To: "Heather Flanagan (RFC Series Editor)" <rse@rfc-editor.org>
X-Mailer: Apple Mail (2.1878.6)
Cc: errata-design@rfc-editor.org
Subject: Re: [Errata-design] An example of an erratum that takes time for little value
X-BeenThere: errata-design@rfc-editor.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <errata-design.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/errata-design>, <mailto:errata-design-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/errata-design/>
List-Post: <mailto:errata-design@rfc-editor.org>
List-Help: <mailto:errata-design-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/errata-design>, <mailto:errata-design-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jan 2015 17:09:41 -0000

On Jan 15, 2015, at 8:43 AM, Heather Flanagan (RFC Series Editor) <rse@rfc-editor.org> wrote:
> In an errata system that relies on community management to mod specific
> entries, what would it mean for the RFC Editor to handle basic typos? 
> The RFC Ed wouldn't change the existing RFC.  Would we just divert these
> entries into another system or something?  What were you thinking this
> might look like?

What I would like to see is an IETF-operated web site that is preferable to the competition (e.g., tools) and that presents errata of this sort as highlighted in a different color on the presented RFC, rather than as comments that are in a separate visual stream from the presented RFC.   I would like errata to be done similarly, if they are verified by someone who can check whether a new consensus is required to affirm the erratum.