Re: RFC Errata: when to file, and when not to

t.p. <daedulus@btconnect.com> Tue, 07 August 2012 13:25 UTC

Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FA4021F85C7 for <ietf@ietfa.amsl.com>; Tue, 7 Aug 2012 06:25:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.571
X-Spam-Level:
X-Spam-Status: No, score=-3.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PUxXVJAesWlI for <ietf@ietfa.amsl.com>; Tue, 7 Aug 2012 06:25:24 -0700 (PDT)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe003.messaging.microsoft.com [216.32.181.183]) by ietfa.amsl.com (Postfix) with ESMTP id 80F3821F85A5 for <ietf@ietf.org>; Tue, 7 Aug 2012 06:25:24 -0700 (PDT)
Received: from mail244-ch1-R.bigfish.com (10.43.68.236) by CH1EHSOBE009.bigfish.com (10.43.70.59) with Microsoft SMTP Server id 14.1.225.23; Tue, 7 Aug 2012 13:25:23 +0000
Received: from mail244-ch1 (localhost [127.0.0.1]) by mail244-ch1-R.bigfish.com (Postfix) with ESMTP id A0C378002C0; Tue, 7 Aug 2012 13:25:23 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.224.141; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0702HT001.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: PS-23(zz98dI9371I542Mzz1202hzz1033IL8275bh8275dhz2dh2a8h5a9h668h839hd24hf0ah107ah304l)
Received: from mail244-ch1 (localhost.localdomain [127.0.0.1]) by mail244-ch1 (MessageSwitch) id 134434592296458_32050; Tue, 7 Aug 2012 13:25:22 +0000 (UTC)
Received: from CH1EHSMHS003.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.240]) by mail244-ch1.bigfish.com (Postfix) with ESMTP id 15B361BC004A; Tue, 7 Aug 2012 13:25:22 +0000 (UTC)
Received: from DB3PRD0702HT001.eurprd07.prod.outlook.com (157.55.224.141) by CH1EHSMHS003.bigfish.com (10.43.70.3) with Microsoft SMTP Server (TLS) id 14.1.225.23; Tue, 7 Aug 2012 13:25:19 +0000
Received: from DBXPRD0510HT004.eurprd05.prod.outlook.com (157.56.252.165) by pod51017.outlook.com (10.3.4.141) with Microsoft SMTP Server (TLS) id 14.15.108.4; Tue, 7 Aug 2012 13:25:10 +0000
Message-ID: <03e701cd749f$73891c40$4001a8c0@gateway.2wire.net>
From: "t.p." <daedulus@btconnect.com>
To: Yoav Nir <ynir@checkpoint.com>
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com><501A5656.2050407@it.aoyama.ac.jp> <501BEC0D.1060404@tana.it> <009101cd7476$bb522c20$4001a8c0@gateway.2wire.net> <599B1629-543A-49BC-A0E7-FA2096C538AD@checkpoint.com>
Subject: Re: RFC Errata: when to file, and when not to
Date: Tue, 07 Aug 2012 14:20:35 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.252.165]
X-OriginatorOrg: btconnect.com
Cc: ietf@ietf.org, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Tue, 07 Aug 2012 13:25:25 -0000

----- Original Message -----
From: "Yoav Nir" <ynir@checkpoint.com>
To: "t.p." <daedulus@btconnect.com>
Cc: "Alessandro Vesely" <vesely@tana.it>; <ietf@ietf.org>
Sent: Tuesday, August 07, 2012 11:58 AM
On Aug 7, 2012, at 11:29 AM, t.p. wrote:
> When I Google RFCnnnn, I am sometimes directed to www.ietf.org, which
is
> not much help here. Other times, I am directed to tools.ietf.org,
whose
> format I find less friendly but which does have 'errata exist' in the
> top right hand corner.  However, I cannot click on that,

No, but two lines above it, there's an "Errata" link, which you can
click.

> unlike the
> Obsoletes and Updates fields; but, more importantly, would your
average
> not-involved-in-standards audience know what errata are?  For me, the
> word comes from a classical education, before ever I got involved with
> standards, and so is a commonplace, but is it used in the world at
> large?  I suspect not.

Probably not, and neither is "bis". But what can you do about this?
It's either allow updating of RFCs after publication, or have a list or
corrections. Would it make it easier to find if they were called "notes"
or "corrections" instead of "errata"?

<tp>
Yes, corrections is what I see published in a newspaper to correct
errata in previous editions.  So far, it is the best word I can think of
(but there might be a better one:-).

In the html version of an RFC, it would be easy to provide old and new
in an easy to compare format (as some editors do for I-D), not perhaps
on permanent display but shown when 'errata' (or whatever name we
choose) is toggled.

Tom Petch
</tp>

Yoav