Re: Proposed IESG Statement Regarding RFC Errata for IETF Sream RFCs
Lisa Dusseault <lisa@osafoundation.org> Thu, 17 April 2008 15:46 UTC
Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4ADA33A6A3F; Thu, 17 Apr 2008 08:46:03 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EA67528C159; Thu, 17 Apr 2008 08:45:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.626
X-Spam-Level:
X-Spam-Status: No, score=-5.626 tagged_above=-999 required=5 tests=[AWL=0.973, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NjnhZXPAkT1L; Thu, 17 Apr 2008 08:45:58 -0700 (PDT)
Received: from laweleka.osafoundation.org (laweleka.osafoundation.org [204.152.186.98]) by core3.amsl.com (Postfix) with ESMTP id 0D7A728C545; Thu, 17 Apr 2008 08:45:20 -0700 (PDT)
Received: from localhost (laweleka.osafoundation.org [127.0.0.1]) by laweleka.osafoundation.org (Postfix) with ESMTP id 97EDE1421F6; Thu, 17 Apr 2008 08:46:01 -0700 (PDT)
X-Virus-Scanned: by amavisd-new and clamav at osafoundation.org
Received: from laweleka.osafoundation.org ([127.0.0.1]) by localhost (laweleka.osafoundation.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oWNr+T5P0ZT2; Thu, 17 Apr 2008 08:45:47 -0700 (PDT)
Received: from [192.168.1.101] (unknown [74.95.2.169]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by laweleka.osafoundation.org (Postfix) with ESMTP id 54B641421FB; Thu, 17 Apr 2008 08:45:47 -0700 (PDT)
Message-Id: <A5B39114-0706-4BE1-9E53-68333E077B26@osafoundation.org>
From: Lisa Dusseault <lisa@osafoundation.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <p06240803c42d09f3a323@[10.20.30.249]>
Mime-Version: 1.0 (Apple Message framework v919.2)
Subject: Re: Proposed IESG Statement Regarding RFC Errata for IETF Sream RFCs
Date: Thu, 17 Apr 2008 08:45:43 -0700
References: <20080416151659.F075C3A6C0B@core3.amsl.com> <p06240803c42d09f3a323@[10.20.30.249]>
X-Mailer: Apple Mail (2.919.2)
Cc: ietf@ietf.org, iaoc@ietf.org, iab@iab.org, iesg@ietf.org, IETF Announcement list <ietf-announce@ietf.org>, rfc-editor@rfc-editor.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
I can assure you, I at least was anticipating that the IESG (and other people handling errata) would be doing *more* work in classifying errata if we have the three categories. The goal as I see it is to avoid presenting 50 errata on an RFC to a user, without any sorting or focus, when only three of them are crucial to interoperability. If we overwhelm implementors with more than a page worth of errata, most of which are junk, implementors will be well justified in ignoring errata. An important part of the errata handling, therefore, is to make the difference clear to the implementor. When an implementor clicks "Errata" for an RFC, they should see the short-list of crucial errata and at the end, a link to "Other possible errata" (or other wording). With that kind of interface, I don't think readers of errata need to care about the exact difference between categories: the essential difference, to them, is which ones have been brought to their immediate attention. Lisa On Apr 17, 2008, at 7:13 AM, Paul Hoffman wrote: > At 8:16 AM -0700 4/16/08, The IESG wrote: >> o Approved - The errata is appropriate under the criteria below >> and >> should be available to implementors or people deploying the RFC. >> >> o Archived - The errata is not a necessary update to the RFC. >> However, any future update of the document should consider this >> errata, and determine whether it is correct and merits including >> in the update. > > Assuming that both categories will be in the errata repository, the > difference between these two may be clear to the IESG, but it will > not be clear to readers of the errata. I suspect that the two > categories were created so that the IESG only needs to consider > "errors that could cause implementation or deployment problems or > significant confusion", not the minor stuff, but this > differentiation will simply cause more arguments about what errors > would cause problems of what magnitude. > > In the end, it is probably better for readers of the errata to have > just one category, and for the IESG to not waste its time > differentiating between the two categories. > > --Paul Hoffman, Director > --VPN Consortium > _______________________________________________ IETF mailing list IETF@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Proposed IESG Statement Regarding RFC Errata for … The IESG
- Re: Proposed IESG Statement Regarding RFC Errata … Marshall Eubanks
- Re: Proposed IESG Statement Regarding RFC Errata … Jeffrey Hutzelman
- Re: Proposed IESG Statement Regarding RFC Errata … Brian E Carpenter
- Re: Proposed IESG Statement Regarding RFC Errata … Frank Ellermann
- Re: Proposed IESG Statement Regarding RFC Errata … Pekka Savola
- Re: Proposed IESG Statement Regarding RFC Errata … Jari Arkko
- Re: Proposed IESG Statement Regarding RFC Errata … Alexey Melnikov
- Re: Proposed IESG Statement Regarding RFC Errata … Paul Hoffman
- Re: Proposed IESG Statement Regarding RFC Errata … Lisa Dusseault
- Re: Proposed IESG Statement Regarding RFC Errata … Paul Hoffman
- RE: Proposed IESG Statement Regarding RFC Errata … David Harrington
- Re: Proposed IESG Statement Regarding RFC Errata … John C Klensin
- Re: Proposed IESG Statement Regarding RFC Errata … Bob Hinden
- Re: Proposed IESG Statement Regarding RFC Errata … Bill McQuillan
- Re: Proposed IESG Statement Regarding RFC Errata … Russ Housley
- Re: Proposed IESG Statement Regarding RFC Errata … Brian E Carpenter
- Re: Proposed IESG Statement Regarding RFC Errata … Paul Hoffman
- Re: Proposed IESG Statement Regarding RFC Errata … Sabahattin Gucukoglu
- Re: Proposed IESG Statement Regarding RFC Errata … Frank Ellermann
- RE: Proposed IESG Statement Regarding RFC Errata … Yaakov Stein
- Re: Proposed IESG Statement Regarding RFC Errata … Marshall Eubanks