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

Barry Leiba <barryleiba@computer.org> Thu, 02 August 2012 14:05 UTC

Return-Path: <barryleiba@gmail.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 AE11321F84EE for <ietf@ietfa.amsl.com>; Thu, 2 Aug 2012 07:05:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.83
X-Spam-Level:
X-Spam-Status: No, score=-102.83 tagged_above=-999 required=5 tests=[AWL=-0.153, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 BJIAxhtFIQsp for <ietf@ietfa.amsl.com>; Thu, 2 Aug 2012 07:05:20 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id E1AD621F845B for <ietf@ietf.org>; Thu, 2 Aug 2012 07:05:19 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so8921972vcb.31 for <ietf@ietf.org>; Thu, 02 Aug 2012 07:05:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=4TgASHtsu1wJXrNq9S9wQDKFZfVKELlNonH8Iz5qEwo=; b=Nn6Tw4p1faiLoP0kWAEpm+aCvVeed4+OTjoiHLr1mnJZMGHVxXpMEzpJlAyU1do9s0 prwmUJb6kgF4wmIPY66kswkvzWL23NQpjDPxw/RgwMrWlZdTBcv0+yjAYbJbkXSchGAq RDROBs185TfonYwMOUDsfgWavYjDOmQ0wS2ZbZtx2ZLiurt78mYWUz/D/3C2LodDiU6U hBRxgg5Sc3BbtiSxHTKtbGc2WIrc/vaqheaLL/isXiFJ4Z/q9Kp624kAt00wLJItiffC WN7IjJtvSshoTbSLgQb3RFjO+1F19BLkrqKNfIqMbpTRHvCmOo9TJkVjzHqVf5OVqZ3Y pKDA==
MIME-Version: 1.0
Received: by 10.58.68.163 with SMTP id x3mr9300812vet.41.1343916319353; Thu, 02 Aug 2012 07:05:19 -0700 (PDT)
Sender: barryleiba@gmail.com
Received: by 10.220.29.8 with HTTP; Thu, 2 Aug 2012 07:05:19 -0700 (PDT)
In-Reply-To: <501A5656.2050407@it.aoyama.ac.jp>
References: <CALaySJKV96tdXhzfPD1e1Mro_+gp5aDarF7Z06QrA+iQtnHkLw@mail.gmail.com> <501A5656.2050407@it.aoyama.ac.jp>
Date: Thu, 02 Aug 2012 10:05:19 -0400
X-Google-Sender-Auth: 9NGW7Rg1xHp8SUWdgXxpKlalGLw
Message-ID: <CALaySJJUufTeKSoRoqgiBqm0MzDM_h+YQ30hVKVNA0hg--74Sg@mail.gmail.com>
Subject: Re: RFC Errata: when to file, and when not to
From: Barry Leiba <barryleiba@computer.org>
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: IETF discussion list <ietf@ietf.org>
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: Thu, 02 Aug 2012 14:05:20 -0000

> Thanks for explanation about errata, which must have been caused at least in
> part by an erratum that I submitted recently.

Yours was one of many.  Yours was actually one that I'd like to find a
way to fix -- a URL that needs to be updated.

>> In particular, the errata system is NOT meant to be used as an issue
>> tracker; please do not submit errata reports with the *intent* that they
>> be marked as "Held for Document Update", to be used as an issue
>> list later.  We have mailing lists, issue trackers, and wikis for this purpose.
>
> Of course we have mailing lists, issue trackers, and wikis, but the problem
> is that none of them are for RFCs. And if there's a tracker for a bis
> version, it's not necessarily easy to find from the RFC.

Yes, and we're working on that.  We're looking into ways of handling
this, to provide some sort of issue tracking for RFCs.  Not sure yet
what the right way to do it is.

Barry