Re: [Editorial Errata Reported] RFC5537 (1980)

RFC Editor <rfc-editor@rfc-editor.org> Tue, 29 December 2009 18:49 UTC

Return-Path: <owner-ietf-usefor@mail.imc.org>
X-Original-To: ietfarch-usefor-archive@core3.amsl.com
Delivered-To: ietfarch-usefor-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D36E33A690C for <ietfarch-usefor-archive@core3.amsl.com>; Tue, 29 Dec 2009 10:49:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.241
X-Spam-Level:
X-Spam-Status: No, score=-4.241 tagged_above=-999 required=5 tests=[AWL=1.805, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 qFtjJzFJV4F5 for <ietfarch-usefor-archive@core3.amsl.com>; Tue, 29 Dec 2009 10:49:57 -0800 (PST)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id F15993A68DF for <usefor-archive@ietf.org>; Tue, 29 Dec 2009 10:49:56 -0800 (PST)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id nBTIlxZS002282 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Dec 2009 11:47:59 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id nBTIlxdn002281; Tue, 29 Dec 2009 11:47:59 -0700 (MST) (envelope-from owner-ietf-usefor@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-usefor@mail.imc.org using -f
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id nBTIlvKi002275 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-usefor@imc.org>; Tue, 29 Dec 2009 11:47:58 -0700 (MST) (envelope-from rfc-ed@ISI.EDU)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id nBTIl686026308; Tue, 29 Dec 2009 10:47:07 -0800 (PST)
Received: (from rfc-ed@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id nBTIl5NC026297; Tue, 29 Dec 2009 10:47:05 -0800 (PST)
Date: Tue, 29 Dec 2009 10:47:05 -0800
From: RFC Editor <rfc-editor@rfc-editor.org>
To: Russ Allbery <rra@stanford.edu>
Cc: Julien ?LIE <julien@trigofacile.com>, Alfred H?nes <ah@TR-Sys.de>, chl@clerew.man.ac.uk, lisa.dusseault@gmail.com, alexey.melnikov@isode.com, harald@alvestrand.no, ietf-usefor@imc.org, RFC Editor <rfc-editor@rfc-editor.org>
Subject: Re: [Editorial Errata Reported] RFC5537 (1980)
Message-ID: <20091229184705.GA23795@isi.edu>
References: <200912282024.VAA13636@TR-Sys.de> <871viebzzi.fsf@windlord.stanford.edu> <06466FD87F5347558C8C6314998443E0@Iulius> <87bphhy76f.fsf@windlord.stanford.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <87bphhy76f.fsf@windlord.stanford.edu>
User-Agent: Mutt/1.4.1i
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@boreas.isi.edu
Sender: owner-ietf-usefor@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-usefor/mail-archive/>
List-Unsubscribe: <mailto:ietf-usefor-request@imc.org?body=unsubscribe>
List-ID: <ietf-usefor.imc.org>

Russ,

In our opinion, it's better to ammend the existing errata report.  The
errata system was not meant to hold errata for errata entries or to
hold multpile errata entries for the same error, as it could be
confusing for readers.

Please note that the responsible AD has the ability to edit the entry
before verifying it. 

Please let us know if you have any questions.

Thank you.

RFC Editor/sg


On Tue, Dec 29, 2009 at 10:19:20AM -0800, Russ Allbery wrote:
> Julien ?LIE <julien@trigofacile.com> writes:
> 
> > Maybe I should re-ask, before the verification takes place...
> > Didn't the mails I sent for errata 1979, 1980 and 1982 reach you?
> 
> They did, yes.
> 
> >> Given this, I agree with all the changes you propose and think the
> >> errata should be verified in its entirety.
> 
> > If the erratum is to be verified, be sure to also include the fourth paragraph
> > of Section 3.4.  It should also be amended:
> 
> >    predating this specification do not add an Injection-Date header.
> 
> > "field" is missing.
> 
> I agree with this change.  I'm not sure how this process works -- whether
> it's better to amend the existing errata or add another one.
> 
> > Another thing:  why is it "header field value" and not "header field
> > body"?  RFCs 5322 and 5536 define "header field body" but not "header
> > field value".  Where is the terminology drawn?
> 
> This is a good point that I didn't check originally.  It does sound like
> header field body might be a better term to use.
> 
> -- 
> Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>