Re: [smime] [Technical Errata Reported] RFC2633 (5019)

Russ Housley <housley@vigilsec.com> Sun, 14 May 2017 17:17 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: smime@ietfa.amsl.com
Delivered-To: smime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2552D129A8D for <smime@ietfa.amsl.com>; Sun, 14 May 2017 10:17:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rRC67Jlp27rf for <smime@ietfa.amsl.com>; Sun, 14 May 2017 10:17:44 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAC7B129B16 for <smime@ietf.org>; Sun, 14 May 2017 10:15:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id DB74D300572 for <smime@ietf.org>; Sun, 14 May 2017 13:15:02 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id QRRvgokUp38Z for <smime@ietf.org>; Sun, 14 May 2017 13:15:00 -0400 (EDT)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id BC63130029F; Sun, 14 May 2017 13:14:59 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20170514163550.3ECC2B80A6E@rfc-editor.org>
Date: Sun, 14 May 2017 13:14:59 -0400
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, Blake Ramsdell <blaker@gmail.com>, Josh Soref <jsoref@gmail.com>, IETF SMIME <smime@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <13A0972A-2D00-4DF8-BFA9-C022D914BCEF@vigilsec.com>
References: <20170514163550.3ECC2B80A6E@rfc-editor.org>
To: Kathleen Moriarty <Kathleen.Moriarty.ietf@gmail.com>, Eric Rescorla <ekr@rtfm.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/3JhPe8mkl3FXNInuY5ihSvs2cpA>
Subject: Re: [smime] [Technical Errata Reported] RFC2633 (5019)
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/smime/>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 14 May 2017 17:17:46 -0000

I believe that this errata should be rejected.  The author used an abbreviation, and the same spelling is used in RFC 3851.

Russ


> On May 14, 2017, at 12:35 PM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been submitted for RFC2633,
> "S/MIME Version 3 Message Specification".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata/eid5019
> 
> --------------------------------------
> Type: Technical
> Reported by: Josh Soref <jsoref@gmail.com>
> 
> Section: 5
> 
> Original Text
> -------------
> id-aa-encrypKeyPref OBJECT IDENTIFIER ::= {id-aa 11}
> 
> 
> Corrected Text
> --------------
> id-aa-encrypKeyPref [sic] OBJECT IDENTIFIER ::= {id-aa 11}
> 
> Notes
> -----
> encryp isn't a word, it's a typo. Unfortunately, like http's (rfc1945) referer [sic] before it, this is now part of the API.
> 
> This error should be highlighted (as rfc2068 does for referer [sic]) so that people are aware that the natural spelling doesn't apply.
> 
> If it's possible for a revised RFC to be published suggesting the correct spelling w/ a way for clients/servers to handle the old spelling, that would be nice, but based on precedent, that seems unlikely.
> 
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party  
> can log in to change the status and edit the report, if necessary. 
> 
> --------------------------------------
> RFC2633 (draft-ietf-smime-msg-08)
> --------------------------------------
> Title               : S/MIME Version 3 Message Specification
> Publication Date    : June 1999
> Author(s)           : B. Ramsdell, Ed.
> Category            : PROPOSED STANDARD
> Source              : S/MIME Mail Security
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG
> 
> _______________________________________________
> smime mailing list
> smime@ietf.org
> https://www.ietf.org/mailman/listinfo/smime