Re: [apps-discuss] [Editorial Errata Reported] RFC6365 (2966)
Peter Saint-Andre <stpeter@stpeter.im> Mon, 17 October 2011 16:08 UTC
Return-Path: <stpeter@stpeter.im>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA08A21F8D2B for <apps-discuss@ietfa.amsl.com>; Mon, 17 Oct 2011 09:08:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, 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 E2iKsQYDrwtM for <apps-discuss@ietfa.amsl.com>; Mon, 17 Oct 2011 09:08:15 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id E1A0221F8D2A for <apps-discuss@ietf.org>; Mon, 17 Oct 2011 09:08:15 -0700 (PDT)
Received: from dhcp-64-101-72-193.cisco.com (unknown [64.101.72.193]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 041AE41E49; Mon, 17 Oct 2011 10:13:02 -0600 (MDT)
Message-ID: <4E9C52E8.80306@stpeter.im>
Date: Mon, 17 Oct 2011 10:08:08 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
References: <20110910083446.7D45098C251@rfc-editor.org> <8FDDE9E59CF60C43C95F3951@PST.JCK.COM> <20110910190557.GA13739@laperouse.bortzmeyer.org> <2A0F6A6C7A60F7292A0A104C@[192.168.1.128]>
In-Reply-To: <2A0F6A6C7A60F7292A0A104C@[192.168.1.128]>
X-Enigmail-Version: 1.3.2
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Cc: apps-discuss@ietf.org, paul.hoffman@vpnc.org, Stéphane Bortzmeyer <bortzmeyer+rfc@nic.fr>, presnick@qualcomm.com, barryleiba@computer.org, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [apps-discuss] [Editorial Errata Reported] RFC6365 (2966)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Oct 2011 16:08:16 -0000
On 9/10/11 4:58 PM, John C Klensin wrote: > > > --On Saturday, September 10, 2011 20:05 +0100 Stéphane > Bortzmeyer <bortzmeyer+rfc@nic.fr> wrote: > >> ... >>> post-publication nit-picking on RFCs. >> >> I would say otherwise: such an errata is of small importance, >> in the grand scheme of things, but, should a 6365bis appear >> one day, it is a good idea if such problems are stored >> somewhere for the future revision. What is wrong with using >> the errata database as a bug-tracking system? And what is the >> actual cost of storing one bug in this database? > > Stéphane, > > First, my apologies for overreacting somewhat. Bad week. > > Beyond that, there are two answers to your question. The first > is that, while it is probably inevitable that something will > slip through every once in a while, the amount of nit-picking > that goes on with a document like this while it is passing > through the approval stages makes it extremely frustrating that > something of more significance than many of the things that were > caught slips through nonetheless. General errata processing issues aside, the proper processing of *this* erratum seems to be "hold for document update"... http://www.ietf.org/iesg/statement/errata-processing.html Peter -- Peter Saint-Andre https://stpeter.im/
- Re: [apps-discuss] [Editorial Errata Reported] RF… John C Klensin
- [apps-discuss] [Editorial Errata Reported] RFC636… RFC Errata System
- Re: [apps-discuss] [Editorial Errata Reported] RF… John C Klensin
- Re: [apps-discuss] [Editorial Errata Reported] RF… Frank Ellermann
- Re: [apps-discuss] [Editorial Errata Reported] RF… SM
- Re: [apps-discuss] [Editorial Errata Reported] RF… Bjoern Hoehrmann
- Re: [apps-discuss] [Editorial Errata Reported] RF… Bill McQuillan
- Re: [apps-discuss] [Editorial Errata Reported] RF… Frank Ellermann
- Re: [apps-discuss] [Editorial Errata Reported] RF… SM
- Re: [apps-discuss] [Editorial Errata Reported] RF… John C Klensin
- Re: [apps-discuss] [Editorial Errata Reported] RF… Stéphane Bortzmeyer
- Re: [apps-discuss] [Editorial Errata Reported] RF… Peter Saint-Andre