
From nobody Thu Aug  6 14:58:26 2020
Return-Path: <wwwrun@rfc-editor.org>
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 EF8A43A0788 for <smime@ietfa.amsl.com>; Thu,  6 Aug 2020 14:58:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, 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 a0XQxqvOIJtx for <smime@ietfa.amsl.com>; Thu,  6 Aug 2020 14:58:23 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C1793A0786 for <smime@ietf.org>; Thu,  6 Aug 2020 14:58:23 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 240BFF40757; Thu,  6 Aug 2020 14:58:15 -0700 (PDT)
To: housley@vigilsec.com, rdd@cert.org, kaduk@mit.edu, paul.hoffman@vpnc.org,  blaker@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: housley@vigilsec.com, smime@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20200806215815.240BFF40757@rfc-editor.org>
Date: Thu,  6 Aug 2020 14:58:15 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/ctil8Wldco1Sk441Z5xV-t14PQU>
Subject: [smime] [Technical Errata Reported] RFC5652 (6250)
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Aug 2020 21:58:25 -0000

The following errata report has been submitted for RFC5652,
"Cryptographic Message Syntax (CMS)".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6250

--------------------------------------
Type: Technical
Reported by: Russ Housley <housley@vigilsec.com>

Section: 9.2

Original Text
-------------
   If the authAttrs field is present, the content-type attribute (as
   described in Section 11.1) and the message-digest attribute (as
   described in Section 11.2) MUST be included, and the input to the MAC
   calculation process is the DER encoding of authAttrs.  A separate
   encoding of the authAttrs field is performed for message digest
   calculation.  The IMPLICIT [2] tag in the authAttrs field is not used
   for the DER encoding, rather an EXPLICIT SET OF tag is used.  That
   is, the DER encoding of the SET OF tag, rather than of the IMPLICIT
   [2] tag, is to be included in the message digest calculation along
   with the length and content octets of the authAttrs value.

Corrected Text
--------------
   If the authAttrs field is present, the content-type attribute (as
   described in Section 11.1) and the message-digest attribute (as
   described in Section 11.2) MUST be included, and the input to the MAC
   calculation process is the DER encoding of authAttrs.  A separate
   encoding of the authAttrs field is performed for message digest
   calculation.  The IMPLICIT [2] tag in the authAttrs field is not used
   for the DER encoding, rather an EXPLICIT SET OF tag is used.  That
   is, the DER encoding of the SET OF tag, rather than of the IMPLICIT
   [2] tag, is to be included in the MAC calculation along
   with the length and content octets of the authAttrs value.

Notes
-----
The paragraph is talking about the input to a MAC calculation, not the input to message digest calculation.

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. 

--------------------------------------
RFC5652 (draft-ietf-smime-rfc3852bis-00)
--------------------------------------
Title               : Cryptographic Message Syntax (CMS)
Publication Date    : September 2009
Author(s)           : R. Housley
Category            : DRAFT STANDARD
Source              : S/MIME Mail Security
Area                : Security
Stream              : IETF
Verifying Party     : IESG


From nobody Thu Aug  6 16:58:16 2020
Return-Path: <ietf@augustcellars.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 A66BE3A0A0C for <smime@ietfa.amsl.com>; Thu,  6 Aug 2020 16:58:14 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 1q1slHXuJYPg for <smime@ietfa.amsl.com>; Thu,  6 Aug 2020 16:58:13 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B9B223A08FF for <smime@ietf.org>; Thu,  6 Aug 2020 16:58:12 -0700 (PDT)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 6 Aug 2020 16:58:05 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'RFC Errata System' <rfc-editor@rfc-editor.org>, <housley@vigilsec.com>, <rdd@cert.org>, <kaduk@mit.edu>, <paul.hoffman@vpnc.org>, <blaker@gmail.com>
CC: <smime@ietf.org>
References: <20200806215815.240BFF40757@rfc-editor.org>
In-Reply-To: <20200806215815.240BFF40757@rfc-editor.org>
Date: Thu, 6 Aug 2020 16:58:03 -0700
Message-ID: <069201d66c4d$6e994b70$4bcbe250$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-us
Thread-Index: AQFBIBo5eNzWorCSF43k72cqIaNNhqpWWpxQ
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/4eWAVR4Gc1f3W2Zb_IM-I73xJeY>
Subject: Re: [smime] [Technical Errata Reported] RFC5652 (6250)
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 06 Aug 2020 23:58:15 -0000

Look right to me

-----Original Message-----
From: smime <smime-bounces@ietf.org> On Behalf Of RFC Errata System
Sent: Thursday, August 6, 2020 2:58 PM
To: housley@vigilsec.com; rdd@cert.org; kaduk@mit.edu;
paul.hoffman@vpnc.org; blaker@gmail.com
Cc: rfc-editor@rfc-editor.org; smime@ietf.org
Subject: [smime] [Technical Errata Reported] RFC5652 (6250)

The following errata report has been submitted for RFC5652, "Cryptographic
Message Syntax (CMS)".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6250

--------------------------------------
Type: Technical
Reported by: Russ Housley <housley@vigilsec.com>

Section: 9.2

Original Text
-------------
   If the authAttrs field is present, the content-type attribute (as
   described in Section 11.1) and the message-digest attribute (as
   described in Section 11.2) MUST be included, and the input to the MAC
   calculation process is the DER encoding of authAttrs.  A separate
   encoding of the authAttrs field is performed for message digest
   calculation.  The IMPLICIT [2] tag in the authAttrs field is not used
   for the DER encoding, rather an EXPLICIT SET OF tag is used.  That
   is, the DER encoding of the SET OF tag, rather than of the IMPLICIT
   [2] tag, is to be included in the message digest calculation along
   with the length and content octets of the authAttrs value.

Corrected Text
--------------
   If the authAttrs field is present, the content-type attribute (as
   described in Section 11.1) and the message-digest attribute (as
   described in Section 11.2) MUST be included, and the input to the MAC
   calculation process is the DER encoding of authAttrs.  A separate
   encoding of the authAttrs field is performed for message digest
   calculation.  The IMPLICIT [2] tag in the authAttrs field is not used
   for the DER encoding, rather an EXPLICIT SET OF tag is used.  That
   is, the DER encoding of the SET OF tag, rather than of the IMPLICIT
   [2] tag, is to be included in the MAC calculation along
   with the length and content octets of the authAttrs value.

Notes
-----
The paragraph is talking about the input to a MAC calculation, not the input
to message digest calculation.

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. 

--------------------------------------
RFC5652 (draft-ietf-smime-rfc3852bis-00)
--------------------------------------
Title               : Cryptographic Message Syntax (CMS)
Publication Date    : September 2009
Author(s)           : R. Housley
Category            : DRAFT 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


From nobody Thu Aug  6 22:00:53 2020
Return-Path: <wwwrun@rfc-editor.org>
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 53CF03A0901; Thu,  6 Aug 2020 22:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, 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 37L9buTJvUxd; Thu,  6 Aug 2020 22:00:44 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA3DD3A0906; Thu,  6 Aug 2020 22:00:43 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id F1740F4074E; Thu,  6 Aug 2020 22:00:34 -0700 (PDT)
To: housley@vigilsec.com, housley@vigilsec.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: kaduk@mit.edu, iesg@ietf.org, smime@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20200807050034.F1740F4074E@rfc-editor.org>
Date: Thu,  6 Aug 2020 22:00:34 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/yWlu3zhf3QOeSxApAyn2tqpfqL8>
Subject: [smime] [Errata Verified] RFC5652 (6250)
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 07 Aug 2020 05:00:46 -0000

The following errata report has been verified for RFC5652,
"Cryptographic Message Syntax (CMS)". 

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6250

--------------------------------------
Status: Verified
Type: Technical

Reported by: Russ Housley <housley@vigilsec.com>
Date Reported: 2020-08-06
Verified by: Benjamin Kaduk (IESG)

Section: 9.2

Original Text
-------------
   If the authAttrs field is present, the content-type attribute (as
   described in Section 11.1) and the message-digest attribute (as
   described in Section 11.2) MUST be included, and the input to the MAC
   calculation process is the DER encoding of authAttrs.  A separate
   encoding of the authAttrs field is performed for message digest
   calculation.  The IMPLICIT [2] tag in the authAttrs field is not used
   for the DER encoding, rather an EXPLICIT SET OF tag is used.  That
   is, the DER encoding of the SET OF tag, rather than of the IMPLICIT
   [2] tag, is to be included in the message digest calculation along
   with the length and content octets of the authAttrs value.

Corrected Text
--------------
   If the authAttrs field is present, the content-type attribute (as
   described in Section 11.1) and the message-digest attribute (as
   described in Section 11.2) MUST be included, and the input to the MAC
   calculation process is the DER encoding of authAttrs.  A separate
   encoding of the authAttrs field is performed for message digest
   calculation.  The IMPLICIT [2] tag in the authAttrs field is not used
   for the DER encoding, rather an EXPLICIT SET OF tag is used.  That
   is, the DER encoding of the SET OF tag, rather than of the IMPLICIT
   [2] tag, is to be included in the MAC calculation along
   with the length and content octets of the authAttrs value.

Notes
-----
The paragraph is talking about the input to a MAC calculation, not the input to message digest calculation.

--------------------------------------
RFC5652 (draft-ietf-smime-rfc3852bis-00)
--------------------------------------
Title               : Cryptographic Message Syntax (CMS)
Publication Date    : September 2009
Author(s)           : R. Housley
Category            : DRAFT STANDARD
Source              : S/MIME Mail Security
Area                : Security
Stream              : IETF
Verifying Party     : IESG


From nobody Fri Aug  7 05:15:26 2020
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 AA52F3A0B71 for <smime@ietfa.amsl.com>; Fri,  7 Aug 2020 05:15:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 jZhV62LCaXNi for <smime@ietfa.amsl.com>; Fri,  7 Aug 2020 05:15:22 -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 B1E9B3A0B3D for <smime@ietf.org>; Fri,  7 Aug 2020 05:15:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 4AF41300B50 for <smime@ietf.org>; Fri,  7 Aug 2020 08:15:20 -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 woUWNwpPfeyk for <smime@ietf.org>; Fri,  7 Aug 2020 08:15:18 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 81D26300AA6 for <smime@ietf.org>; Fri,  7 Aug 2020 08:15:18 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_93F060D0-28E3-474C-9468-153BA797B334"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.15\))
Message-Id: <67C56FED-EEC3-401D-829A-72C4A253E6BF@vigilsec.com>
References: <20200807050034.F1740F4074E@rfc-editor.org>
To: IETF SMIME <smime@ietf.org>
Date: Fri, 7 Aug 2020 08:15:20 -0400
X-Mailer: Apple Mail (2.3445.104.15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/N0_LMQAyJzyTyXgkoEJac-O6Dyg>
Subject: [smime] [lamps] Fwd: [Errata Verified] RFC5652 (6250)
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 07 Aug 2020 12:15:25 -0000

--Apple-Mail=_93F060D0-28E3-474C-9468-153BA797B334
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii



> From: RFC Errata System <rfc-editor@rfc-editor.org =
<mailto:rfc-editor@rfc-editor.org>>
> Subject: [Errata Verified] RFC5652 (6250)
> Date: August 7, 2020 at 1:00:34 AM EDT
> To: housley@vigilsec.com <mailto:housley@vigilsec.com>, =
housley@vigilsec.com <mailto:housley@vigilsec.com>
> Cc: kaduk@mit.edu <mailto:kaduk@mit.edu>, iesg@ietf.org =
<mailto:iesg@ietf.org>, smime@ietf.org <mailto:smime@ietf.org>, =
rfc-editor@rfc-editor.org <mailto:rfc-editor@rfc-editor.org>
>=20
> The following errata report has been verified for RFC5652,
> "Cryptographic Message Syntax (CMS)".=20
>=20
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6250 =
<https://www.rfc-editor.org/errata/eid6250>
>=20
> --------------------------------------
> Status: Verified
> Type: Technical
>=20
> Reported by: Russ Housley <housley@vigilsec.com>
> Date Reported: 2020-08-06
> Verified by: Benjamin Kaduk (IESG)
>=20
> Section: 9.2
>=20
> Original Text
> -------------
>   If the authAttrs field is present, the content-type attribute (as
>   described in Section 11.1) and the message-digest attribute (as
>   described in Section 11.2) MUST be included, and the input to the =
MAC
>   calculation process is the DER encoding of authAttrs.  A separate
>   encoding of the authAttrs field is performed for message digest
>   calculation.  The IMPLICIT [2] tag in the authAttrs field is not =
used
>   for the DER encoding, rather an EXPLICIT SET OF tag is used.  That
>   is, the DER encoding of the SET OF tag, rather than of the IMPLICIT
>   [2] tag, is to be included in the message digest calculation along
>   with the length and content octets of the authAttrs value.
>=20
> Corrected Text
> --------------
>   If the authAttrs field is present, the content-type attribute (as
>   described in Section 11.1) and the message-digest attribute (as
>   described in Section 11.2) MUST be included, and the input to the =
MAC
>   calculation process is the DER encoding of authAttrs.  A separate
>   encoding of the authAttrs field is performed for message digest
>   calculation.  The IMPLICIT [2] tag in the authAttrs field is not =
used
>   for the DER encoding, rather an EXPLICIT SET OF tag is used.  That
>   is, the DER encoding of the SET OF tag, rather than of the IMPLICIT
>   [2] tag, is to be included in the MAC calculation along
>   with the length and content octets of the authAttrs value.
>=20
> Notes
> -----
> The paragraph is talking about the input to a MAC calculation, not the =
input to message digest calculation.
>=20
> --------------------------------------
> RFC5652 (draft-ietf-smime-rfc3852bis-00)
> --------------------------------------
> Title               : Cryptographic Message Syntax (CMS)
> Publication Date    : September 2009
> Author(s)           : R. Housley
> Category            : DRAFT STANDARD
> Source              : S/MIME Mail Security
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG



--Apple-Mail=_93F060D0-28E3-474C-9468-153BA797B334
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><meta=
 http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii" =
class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; line-break: after-white-space;" class=3D""><br class=3D""><div =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D""><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">From: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">RFC Errata System &lt;<a =
href=3D"mailto:rfc-editor@rfc-editor.org" =
class=3D"">rfc-editor@rfc-editor.org</a>&gt;<br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Subject: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><b class=3D"">[Errata Verified] =
RFC5652 (6250)</b><br class=3D""></span></div><div style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" =
class=3D""><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b =
class=3D"">Date: </b></span><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" =
class=3D"">August 7, 2020 at 1:00:34 AM EDT<br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">To: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><a =
href=3D"mailto:housley@vigilsec.com" class=3D"">housley@vigilsec.com</a>, =
<a href=3D"mailto:housley@vigilsec.com" =
class=3D"">housley@vigilsec.com</a><br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Cc: </b></span><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif;" class=3D""><a href=3D"mailto:kaduk@mit.edu" =
class=3D"">kaduk@mit.edu</a>, <a href=3D"mailto:iesg@ietf.org" =
class=3D"">iesg@ietf.org</a>, <a href=3D"mailto:smime@ietf.org" =
class=3D"">smime@ietf.org</a>, <a =
href=3D"mailto:rfc-editor@rfc-editor.org" =
class=3D"">rfc-editor@rfc-editor.org</a><br class=3D""></span></div><br =
class=3D""><div class=3D""><div class=3D"">The following errata report =
has been verified for RFC5652,<br class=3D"">"Cryptographic Message =
Syntax (CMS)". <br class=3D""><br =
class=3D"">--------------------------------------<br class=3D"">You may =
review the report below and at:<br class=3D""><a =
href=3D"https://www.rfc-editor.org/errata/eid6250" =
class=3D"">https://www.rfc-editor.org/errata/eid6250</a><br class=3D""><br=
 class=3D"">--------------------------------------<br class=3D"">Status: =
Verified<br class=3D"">Type: Technical<br class=3D""><br =
class=3D"">Reported by: Russ Housley &lt;<a =
href=3D"mailto:housley@vigilsec.com" =
class=3D"">housley@vigilsec.com</a>&gt;<br class=3D"">Date Reported: =
2020-08-06<br class=3D"">Verified by: Benjamin Kaduk (IESG)<br =
class=3D""><br class=3D"">Section: 9.2<br class=3D""><br =
class=3D"">Original Text<br class=3D"">-------------<br class=3D""> =
&nbsp;&nbsp;If the authAttrs field is present, the content-type =
attribute (as<br class=3D""> &nbsp;&nbsp;described in Section 11.1) and =
the message-digest attribute (as<br class=3D""> &nbsp;&nbsp;described in =
Section 11.2) MUST be included, and the input to the MAC<br class=3D""> =
&nbsp;&nbsp;calculation process is the DER encoding of authAttrs. =
&nbsp;A separate<br class=3D""> &nbsp;&nbsp;encoding of the authAttrs =
field is performed for message digest<br class=3D""> =
&nbsp;&nbsp;calculation. &nbsp;The IMPLICIT [2] tag in the authAttrs =
field is not used<br class=3D""> &nbsp;&nbsp;for the DER encoding, =
rather an EXPLICIT SET OF tag is used. &nbsp;That<br class=3D""> =
&nbsp;&nbsp;is, the DER encoding of the SET OF tag, rather than of the =
IMPLICIT<br class=3D""> &nbsp;&nbsp;[2] tag, is to be included in the =
message digest calculation along<br class=3D""> &nbsp;&nbsp;with the =
length and content octets of the authAttrs value.<br class=3D""><br =
class=3D"">Corrected Text<br class=3D"">--------------<br class=3D""> =
&nbsp;&nbsp;If the authAttrs field is present, the content-type =
attribute (as<br class=3D""> &nbsp;&nbsp;described in Section 11.1) and =
the message-digest attribute (as<br class=3D""> &nbsp;&nbsp;described in =
Section 11.2) MUST be included, and the input to the MAC<br class=3D""> =
&nbsp;&nbsp;calculation process is the DER encoding of authAttrs. =
&nbsp;A separate<br class=3D""> &nbsp;&nbsp;encoding of the authAttrs =
field is performed for message digest<br class=3D""> =
&nbsp;&nbsp;calculation. &nbsp;The IMPLICIT [2] tag in the authAttrs =
field is not used<br class=3D""> &nbsp;&nbsp;for the DER encoding, =
rather an EXPLICIT SET OF tag is used. &nbsp;That<br class=3D""> =
&nbsp;&nbsp;is, the DER encoding of the SET OF tag, rather than of the =
IMPLICIT<br class=3D""> &nbsp;&nbsp;[2] tag, is to be included in the =
MAC calculation along<br class=3D""> &nbsp;&nbsp;with the length and =
content octets of the authAttrs value.<br class=3D""><br =
class=3D"">Notes<br class=3D"">-----<br class=3D"">The paragraph is =
talking about the input to a MAC calculation, not the input to message =
digest calculation.<br class=3D""><br =
class=3D"">--------------------------------------<br class=3D"">RFC5652 =
(draft-ietf-smime-rfc3852bis-00)<br =
class=3D"">--------------------------------------<br class=3D"">Title =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;: Cryptographic Message Syntax (CMS)<br class=3D"">Publication =
Date &nbsp;&nbsp;&nbsp;: September 2009<br class=3D"">Author(s) =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: R. =
Housley<br class=3D"">Category =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;: =
DRAFT STANDARD<br class=3D"">Source =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;: S/MIME Mail Security<br class=3D"">Area =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;: Security<br class=3D"">Stream =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;: IETF<br class=3D"">Verifying Party &nbsp;&nbsp;&nbsp;&nbsp;: =
IESG<br class=3D""></div></div></blockquote></div><br class=3D""></div><br=
 class=3D""></body></html>=

--Apple-Mail=_93F060D0-28E3-474C-9468-153BA797B334--

