
From nobody Tue Apr 13 12:34:11 2021
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 CBD0C3A2491 for <smime@ietfa.amsl.com>; Tue, 13 Apr 2021 12:34:09 -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 EiftAWQh10ot for <smime@ietfa.amsl.com>; Tue, 13 Apr 2021 12:34:05 -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 47AA63A248D for <smime@ietf.org>; Tue, 13 Apr 2021 12:34:05 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E0B0CF407C6; Tue, 13 Apr 2021 12:33:51 -0700 (PDT)
To: sblakewi@certicom.com, dbrown@certicom.com, plambert@sprintmail.com, rdd@cert.org, kaduk@mit.edu, paul.hoffman@vpnc.org, blaker@gmail.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: juli@clockworksquid.com, smime@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20210413193351.E0B0CF407C6@rfc-editor.org>
Date: Tue, 13 Apr 2021 12:33:51 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/ugHkYntdmEhSwOdCJkN_tg57qW4>
Subject: [smime] [Editorial Errata Reported] RFC3278 (6542)
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: Tue, 13 Apr 2021 19:34:10 -0000

The following errata report has been submitted for RFC3278,
"Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)".

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

--------------------------------------
Type: Editorial
Reported by: Juli Mallett <juli@clockworksquid.com>

Section: GLOBAL

Original Text
-------------
   4  AuthenticatedData using ECC ............ ......................  8

Corrected Text
--------------
   4  AuthenticatedData using ECC ...................................  8

Notes
-----
Incorrect space in justification.

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. 

--------------------------------------
RFC3278 (draft-ietf-smime-ecc-06)
--------------------------------------
Title               : Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)
Publication Date    : April 2002
Author(s)           : S. Blake-Wilson, D. Brown, P. Lambert
Category            : INFORMATIONAL
Source              : S/MIME Mail Security
Area                : Security
Stream              : IETF
Verifying Party     : IESG


From nobody Tue Apr 13 13:31:24 2021
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 785BE3A0A27 for <smime@ietfa.amsl.com>; Tue, 13 Apr 2021 13:31:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 m6zTk5BqVlW3 for <smime@ietfa.amsl.com>; Tue, 13 Apr 2021 13:31:18 -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 4F1433A0A25 for <smime@ietf.org>; Tue, 13 Apr 2021 13:31:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 3244B300B43 for <smime@ietf.org>; Tue, 13 Apr 2021 16:31:15 -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 ZyvfhILyxhax for <smime@ietf.org>; Tue, 13 Apr 2021 16:31:13 -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 24C2F30026C; Tue, 13 Apr 2021 16:31:13 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20210413193351.E0B0CF407C6@rfc-editor.org>
Date: Tue, 13 Apr 2021 16:31:14 -0400
Cc: Blake Ramsdell <blaker@gmail.com>, juli@clockworksquid.com, IETF SMIME <smime@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E0099A0-EC32-4EB6-8CD7-C69D56366B97@vigilsec.com>
References: <20210413193351.E0B0CF407C6@rfc-editor.org>
To: "Roman D. Danyliw" <rdd@cert.org>, Ben Kaduk <kaduk@mit.edu>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/LzRewZxHHt5wJNAR6nPMI8bMXqw>
Subject: Re: [smime] [Editorial Errata Reported] RFC3278 (6542)
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: Tue, 13 Apr 2021 20:31:24 -0000

I recommend Hold for Document Update.  I do not think this error will =
confuse anyone trying to implement the protocol.

Russ

> On Apr 13, 2021, at 3:33 PM, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:
>=20
> The following errata report has been submitted for RFC3278,
> "Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic =
Message Syntax (CMS)".
>=20
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6542
>=20
> --------------------------------------
> Type: Editorial
> Reported by: Juli Mallett <juli@clockworksquid.com>
>=20
> Section: GLOBAL
>=20
> Original Text
> -------------
>   4  AuthenticatedData using ECC ............ ......................  =
8
>=20
> Corrected Text
> --------------
>   4  AuthenticatedData using ECC ...................................  =
8
>=20
> Notes
> -----
> Incorrect space in justification.
>=20
> 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 =20
> can log in to change the status and edit the report, if necessary.=20
>=20
> --------------------------------------
> RFC3278 (draft-ietf-smime-ecc-06)
> --------------------------------------
> Title               : Use of Elliptic Curve Cryptography (ECC) =
Algorithms in Cryptographic Message Syntax (CMS)
> Publication Date    : April 2002
> Author(s)           : S. Blake-Wilson, D. Brown, P. Lambert
> Category            : INFORMATIONAL
> Source              : S/MIME Mail Security
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG
>=20
> _______________________________________________
> smime mailing list
> smime@ietf.org
> https://www.ietf.org/mailman/listinfo/smime


From nobody Wed Apr 14 12:36:19 2021
Return-Path: <sean@sn3rd.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 785FB3A1CF1 for <smime@ietfa.amsl.com>; Wed, 14 Apr 2021 12:36:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.com
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 l4SBSejMslgt for <smime@ietfa.amsl.com>; Wed, 14 Apr 2021 12:36:11 -0700 (PDT)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF2BF3A1CED for <smime@ietf.org>; Wed, 14 Apr 2021 12:36:11 -0700 (PDT)
Received: by mail-qt1-x835.google.com with SMTP id y12so16363587qtx.11 for <smime@ietf.org>; Wed, 14 Apr 2021 12:36:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=9t7RGPcj0iLKjJs1UXFjy736oc7BVfpRr/Wh7p5sUoM=; b=hsb7K18jailozMARf9bShCBC2/n5NGRp8ZRFbgVia3iMYasS1O4A3e4JzYOVgcIrtu VFM3NJd52V0Or82pJ+Go3A2InC0igIxwXv2tG54NGM6AvAIeHV13dvy3YVud7IVWBGmC fwh0ZktlqCYlB2heIPCV+wVJku+JA0zVO/91w=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=9t7RGPcj0iLKjJs1UXFjy736oc7BVfpRr/Wh7p5sUoM=; b=TUaX/hccZ4pf4+F9jtRNYl63vHoOtAbEtDqcm7AYROLI9PesM59v+3gwgb5k+1Ww/2 fobzg2AiwYMxrlUU4ZkcEYc0oHisrdfIZCcBTEo2m0Np/GjSyiWDbSZXs9419dNPltDX v/WcEfX68DPEwWLsrtblqLgYhcGsAgQxhRmzskDYCVuxloXAzxTD6iLCV9qk+VoVLwvi XL+tzKuuyhPTulID3tDFdqjhGWd4SIUjeP/a80Lwh3WqEWVAVLkE5Ngdg8JczCcwUiDN IPT9op4agNW6XOLcKyz0UFddLwGO1CAS6bv8KKHvQawUSaUzO62/1vwQMO2jmmnRWMF6 dJkw==
X-Gm-Message-State: AOAM531jDFPU3pRWr5SB4Sw7ohJplD2xPqaMogI5qoL+RsvGY9XjblPw EORCva2H6x+eLIFOS2EXw7htZQ==
X-Google-Smtp-Source: ABdhPJx7m2rxPN9+amUP/ixMr8UhUbjKC62MGUf+7AQNWRgIZYVZTKaAMLlQ5SkOs2CKJYZeVWjtIw==
X-Received: by 2002:ac8:588e:: with SMTP id t14mr35681654qta.123.1618428969835;  Wed, 14 Apr 2021 12:36:09 -0700 (PDT)
Received: from [192.168.1.152] (pool-71-178-177-131.washdc.fios.verizon.net. [71.178.177.131]) by smtp.gmail.com with ESMTPSA id v192sm304034qkb.83.2021.04.14.12.36.09 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Apr 2021 12:36:09 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <5E0099A0-EC32-4EB6-8CD7-C69D56366B97@vigilsec.com>
Date: Wed, 14 Apr 2021 15:36:08 -0400
Cc: Roman Danyliw <rdd@cert.org>, Benjamin Kaduk <kaduk@mit.edu>, juli@clockworksquid.com, IETF SMIME <smime@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E79703D-497A-4607-A2CF-56DD471CA674@sn3rd.com>
References: <20210413193351.E0B0CF407C6@rfc-editor.org> <5E0099A0-EC32-4EB6-8CD7-C69D56366B97@vigilsec.com>
To: Russ Housley <housley@vigilsec.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/i9nKnUT12a48AQHBtNi6O_v1AT0>
Subject: Re: [smime] [Editorial Errata Reported] RFC3278 (6542)
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: Wed, 14 Apr 2021 19:36:18 -0000

yes ;)

> On Apr 13, 2021, at 16:31, Russ Housley <housley@vigilsec.com> wrote:
>=20
> I recommend Hold for Document Update.  I do not think this error will =
confuse anyone trying to implement the protocol.
>=20
> Russ
>=20
>> On Apr 13, 2021, at 3:33 PM, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:
>>=20
>> The following errata report has been submitted for RFC3278,
>> "Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic =
Message Syntax (CMS)".
>>=20
>> --------------------------------------
>> You may review the report below and at:
>> https://www.rfc-editor.org/errata/eid6542
>>=20
>> --------------------------------------
>> Type: Editorial
>> Reported by: Juli Mallett <juli@clockworksquid.com>
>>=20
>> Section: GLOBAL
>>=20
>> Original Text
>> -------------
>>  4  AuthenticatedData using ECC ............ ......................  =
8
>>=20
>> Corrected Text
>> --------------
>>  4  AuthenticatedData using ECC ...................................  =
8
>>=20
>> Notes
>> -----
>> Incorrect space in justification.
>>=20
>> 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 =20
>> can log in to change the status and edit the report, if necessary.=20
>>=20
>> --------------------------------------
>> RFC3278 (draft-ietf-smime-ecc-06)
>> --------------------------------------
>> Title               : Use of Elliptic Curve Cryptography (ECC) =
Algorithms in Cryptographic Message Syntax (CMS)
>> Publication Date    : April 2002
>> Author(s)           : S. Blake-Wilson, D. Brown, P. Lambert
>> Category            : INFORMATIONAL
>> Source              : S/MIME Mail Security
>> Area                : Security
>> Stream              : IETF
>> Verifying Party     : IESG
>>=20
>> _______________________________________________
>> smime mailing list
>> smime@ietf.org
>> https://www.ietf.org/mailman/listinfo/smime
>=20
> _______________________________________________
> smime mailing list
> smime@ietf.org
> https://www.ietf.org/mailman/listinfo/smime


From nobody Wed Apr 14 17:58:25 2021
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 8000D3A2703; Wed, 14 Apr 2021 17:58:23 -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, RCVD_IN_DNSWL_BLOCKED=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 NDTGOWEaiAZu; Wed, 14 Apr 2021 17:58:19 -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 E029C3A26FB; Wed, 14 Apr 2021 17:58:18 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 8C0EEF40783; Wed, 14 Apr 2021 17:58:04 -0700 (PDT)
To: juli@clockworksquid.com, sblakewi@certicom.com, dbrown@certicom.com, plambert@sprintmail.com
X-PHP-Originating-Script: 1005: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: <20210415005804.8C0EEF40783@rfc-editor.org>
Date: Wed, 14 Apr 2021 17:58:04 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/zTgcoB2tnHg7GpAF0_-uH9cmROk>
Subject: [smime] [Errata Held for Document Update] RFC3278 (6542)
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, 15 Apr 2021 00:58:24 -0000

The following errata report has been held for document update 
for RFC3278, "Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)". 

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

--------------------------------------
Status: Held for Document Update
Type: Editorial

Reported by: Juli Mallett <juli@clockworksquid.com>
Date Reported: 2021-04-13
Held by: Benjamin Kaduk (IESG)

Section: GLOBAL

Original Text
-------------
   4  AuthenticatedData using ECC ............ ......................  8

Corrected Text
--------------
   4  AuthenticatedData using ECC ...................................  8

Notes
-----
Incorrect space in justification.

--------------------------------------
RFC3278 (draft-ietf-smime-ecc-06)
--------------------------------------
Title               : Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)
Publication Date    : April 2002
Author(s)           : S. Blake-Wilson, D. Brown, P. Lambert
Category            : INFORMATIONAL
Source              : S/MIME Mail Security
Area                : Security
Stream              : IETF
Verifying Party     : IESG


From nobody Thu Apr 15 11:19:12 2021
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 881F13A29D0 for <smime@ietfa.amsl.com>; Thu, 15 Apr 2021 11:19:10 -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 1O0Em0GuER8W for <smime@ietfa.amsl.com>; Thu, 15 Apr 2021 11:19:06 -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 04AD03A29CF for <smime@ietf.org>; Thu, 15 Apr 2021 11:19:05 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E8E93F407BD; Thu, 15 Apr 2021 11:18:50 -0700 (PDT)
To: housley@vigilsec.com, rdd@cert.org, kaduk@mit.edu, paul.hoffman@vpnc.org,  blaker@gmail.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: dkg@fifthhorseman.net, smime@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20210415181850.E8E93F407BD@rfc-editor.org>
Date: Thu, 15 Apr 2021 11:18:50 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/NJF7Tr9fcT-MlVTR-lHdtTnuolk>
Subject: [smime] [Editorial Errata Reported] RFC5652 (6546)
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, 15 Apr 2021 18:19:11 -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/eid6546

--------------------------------------
Type: Editorial
Reported by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>

Section: 12.1

Original Text
-------------
  -- Imports from Appendix B of this document
           AttributeCertificateV1
              FROM AttributeCertificateVersion1

Corrected Text
--------------
  -- Imports from Section 12.2 of this document
           AttributeCertificateV1
              FROM AttributeCertificateVersion1

Notes
-----
The AttributeCertificateVersion1 is defined in section 12.2; there is no Appendix B in this document.

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 Apr 15 11:24:38 2021
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 184B73A2A09 for <smime@ietfa.amsl.com>; Thu, 15 Apr 2021 11:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 DMXKtK_q9p0v for <smime@ietfa.amsl.com>; Thu, 15 Apr 2021 11:24:31 -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 632703A2A05 for <smime@ietf.org>; Thu, 15 Apr 2021 11:24:31 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id C563F300B82 for <smime@ietf.org>; Thu, 15 Apr 2021 14:24:28 -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 4caNTt6TlYcu for <smime@ietf.org>; Thu, 15 Apr 2021 14:24:26 -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 7E12F300261; Thu, 15 Apr 2021 14:24:26 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20210415181850.E8E93F407BD@rfc-editor.org>
Date: Thu, 15 Apr 2021 14:24:27 -0400
Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, IETF SMIME <smime@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <41657C9B-A198-44BD-952C-4C53A2CA3CCF@vigilsec.com>
References: <20210415181850.E8E93F407BD@rfc-editor.org>
To: "Roman D. Danyliw" <rdd@cert.org>, Ben Kaduk <kaduk@mit.edu>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/rE5wQmav2-a7RK-dB9SIjUkGO9k>
Subject: Re: [smime] [Editorial Errata Reported] RFC5652 (6546)
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, 15 Apr 2021 18:24:36 -0000

This looks correct to me.  Please accept and approve.

Russ


> On Apr 15, 2021, at 2:18 PM, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:
>=20
> The following errata report has been submitted for RFC5652,
> "Cryptographic Message Syntax (CMS)".
>=20
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6546
>=20
> --------------------------------------
> Type: Editorial
> Reported by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
>=20
> Section: 12.1
>=20
> Original Text
> -------------
>  -- Imports from Appendix B of this document
>           AttributeCertificateV1
>              FROM AttributeCertificateVersion1
>=20
> Corrected Text
> --------------
>  -- Imports from Section 12.2 of this document
>           AttributeCertificateV1
>              FROM AttributeCertificateVersion1
>=20
> Notes
> -----
> The AttributeCertificateVersion1 is defined in section 12.2; there is =
no Appendix B in this document.
>=20
> 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 =20
> can log in to change the status and edit the report, if necessary.=20
>=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


From nobody Thu Apr 15 11:32:59 2021
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 A76063A2A44; Thu, 15 Apr 2021 11:32:54 -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 V7Z3eXSQtLbu; Thu, 15 Apr 2021 11:32:50 -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 0ABA33A2A3D; Thu, 15 Apr 2021 11:32:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id EB3C7F407BD; Thu, 15 Apr 2021 11:32:34 -0700 (PDT)
To: dkg@fifthhorseman.net, housley@vigilsec.com
X-PHP-Originating-Script: 1005: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: <20210415183234.EB3C7F407BD@rfc-editor.org>
Date: Thu, 15 Apr 2021 11:32:34 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/MMxWvQGG_H-NYI7YdpYAqZKcSiM>
Subject: [smime] [Errata Verified] RFC5652 (6546)
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, 15 Apr 2021 18:32:55 -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/eid6546

--------------------------------------
Status: Verified
Type: Editorial

Reported by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Date Reported: 2021-04-15
Verified by: Benjamin Kaduk (IESG)

Section: 12.1

Original Text
-------------
  -- Imports from Appendix B of this document
           AttributeCertificateV1
              FROM AttributeCertificateVersion1

Corrected Text
--------------
  -- Imports from Section 12.2 of this document
           AttributeCertificateV1
              FROM AttributeCertificateVersion1

Notes
-----
The AttributeCertificateVersion1 is defined in section 12.2; there is no Appendix B in this document.

--------------------------------------
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 Wed Apr 28 11:08:03 2021
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 C0DBC3A198D for <smime@ietfa.amsl.com>; Wed, 28 Apr 2021 11:08:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 VwKWP1nixEmV for <smime@ietfa.amsl.com>; Wed, 28 Apr 2021 11:07:57 -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 489973A1996 for <smime@ietf.org>; Wed, 28 Apr 2021 11:07:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7B3D3F407B3; Wed, 28 Apr 2021 11:07:43 -0700 (PDT)
To: phoffman@imc.org, rdd@cert.org, kaduk@mit.edu, paul.hoffman@vpnc.org, blaker@gmail.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: David.von.Oheimb@siemens.com, smime@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20210428180743.7B3D3F407B3@rfc-editor.org>
Date: Wed, 28 Apr 2021 11:07:43 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/7_jJ7oiShtzuz-WGEWl6xPR6y8Q>
Subject: [smime] [Technical Errata Reported] RFC2634 (6562)
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: Wed, 28 Apr 2021 18:08:02 -0000

The following errata report has been submitted for RFC2634,
"Enhanced Security Services for S/MIME".

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

--------------------------------------
Type: Technical
Reported by: David von Oheimb <David.von.Oheimb@siemens.com>

Section: 5.4

Original Text
-------------
   The first certificate identified in the sequence of certificate
   identifiers MUST be the certificate used to verify the signature. The
   encoding of the ESSCertID for this certificate SHOULD include the
   issuerSerial field. If other constraints ensure that
   issuerAndSerialNumber will be present in the SignerInfo, the
   issuerSerial field MAY be omitted. The certificate identified is used
   during the signature verification process. If the hash of the
   certificate does not match the certificate used to verify the
   signature, the signature MUST be considered invalid.

   If more than one certificate is present in the sequence of
   ESSCertIDs, the certificates after the first one limit the set of
   authorization certificates that are used during signature validation.


Corrected Text
--------------
   The sequence of certificate identifiers MUST contain at least one element.
   The first certificate identified MUST be the certificate used to verify the signature.
   The encoding of the ESSCertID for this certificate SHOULD include the
   issuerSerial field. If other constraints ensure that
   issuerAndSerialNumber will be present in the SignerInfo, the
   issuerSerial field MAY be omitted. The certificate identified is used
   during the signature verification process. If the hash of the
   certificate does not match the certificate used to verify the
   signature, the signature MUST be considered invalid.

   If more than one certificate identifier is present in the sequence of ESSCertIDs,
   all certificates referenced there MUST be part of the signature validation chain.


Notes
-----
Some aspects of the 'certs' field of a SigningCertificate attribute:

   SigningCertificate ::=  SEQUENCE {
       certs        SEQUENCE OF ESSCertID,
       policies     SEQUENCE OF PolicyInformation OPTIONAL
   }

described in the sentences quoted above are very vague.
This lead to major confusion and wrong implementations.
As meanwhile has been clarified, they should be re-phrased;
see suggested new version above.

(One may further mandate/clarify that the certificate identifiers must be given in the same order
as they are expected in the validation chain, but I think this is not important because
the order should not play a critical role and will be determined by the validation chain anyway.)

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. 

--------------------------------------
RFC2634 (draft-ietf-smime-ess-12)
--------------------------------------
Title               : Enhanced Security Services for S/MIME
Publication Date    : June 1999
Author(s)           : P. Hoffman, Ed.
Category            : PROPOSED STANDARD
Source              : S/MIME Mail Security
Area                : Security
Stream              : IETF
Verifying Party     : IESG


From nobody Wed Apr 28 11:10:41 2021
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 9236A3A19B9 for <smime@ietfa.amsl.com>; Wed, 28 Apr 2021 11:10:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 UYoK4d8CLTJK for <smime@ietfa.amsl.com>; Wed, 28 Apr 2021 11:10:35 -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 2DB5C3A19AA for <smime@ietf.org>; Wed, 28 Apr 2021 11:10:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7FCD6F407AF; Wed, 28 Apr 2021 11:10:21 -0700 (PDT)
To: phoffman@imc.org, rdd@cert.org, kaduk@mit.edu, paul.hoffman@vpnc.org, blaker@gmail.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: David.von.Oheimb@siemens.com, smime@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20210428181021.7FCD6F407AF@rfc-editor.org>
Date: Wed, 28 Apr 2021 11:10:21 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/3WAYknwqksLQ05v6gr9o8d9BWc0>
Subject: [smime] [Technical Errata Reported] RFC2634 (6563)
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: Wed, 28 Apr 2021 18:10:40 -0000

The following errata report has been submitted for RFC2634,
"Enhanced Security Services for S/MIME".

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

--------------------------------------
Type: Technical
Reported by: David von Oheimb <David.von.Oheimb@siemens.com>

Section: 3

Original Text
-------------

   certs
      contains the list of certificates that are to be used in
      validating the message.  The first certificate identified in the
      sequence of certificate identifiers MUST be the certificate used
      to verify the signature.  The encoding of the ESSCertIDv2 for this
      certificate SHOULD include the issuerSerial field.  If other
      constraints ensure that issuerAndSerialNumber will be present in
      the SignerInfo, the issuerSerial field MAY be omitted.  The
      certificate identified is used during the signature verification
      process.  If the hash of the certificate does not match the
      certificate used to verify the signature, the signature MUST be
      considered invalid.

      If more than one certificate is present, subsequent certificates
      limit the set of certificates that are used during validation.

Corrected Text
--------------

   certs
      contains the list of certificates that are to be used in
      validating the message. It MUST contain at least one element.
      The first certificate identified in the
      sequence of certificate identifiers MUST be the certificate used
      to verify the signature.  The encoding of the ESSCertIDv2 for this
      certificate SHOULD include the issuerSerial field.  If other
      constraints ensure that issuerAndSerialNumber will be present in
      the SignerInfo, the issuerSerial field MAY be omitted.  The
      certificate identified is used during the signature verification
      process.  If the hash of the certificate does not match the
      certificate used to verify the signature, the signature MUST be
      considered invalid.

      If more than one certificate identifier is present in the sequence of ESSCertIDv2s,
      all certificates referenced there MUST be part of the signature validation chain.

Notes
-----
Some aspects of the 'certs' field of a SigningCertificateV2 attribute:

   SigningCertificateV2 ::=  SEQUENCE {
       certs        SEQUENCE OF ESSCertIDv2,
       policies     SEQUENCE OF PolicyInformation OPTIONAL
   }

described in the sentences quoted above are rather vague.
This lead to major confusion and wrong implementations.
As meanwhile has been clarified, they should be re-phrased;
see suggested new version above.

(One may further mandate/clarify that the certificate identifiers must be given in the same order
as they are expected in the validation chain, but I think this is not important because
the order should not play a critical role and will be determined by the validation chain anyway.)

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. 

--------------------------------------
RFC2634 (draft-ietf-smime-ess-12)
--------------------------------------
Title               : Enhanced Security Services for S/MIME
Publication Date    : June 1999
Author(s)           : P. Hoffman, Ed.
Category            : PROPOSED STANDARD
Source              : S/MIME Mail Security
Area                : Security
Stream              : IETF
Verifying Party     : IESG


From nobody Wed Apr 28 12:06:47 2021
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 DBA4D3A1BB4 for <smime@ietfa.amsl.com>; Wed, 28 Apr 2021 12:06:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 nNKAxXbkZpNQ for <smime@ietfa.amsl.com>; Wed, 28 Apr 2021 12:06:42 -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 25F283A1BB6 for <smime@ietf.org>; Wed, 28 Apr 2021 12:06:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id E6065300B9C for <smime@ietf.org>; Wed, 28 Apr 2021 15:06:39 -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 XkyvL_Fa2g9P for <smime@ietf.org>; Wed, 28 Apr 2021 15:06:33 -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 D478C300AE5; Wed, 28 Apr 2021 15:06:32 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.20\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20210428180743.7B3D3F407B3@rfc-editor.org>
Date: Wed, 28 Apr 2021 15:06:32 -0400
Cc: David.von.Oheimb@siemens.com, IETF SMIME <smime@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <71F42520-97DE-4408-82DF-D2032C4696FB@vigilsec.com>
References: <20210428180743.7B3D3F407B3@rfc-editor.org>
To: "Roman D. Danyliw" <rdd@cert.org>, Ben Kaduk <kaduk@mit.edu>
X-Mailer: Apple Mail (2.3445.104.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/-osXO7lkPzJlmm0mSymCz5DWees>
Subject: Re: [smime] [Technical Errata Reported] RFC2634 (6562)
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: Wed, 28 Apr 2021 19:06:47 -0000

Roman and Ben:

This was discussed on the mail list, and people agree that the proposed =
text adds clarity.  I think that the MUST in the first sentence was =
implied, but others think otherwise.  I recommend approving this one.

Russ


> On Apr 28, 2021, at 2:07 PM, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:
>=20
> The following errata report has been submitted for RFC2634,
> "Enhanced Security Services for S/MIME".
>=20
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6562
>=20
> --------------------------------------
> Type: Technical
> Reported by: David von Oheimb <David.von.Oheimb@siemens.com>
>=20
> Section: 5.4
>=20
> Original Text
> -------------
>   The first certificate identified in the sequence of certificate
>   identifiers MUST be the certificate used to verify the signature. =
The
>   encoding of the ESSCertID for this certificate SHOULD include the
>   issuerSerial field. If other constraints ensure that
>   issuerAndSerialNumber will be present in the SignerInfo, the
>   issuerSerial field MAY be omitted. The certificate identified is =
used
>   during the signature verification process. If the hash of the
>   certificate does not match the certificate used to verify the
>   signature, the signature MUST be considered invalid.
>=20
>   If more than one certificate is present in the sequence of
>   ESSCertIDs, the certificates after the first one limit the set of
>   authorization certificates that are used during signature =
validation.
>=20
>=20
> Corrected Text
> --------------
>   The sequence of certificate identifiers MUST contain at least one =
element.
>   The first certificate identified MUST be the certificate used to =
verify the signature.
>   The encoding of the ESSCertID for this certificate SHOULD include =
the
>   issuerSerial field. If other constraints ensure that
>   issuerAndSerialNumber will be present in the SignerInfo, the
>   issuerSerial field MAY be omitted. The certificate identified is =
used
>   during the signature verification process. If the hash of the
>   certificate does not match the certificate used to verify the
>   signature, the signature MUST be considered invalid.
>=20
>   If more than one certificate identifier is present in the sequence =
of ESSCertIDs,
>   all certificates referenced there MUST be part of the signature =
validation chain.
>=20
>=20
> Notes
> -----
> Some aspects of the 'certs' field of a SigningCertificate attribute:
>=20
>   SigningCertificate ::=3D  SEQUENCE {
>       certs        SEQUENCE OF ESSCertID,
>       policies     SEQUENCE OF PolicyInformation OPTIONAL
>   }
>=20
> described in the sentences quoted above are very vague.
> This lead to major confusion and wrong implementations.
> As meanwhile has been clarified, they should be re-phrased;
> see suggested new version above.
>=20
> (One may further mandate/clarify that the certificate identifiers must =
be given in the same order
> as they are expected in the validation chain, but I think this is not =
important because
> the order should not play a critical role and will be determined by =
the validation chain anyway.)
>=20
> 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 =20
> can log in to change the status and edit the report, if necessary.=20
>=20
> --------------------------------------
> RFC2634 (draft-ietf-smime-ess-12)
> --------------------------------------
> Title               : Enhanced Security Services for S/MIME
> Publication Date    : June 1999
> Author(s)           : P. Hoffman, Ed.
> Category            : PROPOSED STANDARD
> Source              : S/MIME Mail Security
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG
>=20
> _______________________________________________
> smime mailing list
> smime@ietf.org
> https://www.ietf.org/mailman/listinfo/smime


From nobody Wed Apr 28 13:57:34 2021
Return-Path: <mferguson@amsl.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 067903A2000 for <smime@ietfa.amsl.com>; Wed, 28 Apr 2021 13:57:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 qFsTAc9YXBPY for <smime@ietfa.amsl.com>; Wed, 28 Apr 2021 13:57:28 -0700 (PDT)
Received: from mail.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA3113A1D06 for <smime@ietf.org>; Wed, 28 Apr 2021 13:57:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 8B9DB389EBC; Wed, 28 Apr 2021 13:57:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a2kTmWavvZCU; Wed, 28 Apr 2021 13:57:28 -0700 (PDT)
Received: from [192.168.68.126] (pool-173-48-33-241.bstnma.fios.verizon.net [173.48.33.241]) by c8a.amsl.com (Postfix) with ESMTPSA id C7ABA3898BA; Wed, 28 Apr 2021 13:57:27 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Megan Ferguson <mferguson@amsl.com>
In-Reply-To: <20210428181021.7FCD6F407AF@rfc-editor.org>
Date: Wed, 28 Apr 2021 16:57:26 -0400
Cc: phoffman@imc.org, rdd@cert.org, kaduk@mit.edu, paul.hoffman@vpnc.org, blaker@gmail.com, smime@ietf.org, RFC Errata System <rfc-editor@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E6051CC-11AA-4B39-BE0E-57408DD998FC@amsl.com>
References: <20210428181021.7FCD6F407AF@rfc-editor.org>
To: David.von.Oheimb@siemens.com
X-Mailer: Apple Mail (2.3654.60.0.2.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/mZIqgCrzsN2D17pmCU1ogCZsMK0>
Subject: Re: [smime] [Technical Errata Reported] RFC2634 (6563)
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: Wed, 28 Apr 2021 20:57:33 -0000

Hi David,

It looks like this text is from RFC 5035 =
(https://www.rfc-editor.org/rfc/rfc5035.txt) not RFC 2643.

We have deleted EID 6563 assuming this is the case.  Please resubmit =
using the correct RFC number.  (Unfortunately, that is one thing I =
can=E2=80=99t change from my end.)

Please let us know if we can be of further assistance.

Thank you.

RFC Editor/mf

> On Apr 28, 2021, at 2:10 PM, RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:
>=20
> The following errata report has been submitted for RFC2634,
> "Enhanced Security Services for S/MIME".
>=20
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6563
>=20
> --------------------------------------
> Type: Technical
> Reported by: David von Oheimb <David.von.Oheimb@siemens.com>
>=20
> Section: 3
>=20
> Original Text
> -------------
>=20
>   certs
>      contains the list of certificates that are to be used in
>      validating the message.  The first certificate identified in the
>      sequence of certificate identifiers MUST be the certificate used
>      to verify the signature.  The encoding of the ESSCertIDv2 for =
this
>      certificate SHOULD include the issuerSerial field.  If other
>      constraints ensure that issuerAndSerialNumber will be present in
>      the SignerInfo, the issuerSerial field MAY be omitted.  The
>      certificate identified is used during the signature verification
>      process.  If the hash of the certificate does not match the
>      certificate used to verify the signature, the signature MUST be
>      considered invalid.
>=20
>      If more than one certificate is present, subsequent certificates
>      limit the set of certificates that are used during validation.
>=20
> Corrected Text
> --------------
>=20
>   certs
>      contains the list of certificates that are to be used in
>      validating the message. It MUST contain at least one element.
>      The first certificate identified in the
>      sequence of certificate identifiers MUST be the certificate used
>      to verify the signature.  The encoding of the ESSCertIDv2 for =
this
>      certificate SHOULD include the issuerSerial field.  If other
>      constraints ensure that issuerAndSerialNumber will be present in
>      the SignerInfo, the issuerSerial field MAY be omitted.  The
>      certificate identified is used during the signature verification
>      process.  If the hash of the certificate does not match the
>      certificate used to verify the signature, the signature MUST be
>      considered invalid.
>=20
>      If more than one certificate identifier is present in the =
sequence of ESSCertIDv2s,
>      all certificates referenced there MUST be part of the signature =
validation chain.
>=20
> Notes
> -----
> Some aspects of the 'certs' field of a SigningCertificateV2 attribute:
>=20
>   SigningCertificateV2 ::=3D  SEQUENCE {
>       certs        SEQUENCE OF ESSCertIDv2,
>       policies     SEQUENCE OF PolicyInformation OPTIONAL
>   }
>=20
> described in the sentences quoted above are rather vague.
> This lead to major confusion and wrong implementations.
> As meanwhile has been clarified, they should be re-phrased;
> see suggested new version above.
>=20
> (One may further mandate/clarify that the certificate identifiers must =
be given in the same order
> as they are expected in the validation chain, but I think this is not =
important because
> the order should not play a critical role and will be determined by =
the validation chain anyway.)
>=20
> 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 =20
> can log in to change the status and edit the report, if necessary.=20
>=20
> --------------------------------------
> RFC2634 (draft-ietf-smime-ess-12)
> --------------------------------------
> Title               : Enhanced Security Services for S/MIME
> Publication Date    : June 1999
> Author(s)           : P. Hoffman, Ed.
> Category            : PROPOSED STANDARD
> Source              : S/MIME Mail Security
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG
>=20


From nobody Thu Apr 29 01:30:40 2021
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 80CBA3A35B2 for <smime@ietfa.amsl.com>; Thu, 29 Apr 2021 01:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 8DOTM33HkLqx for <smime@ietfa.amsl.com>; Thu, 29 Apr 2021 01:30:34 -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 233763A35B1 for <smime@ietf.org>; Thu, 29 Apr 2021 01:30:33 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7A84BF407A8; Thu, 29 Apr 2021 01:30:19 -0700 (PDT)
To: jimsch@exmsft.com, rdd@cert.org, kaduk@mit.edu, paul.hoffman@vpnc.org, blaker@gmail.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: David.von.Oheimb@siemens.com, smime@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20210429083019.7A84BF407A8@rfc-editor.org>
Date: Thu, 29 Apr 2021 01:30:19 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/Ew8ET_qdJ7CNlie3MvAMg4eTfak>
Subject: [smime] [Technical Errata Reported] RFC5035 (6566)
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, 29 Apr 2021 08:30:39 -0000

The following errata report has been submitted for RFC5035,
"Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility".

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

--------------------------------------
Type: Technical
Reported by: David von Oheimb <David.von.Oheimb@siemens.com>

Section: 3

Original Text
-------------
   certs
      contains the list of certificates that are to be used in
      validating the message.  The first certificate identified in the
      sequence of certificate identifiers MUST be the certificate used
      to verify the signature.  The encoding of the ESSCertIDv2 for this
      certificate SHOULD include the issuerSerial field.  If other
      constraints ensure that issuerAndSerialNumber will be present in
      the SignerInfo, the issuerSerial field MAY be omitted.  The
      certificate identified is used during the signature verification
      process.  If the hash of the certificate does not match the
      certificate used to verify the signature, the signature MUST be
      considered invalid.

      If more than one certificate is present, subsequent certificates
      limit the set of certificates that are used during validation.


Corrected Text
--------------
   certs
      contains the list of certificates that are to be used in
      validating the message. It MUST contain at least one element.
      The first certificate identified in the
      sequence of certificate identifiers MUST be the certificate used
      to verify the signature.  The encoding of the ESSCertIDv2 for this
      certificate SHOULD include the issuerSerial field.  If other
      constraints ensure that issuerAndSerialNumber will be present in
      the SignerInfo, the issuerSerial field MAY be omitted.  The
      certificate identified is used during the signature verification
      process.  If the hash of the certificate does not match the
      certificate used to verify the signature, the signature MUST be
      considered invalid.

      If more than one certificate identifier is present in the sequence of ESSCertIDv2s,
      all certificates referenced there MUST be part of the signature validation chain.

Notes
-----
Some aspects of the 'certs' field of a SigningCertificateV2 attribute:

   SigningCertificateV2 ::=  SEQUENCE {
       certs        SEQUENCE OF ESSCertIDv2,
       policies     SEQUENCE OF PolicyInformation OPTIONAL
   }

described in the sentences quoted above are rather vague.
This lead to major confusion and wrong implementations.
As meanwhile has been clarified, they should be re-phrased;
see suggested new version above.

(One may further mandate/clarify that the certificate identifiers must be given in the same order
as they are expected in the validation chain, but I think this is not important because
the order should not play a critical role and will be determined by the validation chain anyway.)

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. 

--------------------------------------
RFC5035 (draft-ietf-smime-escertid-06)
--------------------------------------
Title               : Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility
Publication Date    : August 2007
Author(s)           : J. Schaad
Category            : PROPOSED STANDARD
Source              : S/MIME Mail Security
Area                : Security
Stream              : IETF
Verifying Party     : IESG


From nobody Thu Apr 29 01:37:53 2021
Return-Path: <David.von.Oheimb@siemens.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 608413A35E5 for <smime@ietfa.amsl.com>; Thu, 29 Apr 2021 01:37:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.917
X-Spam-Level: 
X-Spam-Status: No, score=-1.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 xdfvysZ0DA52 for <smime@ietfa.amsl.com>; Thu, 29 Apr 2021 01:37:47 -0700 (PDT)
Received: from lizzard.sbs.de (lizzard.sbs.de [194.138.37.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A73DB3A35E4 for <smime@ietf.org>; Thu, 29 Apr 2021 01:37:46 -0700 (PDT)
Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by lizzard.sbs.de (8.15.2/8.15.2) with ESMTPS id 13T8bTng026490 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Thu, 29 Apr 2021 10:37:29 +0200
Received: from [139.22.38.45] ([139.22.38.45]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id 13T8Xlpi022136; Thu, 29 Apr 2021 10:33:47 +0200
To: Megan Ferguson <mferguson@amsl.com>
Cc: phoffman@imc.org, rdd@cert.org, kaduk@mit.edu, paul.hoffman@vpnc.org, blaker@gmail.com, smime@ietf.org, RFC Errata System <rfc-editor@rfc-editor.org>, Hendrik Brockhaus <Hendrik.Brockhaus@siemens.com>
References: <20210428181021.7FCD6F407AF@rfc-editor.org> <7E6051CC-11AA-4B39-BE0E-57408DD998FC@amsl.com>
From: David von Oheimb <David.von.Oheimb@siemens.com>
Message-ID: <55fa381e-e85a-2511-e3f5-71b0b30988e1@siemens.com>
Date: Thu, 29 Apr 2021 10:33:47 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1
MIME-Version: 1.0
In-Reply-To: <7E6051CC-11AA-4B39-BE0E-57408DD998FC@amsl.com>
Content-Type: multipart/alternative; boundary="------------F7ED7B1E1D250324EF00782C"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/smime/fXTY6u2-CTCTC5FzdftKVWklPPU>
Subject: Re: [smime] [Technical Errata Reported] RFC2634 (6563)
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, 29 Apr 2021 08:37:51 -0000

This is a multi-part message in MIME format.
--------------F7ED7B1E1D250324EF00782C
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

HI Megan,

thank you for your response.
Indeed the report was meant for RFC 5035 (by mistake I had not updated
the RFC number from 2643, for which just before I had filed a strongly
related report).

The corrected errata report is now at
https://www.rfc-editor.org/errata/eid6566.

Regards,

    David

On 28.04.21 22:57, Megan Ferguson wrote:
> Hi David,
>
> It looks like this text is from RFC 5035 (https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Frfc%2Frfc5035.txt&amp;data=04%7C01%7C3fc86e35-ce5e-4719-beb0-5253a4681d60%40ad011.siemens.com%7C53c91a479bda4ba0153e08d90a883d24%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637552402958167199%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=93dCWRI%2BJ598Hvxt%2BovfATRqlT5QHwyOrCLIcuJfUAc%3D&amp;reserved=0) not RFC 2643.
>
> We have deleted EID 6563 assuming this is the case.  Please resubmit using the correct RFC number.  (Unfortunately, that is one thing I can’t change from my end.)
>
> Please let us know if we can be of further assistance.
>
> Thank you.
>
> RFC Editor/mf
>
>> On Apr 28, 2021, at 2:10 PM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
>>
>> The following errata report has been submitted for RFC2634,
>> "Enhanced Security Services for S/MIME".
>>
>> --------------------------------------
>> You may review the report below and at:
>> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.rfc-editor.org%2Ferrata%2Feid6563&amp;data=04%7C01%7C3fc86e35-ce5e-4719-beb0-5253a4681d60%40ad011.siemens.com%7C53c91a479bda4ba0153e08d90a883d24%7C38ae3bcd95794fd4addab42e1495d55a%7C1%7C0%7C637552402958167199%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=bczwGB3kuvF4347dUJyhcXqCkByWQ%2BCj8sP4Yyep14I%3D&amp;reserved=0
>>
>> --------------------------------------
>> Type: Technical
>> Reported by: David von Oheimb <David.von.Oheimb@siemens.com>
>>
>> Section: 3
>>
>> Original Text
>> -------------
>>
>>   certs
>>      contains the list of certificates that are to be used in
>>      validating the message.  The first certificate identified in the
>>      sequence of certificate identifiers MUST be the certificate used
>>      to verify the signature.  The encoding of the ESSCertIDv2 for this
>>      certificate SHOULD include the issuerSerial field.  If other
>>      constraints ensure that issuerAndSerialNumber will be present in
>>      the SignerInfo, the issuerSerial field MAY be omitted.  The
>>      certificate identified is used during the signature verification
>>      process.  If the hash of the certificate does not match the
>>      certificate used to verify the signature, the signature MUST be
>>      considered invalid.
>>
>>      If more than one certificate is present, subsequent certificates
>>      limit the set of certificates that are used during validation.
>>
>> Corrected Text
>> --------------
>>
>>   certs
>>      contains the list of certificates that are to be used in
>>      validating the message. It MUST contain at least one element.
>>      The first certificate identified in the
>>      sequence of certificate identifiers MUST be the certificate used
>>      to verify the signature.  The encoding of the ESSCertIDv2 for this
>>      certificate SHOULD include the issuerSerial field.  If other
>>      constraints ensure that issuerAndSerialNumber will be present in
>>      the SignerInfo, the issuerSerial field MAY be omitted.  The
>>      certificate identified is used during the signature verification
>>      process.  If the hash of the certificate does not match the
>>      certificate used to verify the signature, the signature MUST be
>>      considered invalid.
>>
>>      If more than one certificate identifier is present in the sequence of ESSCertIDv2s,
>>      all certificates referenced there MUST be part of the signature validation chain.
>>
>> Notes
>> -----
>> Some aspects of the 'certs' field of a SigningCertificateV2 attribute:
>>
>>   SigningCertificateV2 ::=  SEQUENCE {
>>       certs        SEQUENCE OF ESSCertIDv2,
>>       policies     SEQUENCE OF PolicyInformation OPTIONAL
>>   }
>>
>> described in the sentences quoted above are rather vague.
>> This lead to major confusion and wrong implementations.
>> As meanwhile has been clarified, they should be re-phrased;
>> see suggested new version above.
>>
>> (One may further mandate/clarify that the certificate identifiers must be given in the same order
>> as they are expected in the validation chain, but I think this is not important because
>> the order should not play a critical role and will be determined by the validation chain anyway.)
>>
>> 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. 
>>
>> --------------------------------------
>> RFC2634 (draft-ietf-smime-ess-12)
>> --------------------------------------
>> Title               : Enhanced Security Services for S/MIME
>> Publication Date    : June 1999
>> Author(s)           : P. Hoffman, Ed.
>> Category            : PROPOSED STANDARD
>> Source              : S/MIME Mail Security
>> Area                : Security
>> Stream              : IETF
>> Verifying Party     : IESG
>>

--------------F7ED7B1E1D250324EF00782C
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+CiAgPGhlYWQ+CiAgICA8bWV0YSBodHRwLWVxdWl2PSJDb250ZW50LVR5cGUiIGNv
bnRlbnQ9InRleHQvaHRtbDsgY2hhcnNldD1VVEYtOCI+CiAgPC9oZWFkPgogIDxib2R5Pgog
ICAgPHA+SEkgTWVnYW4sPC9wPgogICAgPHA+dGhhbmsgeW91IGZvciB5b3VyIHJlc3BvbnNl
Ljxicj4KICAgICAgSW5kZWVkIHRoZSByZXBvcnQgd2FzIG1lYW50IGZvciBSRkMgNTAzNSAo
YnkgbWlzdGFrZSBJIGhhZCBub3QKICAgICAgdXBkYXRlZCB0aGUgUkZDIG51bWJlciBmcm9t
IDI2NDMsIGZvciB3aGljaCBqdXN0IGJlZm9yZSBJIGhhZAogICAgICBmaWxlZCBhIHN0cm9u
Z2x5IHJlbGF0ZWQgcmVwb3J0KS48L3A+CiAgICA8cD5UaGUgY29ycmVjdGVkIGVycmF0YSBy
ZXBvcnQgaXMgbm93IGF0IDxhIG1vei1kby1ub3Qtc2VuZD0idHJ1ZSIKICAgICAgICBocmVm
PSJodHRwczovL3d3dy5yZmMtZWRpdG9yLm9yZy9lcnJhdGEvZWlkNjU2NiI+aHR0cHM6Ly93
d3cucmZjLWVkaXRvci5vcmcvZXJyYXRhL2VpZDY1NjY8L2E+LjwvcD4KICAgIDxwPlJlZ2Fy
ZHMsPC9wPgogICAgPHA+wqDCoMKgIERhdmlkPGJyPgogICAgPC9wPgogICAgPGRpdiBjbGFz
cz0ibW96LWNpdGUtcHJlZml4Ij5PbiAyOC4wNC4yMSAyMjo1NywgTWVnYW4gRmVyZ3Vzb24K
ICAgICAgd3JvdGU6PGJyPgogICAgPC9kaXY+CiAgICA8YmxvY2txdW90ZSB0eXBlPSJjaXRl
IgogICAgICBjaXRlPSJtaWQ6N0U2MDUxQ0MtMTFBQS00QjM5LUJFMEUtNTc0MDhERDk5OEZD
QGFtc2wuY29tIj4KICAgICAgPHByZSBjbGFzcz0ibW96LXF1b3RlLXByZSIgd3JhcD0iIj5I
aSBEYXZpZCwKCkl0IGxvb2tzIGxpa2UgdGhpcyB0ZXh0IGlzIGZyb20gUkZDIDUwMzUgKDxh
IGNsYXNzPSJtb3otdHh0LWxpbmstZnJlZXRleHQiIGhyZWY9Imh0dHBzOi8vZXVyMDEuc2Fm
ZWxpbmtzLnByb3RlY3Rpb24ub3V0bG9vay5jb20vP3VybD1odHRwcyUzQSUyRiUyRnd3dy5y
ZmMtZWRpdG9yLm9yZyUyRnJmYyUyRnJmYzUwMzUudHh0JmFtcDthbXA7ZGF0YT0wNCU3QzAx
JTdDM2ZjODZlMzUtY2U1ZS00NzE5LWJlYjAtNTI1M2E0NjgxZDYwJTQwYWQwMTEuc2llbWVu
cy5jb20lN0M1M2M5MWE0NzliZGE0YmEwMTUzZTA4ZDkwYTg4M2QyNCU3QzM4YWUzYmNkOTU3
OTRmZDRhZGRhYjQyZTE0OTVkNTVhJTdDMSU3QzAlN0M2Mzc1NTI0MDI5NTgxNjcxOTklN0NV
bmtub3duJTdDVFdGcGJHWnNiM2Q4ZXlKV0lqb2lNQzR3TGpBd01EQWlMQ0pRSWpvaVYybHVN
eklpTENKQlRpSTZJazFoYVd3aUxDSlhWQ0k2TW4wJTNEJTdDMzAwMCZhbXA7YW1wO3NkYXRh
PTkzZENXUkklMkJKNTk4SHZ4dCUyQm92ZkFUUnFsVDVRSHd5T3JDTEljdUpmVUFjJTNEJmFt
cDthbXA7cmVzZXJ2ZWQ9MCI+aHR0cHM6Ly9ldXIwMS5zYWZlbGlua3MucHJvdGVjdGlvbi5v
dXRsb29rLmNvbS8/dXJsPWh0dHBzJTNBJTJGJTJGd3d3LnJmYy1lZGl0b3Iub3JnJTJGcmZj
JTJGcmZjNTAzNS50eHQmYW1wO2FtcDtkYXRhPTA0JTdDMDElN0MzZmM4NmUzNS1jZTVlLTQ3
MTktYmViMC01MjUzYTQ2ODFkNjAlNDBhZDAxMS5zaWVtZW5zLmNvbSU3QzUzYzkxYTQ3OWJk
YTRiYTAxNTNlMDhkOTBhODgzZDI0JTdDMzhhZTNiY2Q5NTc5NGZkNGFkZGFiNDJlMTQ5NWQ1
NWElN0MxJTdDMCU3QzYzNzU1MjQwMjk1ODE2NzE5OSU3Q1Vua25vd24lN0NUV0ZwYkdac2Iz
ZDhleUpXSWpvaU1DNHdMakF3TURBaUxDSlFJam9pVjJsdU16SWlMQ0pCVGlJNklrMWhhV3dp
TENKWFZDSTZNbjAlM0QlN0MzMDAwJmFtcDthbXA7c2RhdGE9OTNkQ1dSSSUyQko1OThIdnh0
JTJCb3ZmQVRScWxUNVFId3lPckNMSWN1SmZVQWMlM0QmYW1wO2FtcDtyZXNlcnZlZD0wPC9h
Pikgbm90IFJGQyAyNjQzLgoKV2UgaGF2ZSBkZWxldGVkIEVJRCA2NTYzIGFzc3VtaW5nIHRo
aXMgaXMgdGhlIGNhc2UuICBQbGVhc2UgcmVzdWJtaXQgdXNpbmcgdGhlIGNvcnJlY3QgUkZD
IG51bWJlci4gIChVbmZvcnR1bmF0ZWx5LCB0aGF0IGlzIG9uZSB0aGluZyBJIGNhbuKAmXQg
Y2hhbmdlIGZyb20gbXkgZW5kLikKClBsZWFzZSBsZXQgdXMga25vdyBpZiB3ZSBjYW4gYmUg
b2YgZnVydGhlciBhc3Npc3RhbmNlLgoKVGhhbmsgeW91LgoKUkZDIEVkaXRvci9tZgoKPC9w
cmU+CiAgICAgIDxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPgogICAgICAgIDxwcmUgY2xhc3M9
Im1vei1xdW90ZS1wcmUiIHdyYXA9IiI+T24gQXByIDI4LCAyMDIxLCBhdCAyOjEwIFBNLCBS
RkMgRXJyYXRhIFN5c3RlbSA8YSBjbGFzcz0ibW96LXR4dC1saW5rLXJmYzIzOTZFIiBocmVm
PSJtYWlsdG86cmZjLWVkaXRvckByZmMtZWRpdG9yLm9yZyI+Jmx0O3JmYy1lZGl0b3JAcmZj
LWVkaXRvci5vcmcmZ3Q7PC9hPiB3cm90ZToKClRoZSBmb2xsb3dpbmcgZXJyYXRhIHJlcG9y
dCBoYXMgYmVlbiBzdWJtaXR0ZWQgZm9yIFJGQzI2MzQsCiJFbmhhbmNlZCBTZWN1cml0eSBT
ZXJ2aWNlcyBmb3IgUy9NSU1FIi4KCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tCllvdSBtYXkgcmV2aWV3IHRoZSByZXBvcnQgYmVsb3cgYW5kIGF0Ogo8YSBjbGFz
cz0ibW96LXR4dC1saW5rLWZyZWV0ZXh0IiBocmVmPSJodHRwczovL2V1cjAxLnNhZmVsaW5r
cy5wcm90ZWN0aW9uLm91dGxvb2suY29tLz91cmw9aHR0cHMlM0ElMkYlMkZ3d3cucmZjLWVk
aXRvci5vcmclMkZlcnJhdGElMkZlaWQ2NTYzJmFtcDthbXA7ZGF0YT0wNCU3QzAxJTdDM2Zj
ODZlMzUtY2U1ZS00NzE5LWJlYjAtNTI1M2E0NjgxZDYwJTQwYWQwMTEuc2llbWVucy5jb20l
N0M1M2M5MWE0NzliZGE0YmEwMTUzZTA4ZDkwYTg4M2QyNCU3QzM4YWUzYmNkOTU3OTRmZDRh
ZGRhYjQyZTE0OTVkNTVhJTdDMSU3QzAlN0M2Mzc1NTI0MDI5NTgxNjcxOTklN0NVbmtub3du
JTdDVFdGcGJHWnNiM2Q4ZXlKV0lqb2lNQzR3TGpBd01EQWlMQ0pRSWpvaVYybHVNeklpTENK
QlRpSTZJazFoYVd3aUxDSlhWQ0k2TW4wJTNEJTdDMzAwMCZhbXA7YW1wO3NkYXRhPWJjendH
QjNrdXZGNDM0N2RVSnloY1hxQ2tCeVdRJTJCQ2o4c1A0WXllcDE0SSUzRCZhbXA7YW1wO3Jl
c2VydmVkPTAiPmh0dHBzOi8vZXVyMDEuc2FmZWxpbmtzLnByb3RlY3Rpb24ub3V0bG9vay5j
b20vP3VybD1odHRwcyUzQSUyRiUyRnd3dy5yZmMtZWRpdG9yLm9yZyUyRmVycmF0YSUyRmVp
ZDY1NjMmYW1wO2FtcDtkYXRhPTA0JTdDMDElN0MzZmM4NmUzNS1jZTVlLTQ3MTktYmViMC01
MjUzYTQ2ODFkNjAlNDBhZDAxMS5zaWVtZW5zLmNvbSU3QzUzYzkxYTQ3OWJkYTRiYTAxNTNl
MDhkOTBhODgzZDI0JTdDMzhhZTNiY2Q5NTc5NGZkNGFkZGFiNDJlMTQ5NWQ1NWElN0MxJTdD
MCU3QzYzNzU1MjQwMjk1ODE2NzE5OSU3Q1Vua25vd24lN0NUV0ZwYkdac2IzZDhleUpXSWpv
aU1DNHdMakF3TURBaUxDSlFJam9pVjJsdU16SWlMQ0pCVGlJNklrMWhhV3dpTENKWFZDSTZN
bjAlM0QlN0MzMDAwJmFtcDthbXA7c2RhdGE9YmN6d0dCM2t1dkY0MzQ3ZFVKeWhjWHFDa0J5
V1ElMkJDajhzUDRZeWVwMTRJJTNEJmFtcDthbXA7cmVzZXJ2ZWQ9MDwvYT4KCi0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tClR5cGU6IFRlY2huaWNhbApSZXBvcnRl
ZCBieTogRGF2aWQgdm9uIE9oZWltYiA8YSBjbGFzcz0ibW96LXR4dC1saW5rLXJmYzIzOTZF
IiBocmVmPSJtYWlsdG86RGF2aWQudm9uLk9oZWltYkBzaWVtZW5zLmNvbSI+Jmx0O0Rhdmlk
LnZvbi5PaGVpbWJAc2llbWVucy5jb20mZ3Q7PC9hPgoKU2VjdGlvbjogMwoKT3JpZ2luYWwg
VGV4dAotLS0tLS0tLS0tLS0tCgogIGNlcnRzCiAgICAgY29udGFpbnMgdGhlIGxpc3Qgb2Yg
Y2VydGlmaWNhdGVzIHRoYXQgYXJlIHRvIGJlIHVzZWQgaW4KICAgICB2YWxpZGF0aW5nIHRo
ZSBtZXNzYWdlLiAgVGhlIGZpcnN0IGNlcnRpZmljYXRlIGlkZW50aWZpZWQgaW4gdGhlCiAg
ICAgc2VxdWVuY2Ugb2YgY2VydGlmaWNhdGUgaWRlbnRpZmllcnMgTVVTVCBiZSB0aGUgY2Vy
dGlmaWNhdGUgdXNlZAogICAgIHRvIHZlcmlmeSB0aGUgc2lnbmF0dXJlLiAgVGhlIGVuY29k
aW5nIG9mIHRoZSBFU1NDZXJ0SUR2MiBmb3IgdGhpcwogICAgIGNlcnRpZmljYXRlIFNIT1VM
RCBpbmNsdWRlIHRoZSBpc3N1ZXJTZXJpYWwgZmllbGQuICBJZiBvdGhlcgogICAgIGNvbnN0
cmFpbnRzIGVuc3VyZSB0aGF0IGlzc3VlckFuZFNlcmlhbE51bWJlciB3aWxsIGJlIHByZXNl
bnQgaW4KICAgICB0aGUgU2lnbmVySW5mbywgdGhlIGlzc3VlclNlcmlhbCBmaWVsZCBNQVkg
YmUgb21pdHRlZC4gIFRoZQogICAgIGNlcnRpZmljYXRlIGlkZW50aWZpZWQgaXMgdXNlZCBk
dXJpbmcgdGhlIHNpZ25hdHVyZSB2ZXJpZmljYXRpb24KICAgICBwcm9jZXNzLiAgSWYgdGhl
IGhhc2ggb2YgdGhlIGNlcnRpZmljYXRlIGRvZXMgbm90IG1hdGNoIHRoZQogICAgIGNlcnRp
ZmljYXRlIHVzZWQgdG8gdmVyaWZ5IHRoZSBzaWduYXR1cmUsIHRoZSBzaWduYXR1cmUgTVVT
VCBiZQogICAgIGNvbnNpZGVyZWQgaW52YWxpZC4KCiAgICAgSWYgbW9yZSB0aGFuIG9uZSBj
ZXJ0aWZpY2F0ZSBpcyBwcmVzZW50LCBzdWJzZXF1ZW50IGNlcnRpZmljYXRlcwogICAgIGxp
bWl0IHRoZSBzZXQgb2YgY2VydGlmaWNhdGVzIHRoYXQgYXJlIHVzZWQgZHVyaW5nIHZhbGlk
YXRpb24uCgpDb3JyZWN0ZWQgVGV4dAotLS0tLS0tLS0tLS0tLQoKICBjZXJ0cwogICAgIGNv
bnRhaW5zIHRoZSBsaXN0IG9mIGNlcnRpZmljYXRlcyB0aGF0IGFyZSB0byBiZSB1c2VkIGlu
CiAgICAgdmFsaWRhdGluZyB0aGUgbWVzc2FnZS4gSXQgTVVTVCBjb250YWluIGF0IGxlYXN0
IG9uZSBlbGVtZW50LgogICAgIFRoZSBmaXJzdCBjZXJ0aWZpY2F0ZSBpZGVudGlmaWVkIGlu
IHRoZQogICAgIHNlcXVlbmNlIG9mIGNlcnRpZmljYXRlIGlkZW50aWZpZXJzIE1VU1QgYmUg
dGhlIGNlcnRpZmljYXRlIHVzZWQKICAgICB0byB2ZXJpZnkgdGhlIHNpZ25hdHVyZS4gIFRo
ZSBlbmNvZGluZyBvZiB0aGUgRVNTQ2VydElEdjIgZm9yIHRoaXMKICAgICBjZXJ0aWZpY2F0
ZSBTSE9VTEQgaW5jbHVkZSB0aGUgaXNzdWVyU2VyaWFsIGZpZWxkLiAgSWYgb3RoZXIKICAg
ICBjb25zdHJhaW50cyBlbnN1cmUgdGhhdCBpc3N1ZXJBbmRTZXJpYWxOdW1iZXIgd2lsbCBi
ZSBwcmVzZW50IGluCiAgICAgdGhlIFNpZ25lckluZm8sIHRoZSBpc3N1ZXJTZXJpYWwgZmll
bGQgTUFZIGJlIG9taXR0ZWQuICBUaGUKICAgICBjZXJ0aWZpY2F0ZSBpZGVudGlmaWVkIGlz
IHVzZWQgZHVyaW5nIHRoZSBzaWduYXR1cmUgdmVyaWZpY2F0aW9uCiAgICAgcHJvY2Vzcy4g
IElmIHRoZSBoYXNoIG9mIHRoZSBjZXJ0aWZpY2F0ZSBkb2VzIG5vdCBtYXRjaCB0aGUKICAg
ICBjZXJ0aWZpY2F0ZSB1c2VkIHRvIHZlcmlmeSB0aGUgc2lnbmF0dXJlLCB0aGUgc2lnbmF0
dXJlIE1VU1QgYmUKICAgICBjb25zaWRlcmVkIGludmFsaWQuCgogICAgIElmIG1vcmUgdGhh
biBvbmUgY2VydGlmaWNhdGUgaWRlbnRpZmllciBpcyBwcmVzZW50IGluIHRoZSBzZXF1ZW5j
ZSBvZiBFU1NDZXJ0SUR2MnMsCiAgICAgYWxsIGNlcnRpZmljYXRlcyByZWZlcmVuY2VkIHRo
ZXJlIE1VU1QgYmUgcGFydCBvZiB0aGUgc2lnbmF0dXJlIHZhbGlkYXRpb24gY2hhaW4uCgpO
b3RlcwotLS0tLQpTb21lIGFzcGVjdHMgb2YgdGhlICdjZXJ0cycgZmllbGQgb2YgYSBTaWdu
aW5nQ2VydGlmaWNhdGVWMiBhdHRyaWJ1dGU6CgogIFNpZ25pbmdDZXJ0aWZpY2F0ZVYyIDo6
PSAgU0VRVUVOQ0UgewogICAgICBjZXJ0cyAgICAgICAgU0VRVUVOQ0UgT0YgRVNTQ2VydElE
djIsCiAgICAgIHBvbGljaWVzICAgICBTRVFVRU5DRSBPRiBQb2xpY3lJbmZvcm1hdGlvbiBP
UFRJT05BTAogIH0KCmRlc2NyaWJlZCBpbiB0aGUgc2VudGVuY2VzIHF1b3RlZCBhYm92ZSBh
cmUgcmF0aGVyIHZhZ3VlLgpUaGlzIGxlYWQgdG8gbWFqb3IgY29uZnVzaW9uIGFuZCB3cm9u
ZyBpbXBsZW1lbnRhdGlvbnMuCkFzIG1lYW53aGlsZSBoYXMgYmVlbiBjbGFyaWZpZWQsIHRo
ZXkgc2hvdWxkIGJlIHJlLXBocmFzZWQ7CnNlZSBzdWdnZXN0ZWQgbmV3IHZlcnNpb24gYWJv
dmUuCgooT25lIG1heSBmdXJ0aGVyIG1hbmRhdGUvY2xhcmlmeSB0aGF0IHRoZSBjZXJ0aWZp
Y2F0ZSBpZGVudGlmaWVycyBtdXN0IGJlIGdpdmVuIGluIHRoZSBzYW1lIG9yZGVyCmFzIHRo
ZXkgYXJlIGV4cGVjdGVkIGluIHRoZSB2YWxpZGF0aW9uIGNoYWluLCBidXQgSSB0aGluayB0
aGlzIGlzIG5vdCBpbXBvcnRhbnQgYmVjYXVzZQp0aGUgb3JkZXIgc2hvdWxkIG5vdCBwbGF5
IGEgY3JpdGljYWwgcm9sZSBhbmQgd2lsbCBiZSBkZXRlcm1pbmVkIGJ5IHRoZSB2YWxpZGF0
aW9uIGNoYWluIGFueXdheS4pCgpJbnN0cnVjdGlvbnM6Ci0tLS0tLS0tLS0tLS0KVGhpcyBl
cnJhdHVtIGlzIGN1cnJlbnRseSBwb3N0ZWQgYXMgIlJlcG9ydGVkIi4gSWYgbmVjZXNzYXJ5
LCBwbGVhc2UKdXNlICJSZXBseSBBbGwiIHRvIGRpc2N1c3Mgd2hldGhlciBpdCBzaG91bGQg
YmUgdmVyaWZpZWQgb3IKcmVqZWN0ZWQuIFdoZW4gYSBkZWNpc2lvbiBpcyByZWFjaGVkLCB0
aGUgdmVyaWZ5aW5nIHBhcnR5ICAKY2FuIGxvZyBpbiB0byBjaGFuZ2UgdGhlIHN0YXR1cyBh
bmQgZWRpdCB0aGUgcmVwb3J0LCBpZiBuZWNlc3NhcnkuIAoKLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0KUkZDMjYzNCAoZHJhZnQtaWV0Zi1zbWltZS1lc3MtMTIp
Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tClRpdGxlICAgICAgICAg
ICAgICAgOiBFbmhhbmNlZCBTZWN1cml0eSBTZXJ2aWNlcyBmb3IgUy9NSU1FClB1YmxpY2F0
aW9uIERhdGUgICAgOiBKdW5lIDE5OTkKQXV0aG9yKHMpICAgICAgICAgICA6IFAuIEhvZmZt
YW4sIEVkLgpDYXRlZ29yeSAgICAgICAgICAgIDogUFJPUE9TRUQgU1RBTkRBUkQKU291cmNl
ICAgICAgICAgICAgICA6IFMvTUlNRSBNYWlsIFNlY3VyaXR5CkFyZWEgICAgICAgICAgICAg
ICAgOiBTZWN1cml0eQpTdHJlYW0gICAgICAgICAgICAgIDogSUVURgpWZXJpZnlpbmcgUGFy
dHkgICAgIDogSUVTRwoKPC9wcmU+CiAgICAgIDwvYmxvY2txdW90ZT4KICAgICAgPHByZSBj
bGFzcz0ibW96LXF1b3RlLXByZSIgd3JhcD0iIj4KPC9wcmU+CiAgICA8L2Jsb2NrcXVvdGU+
CiAgPC9ib2R5Pgo8L2h0bWw+Cg==
--------------F7ED7B1E1D250324EF00782C--

