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

Alessandro Vesely <vesely@tana.it> Fri, 03 August 2012 15:19 UTC

Return-Path: <vesely@tana.it>
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 C241F21F8DE9 for <ietf@ietfa.amsl.com>; Fri, 3 Aug 2012 08:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level:
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
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 V9CFs42TQ4vW for <ietf@ietfa.amsl.com>; Fri, 3 Aug 2012 08:19:56 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id A140921F8DE8 for <ietf@ietf.org>; Fri, 3 Aug 2012 08:19:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=test; t=1344007194; bh=L6MOheLECERarDcHP5PyVPWGhonlUBqGVZyNCMdo4Rc=; l=916; h=Message-ID:Date:From:MIME-Version:To:References:In-Reply-To: Content-Transfer-Encoding; b=B0+Eag8d1bLM+jPfEXLpzsuyuUD+/n8rn6+7DWl91vEvgWcsvWVBvCtWZ0r8Dsb8Y jegTgBNj0RoczQMtbgham9CztvVvpZNX2xMb3i8iCq1ayROKgd7e8h3C3KLWPT260x qft+TZyVJKJpZg11unrhDq2uts5TGzDhokpX8+4c=
Received: from [208.181.206.141] (softdnserr [208.181.206.141]) (AUTH: PLAIN 515, TLS: TLS1.0,256bits,RSA_AES_256_CBC_SHA1) by wmail.tana.it with ESMTPSA; Fri, 03 Aug 2012 17:19:52 +0200 id 00000000005DC049.00000000501BEC1A.00004F83
Message-ID: <501BEC0D.1060404@tana.it>
Date: Fri, 03 Aug 2012 08:19:41 -0700
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: RFC Errata: when to file, and when not to
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com> <501A5656.2050407@it.aoyama.ac.jp>
In-Reply-To: <501A5656.2050407@it.aoyama.ac.jp>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
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: Fri, 03 Aug 2012 15:19:58 -0000

On Thu 02/Aug/2012 03:28:38 -0700 Martin J. Dürst wrote:
> 
>> In particular, the errata system is NOT meant to be used as an issue
>> tracker;
> 
> Of course we have mailing lists, issue trackers, and wikis, but the
> problem is that none of them are for RFCs.

In addition, those tools seem to be intended rather for IETF internal
use than for general public.

> The question then comes up on whether we can do better. And my guess
> is that in this day and age of linked information, we should be able
> to do better. With the tools version of an RFC, which is quickly
> becoming the preferred version of many, it's already easy to find errata.

It is /not difficult/ to find errata.  "Easy" would mean that people
usually find them even if they're not purposely looking for them.  For
example, the existence of an approved errata could be signaled by
coloring the margin near the relevant text.