From wwwrun@rfc-editor.org Mon Jan 25 10:18:46 2010 Return-Path: X-Original-To: smime@core3.amsl.com Delivered-To: smime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1480F3A688D; Mon, 25 Jan 2010 10:18:46 -0800 (PST) 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=[AWL=0.100, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jxQL-rJU3ERM; Mon, 25 Jan 2010 10:18:45 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 631E23A6851; Mon, 25 Jan 2010 10:18:45 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 86D81E06AE; Mon, 25 Jan 2010 10:18:52 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20100125181852.86D81E06AE@rfc-editor.org> Date: Mon, 25 Jan 2010 10:18:52 -0800 (PST) Cc: smime@ietf.org, rfc-editor@rfc-editor.org Subject: [smime] RFC 5750 on Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate Handling X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2010 18:18:46 -0000 A new Request for Comments is now available in online RFC libraries. RFC 5750 Title: Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate Handling Author: B. Ramsdell, S. Turner Status: Standards Track Date: January 2010 Mailbox: blaker@gmail.com, turners@ieca.com Pages: 21 Characters: 48716 Obsoletes: RFC3850 I-D Tag: draft-ietf-smime-3850bis-11.txt URL: http://www.rfc-editor.org/rfc/rfc5750.txt This document specifies conventions for X.509 certificate usage by Secure/Multipurpose Internet Mail Extensions (S/MIME) v3.2 agents. S/MIME provides a method to send and receive secure MIME messages, and certificates are an integral part of S/MIME agent processing. S/MIME agents validate certificates as described in RFC 5280, the Internet X.509 Public Key Infrastructure Certificate and CRL Profile. S/MIME agents must meet the certificate processing requirements in this document as well as those in RFC 5280. This document obsoletes RFC 3850. [STANDARDS TRACK] This document is a product of the S/MIME Mail Security Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From wwwrun@rfc-editor.org Mon Jan 25 10:19:05 2010 Return-Path: X-Original-To: smime@core3.amsl.com Delivered-To: smime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8392128C100; Mon, 25 Jan 2010 10:19:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.92 X-Spam-Level: X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[AWL=0.080, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IPqy0Xai7MUk; Mon, 25 Jan 2010 10:19:04 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id BE36928C0FF; Mon, 25 Jan 2010 10:19:04 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id E1886E06B9; Mon, 25 Jan 2010 10:19:11 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20100125181911.E1886E06B9@rfc-editor.org> Date: Mon, 25 Jan 2010 10:19:11 -0800 (PST) Cc: smime@ietf.org, rfc-editor@rfc-editor.org Subject: [smime] RFC 5751 on Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2010 18:19:05 -0000 A new Request for Comments is now available in online RFC libraries. RFC 5751 Title: Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification Author: B. Ramsdell, S. Turner Status: Standards Track Date: January 2010 Mailbox: blaker@gmail.com, turners@ieca.com Pages: 45 Characters: 98638 Obsoletes: RFC3851 I-D Tag: draft-ietf-smime-3851bis-11.txt URL: http://www.rfc-editor.org/rfc/rfc5751.txt This document defines Secure/Multipurpose Internet Mail Extensions (S/MIME) version 3.2. S/MIME provides a consistent way to send and receive secure MIME data. Digital signatures provide authentication, message integrity, and non-repudiation with proof of origin. Encryption provides data confidentiality. Compression can be used to reduce data size. This document obsoletes RFC 3851. [STANDARDS TRACK] This document is a product of the S/MIME Mail Security Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From wwwrun@rfc-editor.org Mon Jan 25 10:19:24 2010 Return-Path: X-Original-To: smime@core3.amsl.com Delivered-To: smime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C2CB628C0FE; Mon, 25 Jan 2010 10:19:24 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.933 X-Spam-Level: X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dF7ffdJx17-d; Mon, 25 Jan 2010 10:19:24 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id CEC6A28C108; Mon, 25 Jan 2010 10:19:23 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 11800E06BD; Mon, 25 Jan 2010 10:19:29 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20100125181929.11800E06BD@rfc-editor.org> Date: Mon, 25 Jan 2010 10:19:29 -0800 (PST) Cc: smime@ietf.org, rfc-editor@rfc-editor.org Subject: [smime] RFC 5752 on Multiple Signatures in Cryptographic Message Syntax (CMS) X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2010 18:19:24 -0000 A new Request for Comments is now available in online RFC libraries. RFC 5752 Title: Multiple Signatures in Cryptographic Message Syntax (CMS) Author: S. Turner, J. Schaad Status: Standards Track Date: January 2010 Mailbox: turners@ieca.com, jimsch@exmsft.com Pages: 17 Characters: 34502 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-smime-multisig-05.txt URL: http://www.rfc-editor.org/rfc/rfc5752.txt Cryptographic Message Syntax (CMS) SignedData includes the SignerInfo structure to convey per-signer information. SignedData supports multiple signers and multiple signature algorithms per signer with multiple SignerInfo structures. If a signer attaches more than one SignerInfo, there are concerns that an attacker could perform a downgrade attack by removing the SignerInfo(s) with the 'strong' algorithm(s). This document defines the multiple-signatures attribute, its generation rules, and its processing rules to allow signers to convey multiple SignerInfo objects while protecting against downgrade attacks. Additionally, this attribute may assist during periods of algorithm migration. [STANDARDS TRACK] This document is a product of the S/MIME Mail Security Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From wwwrun@rfc-editor.org Mon Jan 25 10:19:37 2010 Return-Path: X-Original-To: smime@core3.amsl.com Delivered-To: smime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5F62928C121; Mon, 25 Jan 2010 10:19:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.243 X-Spam-Level: X-Spam-Status: No, score=-2.243 tagged_above=-999 required=5 tests=[AWL=0.357, BAYES_00=-2.599, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s3EkpFs1jDXJ; Mon, 25 Jan 2010 10:19:36 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 9664728C11C; Mon, 25 Jan 2010 10:19:36 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id AB3D4E06BE; Mon, 25 Jan 2010 10:19:43 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20100125181943.AB3D4E06BE@rfc-editor.org> Date: Mon, 25 Jan 2010 10:19:43 -0800 (PST) Cc: smime@ietf.org, rfc-editor@rfc-editor.org Subject: [smime] RFC 5753 on Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS) X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2010 18:19:37 -0000 A new Request for Comments is now available in online RFC libraries. RFC 5753 Title: Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS) Author: S. Turner, D. Brown Status: Informational Date: January 2010 Mailbox: turners@ieca.com, dbrown@certicom.com Pages: 61 Characters: 112095 Obsoletes: RFC3278 I-D Tag: draft-ietf-smime-3278bis-09.txt URL: http://www.rfc-editor.org/rfc/rfc5753.txt This document describes how to use Elliptic Curve Cryptography (ECC) public key algorithms in the Cryptographic Message Syntax (CMS). The ECC algorithms support the creation of digital signatures and the exchange of keys to encrypt or authenticate content. The definition of the algorithm processing is based on the NIST FIPS 186-3 for digital signature, NIST SP800-56A and SEC1 for key agreement, RFC 3370 and RFC 3565 for key wrap and content encryption, NIST FIPS 180-3 for message digest, SEC1 for key derivation, and RFC 2104 and RFC 4231 for message authentication code standards. This document obsoletes RFC 3278. This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the S/MIME Mail Security Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From wwwrun@rfc-editor.org Mon Jan 25 10:19:50 2010 Return-Path: X-Original-To: smime@core3.amsl.com Delivered-To: smime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 88DFC28C126; Mon, 25 Jan 2010 10:19:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.988 X-Spam-Level: X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A2AOpiC1pQYd; Mon, 25 Jan 2010 10:19:49 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id C997C28C129; Mon, 25 Jan 2010 10:19:49 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id EE5FDE06C6; Mon, 25 Jan 2010 10:19:56 -0800 (PST) To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org Message-Id: <20100125181956.EE5FDE06C6@rfc-editor.org> Date: Mon, 25 Jan 2010 10:19:56 -0800 (PST) Cc: smime@ietf.org, rfc-editor@rfc-editor.org Subject: [smime] RFC 5754 on Using SHA2 Algorithms with Cryptographic Message Syntax X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jan 2010 18:19:50 -0000 A new Request for Comments is now available in online RFC libraries. RFC 5754 Title: Using SHA2 Algorithms with Cryptographic Message Syntax Author: S. Turner Status: Standards Track Date: January 2010 Mailbox: turners@ieca.com Pages: 10 Characters: 21543 Updates: RFC3370 I-D Tag: draft-ietf-smime-sha2-11.txt URL: http://www.rfc-editor.org/rfc/rfc5754.txt This document describes the conventions for using the Secure Hash Algorithm (SHA) message digest algorithms (SHA-224, SHA-256, SHA-384, SHA-512) with the Cryptographic Message Syntax (CMS). It also describes the conventions for using these algorithms with the CMS and the Digital Signature Algorithm (DSA), Rivest Shamir Adleman (RSA), and Elliptic Curve DSA (ECDSA) signature algorithms. Further, it provides SMIMECapabilities attribute values for each algorithm. [STANDARDS TRACK] This document is a product of the S/MIME Mail Security Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements. Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC From wwwrun@rfc-editor.org Wed Jan 27 17:05:36 2010 Return-Path: X-Original-To: smime@core3.amsl.com Delivered-To: smime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 48C103A6AF7 for ; Wed, 27 Jan 2010 17:05:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.275 X-Spam-Level: X-Spam-Status: No, score=-2.275 tagged_above=-999 required=5 tests=[AWL=-0.275, BAYES_00=-2.599, J_CHICKENPOX_45=0.6, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8e+vIGEw+3k2 for ; Wed, 27 Jan 2010 17:05:35 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 8A5E73A6AF0 for ; Wed, 27 Jan 2010 17:05:35 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id DADDCE0697; Wed, 27 Jan 2010 17:05:51 -0800 (PST) To: turners@ieca.com, tim.polk@nist.gov, pasi.eronen@nokia.com, turners@ieca.com, blaker@gmail.com From: RFC Errata System Message-Id: <20100128010551.DADDCE0697@rfc-editor.org> Date: Wed, 27 Jan 2010 17:05:51 -0800 (PST) Cc: ah@TR-Sys.de, rfc-editor@rfc-editor.org, smime@ietf.org Subject: [smime] [Technical Errata Reported] RFC5754 (2025) X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2010 01:05:36 -0000 The following errata report has been submitted for RFC5754, "Using SHA2 Algorithms with Cryptographic Message Syntax". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5754&eid=2025 -------------------------------------- Type: Technical Reported by: Alfred Hoenes Section: 2.4, pg. 6 Original Text ------------- 2.4. SHA-512 [...] | The SMIMECapabilities attribute value indicates support for SHA-384 in a SEQUENCE with the capabilityID field containing the object | identifier id-sha384 with absent parameters. The DER encoding for this SMIMECapability value is: id-sha512: 30 0b 06 09 60 86 48 01 65 03 04 02 03 Corrected Text -------------- 2.4. SHA-512 [...] | The SMIMECapabilities attribute value indicates support for SHA-512 in a SEQUENCE with the capabilityID field containing the object | identifier id-sha512 with absent parameters. The DER encoding for this SMIMECapability value is: id-sha512: 30 0b 06 09 60 86 48 01 65 03 04 02 03 Notes ----- Rationale: Undetected copy&paste error, but significant (therefore classified as Technical) Instructions: ------------- This errata 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 (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5754 (draft-ietf-smime-sha2-11) -------------------------------------- Title : Using SHA2 Algorithms with Cryptographic Message Syntax Publication Date : January 2010 Author(s) : S. Turner Category : PROPOSED STANDARD Source : S/MIME Mail Security Area : Security Stream : IETF Verifying Party : IESG From wwwrun@rfc-editor.org Thu Jan 28 01:00:55 2010 Return-Path: X-Original-To: smime@core3.amsl.com Delivered-To: smime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B2E413A6A26 for ; Thu, 28 Jan 2010 01:00:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.554 X-Spam-Level: X-Spam-Status: No, score=-2.554 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pRPQXIPVN22Z for ; Thu, 28 Jan 2010 01:00:54 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id F0EF83A6A25 for ; Thu, 28 Jan 2010 01:00:54 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 8A12A130001; Thu, 28 Jan 2010 01:01:12 -0800 (PST) To: housley@vigilsec.com, tim.polk@nist.gov, pasi.eronen@nokia.com, turners@ieca.com, blaker@gmail.com From: RFC Errata System Message-Id: <20100128090112.8A12A130001@rfc-editor.org> Date: Thu, 28 Jan 2010 01:01:12 -0800 (PST) Cc: ah@TR-Sys.de, rfc-editor@rfc-editor.org, smime@ietf.org Subject: [smime] [Editorial Errata Reported] RFC5652 (2026) X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jan 2010 09:00:55 -0000 The following errata report has been submitted for RFC5652, "Cryptographic Message Syntax (CMS)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5652&eid=2026 -------------------------------------- Type: Editorial Reported by: Alfred Hoenes Section: 5.3, pg. 15 Original Text ------------- [[ around the page break from page 14 to page 15: ]] digestAlgorithm identifies the message digest algorithm, and any associated parameters, used by the signer. The message digest is computed on either the content being signed or the content << page break >> together with the signed attributes using the process described in Section 5.4. The message digest algorithm SHOULD be among those | listed in the digestAlgorithms field of the associated SignerData. ^^^^^^^^^^ Implementations MAY fail to validate signatures that use a digest algorithm that is not included in the SignedData digestAlgorithms set. Corrected Text -------------- digestAlgorithm identifies the message digest algorithm, and any associated parameters, used by the signer. The message digest is computed on either the content being signed or the content together with the signed attributes using the process described in Section 5.4. The message digest algorithm SHOULD be among those | listed in the digestAlgorithms field of the associated SignedData. Implementations MAY fail to validate signatures that use a digest algorithm that is not included in the SignedData digestAlgorithms set. Notes ----- Rationale: There's no such ASN.1 type/object named "SignerData" in relevant specifications. Text should refer to "SignedData" instead. This is an undetected legacy flaw inherited literally from RFC 2630, RFC 3369, and RFC 3852. Instructions: ------------- This errata 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 (IESG) 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 wwwrun@rfc-editor.org Fri Jan 29 12:51:00 2010 Return-Path: X-Original-To: smime@core3.amsl.com Delivered-To: smime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 38E9F3A688B for ; Fri, 29 Jan 2010 12:51:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.557 X-Spam-Level: X-Spam-Status: No, score=-2.557 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ft3BmVAhAwNM for ; Fri, 29 Jan 2010 12:50:59 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 615513A6848 for ; Fri, 29 Jan 2010 12:50:59 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 15FC1E06B0; Fri, 29 Jan 2010 12:51:23 -0800 (PST) To: turners@ieca.com, jimsch@exmsft.com, tim.polk@nist.gov, pasi.eronen@nokia.com, turners@ieca.com, blaker@gmail.com From: RFC Errata System Message-Id: <20100129205123.15FC1E06B0@rfc-editor.org> Date: Fri, 29 Jan 2010 12:51:23 -0800 (PST) Cc: ah@TR-Sys.de, rfc-editor@rfc-editor.org, smime@ietf.org Subject: [smime] [Technical Errata Reported] RFC5752 (2027) X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2010 20:51:00 -0000 The following errata report has been submitted for RFC5752, "Multiple Signatures in Cryptographic Message Syntax (CMS)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5752&eid=2027 -------------------------------------- Type: Technical Reported by: Alfred Hoenes Section: 5, pg. 8 Original Text ------------- This section describes recommended processing of signatures when | there are more than one SignerInfo present in a message. This may be due to either multiple SignerInfo objects being present in a single | SignedData object or multiple SignerData objects embedded in each other. [...] Order of operations: 1) Evaluate each SignerInfo object independently. 2) Combine the results of all SignerInfo objects at the same level | (i.e., attached to the same SignerData object). | 3) Combine the results of the nested SignerData objects. Note that this should ignore the presence of other CMS objects between the SignedData objects. Corrected Text -------------- This section describes recommended processing of signatures when | there is more than one SignerInfo object present in a message. This may be due to either multiple SignerInfo objects being present in a | single SignedData object or multiple SignedData objects embedded in each other. [...] Order of operations: 1) Evaluate each SignerInfo object independently. 2) Combine the results of all SignerInfo objects at the same level | (i.e., attached to the same SignedData object). | 3) Combine the results of the nested SignedData objects. Note that this should ignore the presence of other CMS objects between the SignedData objects. Notes ----- Rationale: There's no such ASN.1 type/object "SignerData". Based on the importance of referencing the correct type/object, the correction to "SignedData" is classified as 'Technical'. Also a clarification and fix is applied in the first sentence. Instructions: ------------- This errata 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 (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5752 (draft-ietf-smime-multisig-05) -------------------------------------- Title : Multiple Signatures in Cryptographic Message Syntax (CMS) Publication Date : January 2010 Author(s) : S. Turner, J. Schaad Category : PROPOSED STANDARD Source : S/MIME Mail Security Area : Security Stream : IETF Verifying Party : IESG From wwwrun@rfc-editor.org Fri Jan 29 12:54:28 2010 Return-Path: X-Original-To: smime@core3.amsl.com Delivered-To: smime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B3BD43A67DA for ; Fri, 29 Jan 2010 12:54:28 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.56 X-Spam-Level: X-Spam-Status: No, score=-2.56 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TuFdc+cEP7YD for ; Fri, 29 Jan 2010 12:54:27 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id B3FC13A659A for ; Fri, 29 Jan 2010 12:54:27 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 749E7E06B3; Fri, 29 Jan 2010 12:54:51 -0800 (PST) To: turners@ieca.com, jimsch@exmsft.com, tim.polk@nist.gov, pasi.eronen@nokia.com, turners@ieca.com, blaker@gmail.com From: RFC Errata System Message-Id: <20100129205451.749E7E06B3@rfc-editor.org> Date: Fri, 29 Jan 2010 12:54:51 -0800 (PST) Cc: ah@TR-Sys.de, rfc-editor@rfc-editor.org, smime@ietf.org Subject: [smime] [Editorial Errata Reported] RFC5752 (2028) X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2010 20:54:28 -0000 The following errata report has been submitted for RFC5752, "Multiple Signatures in Cryptographic Message Syntax (CMS)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5752&eid=2028 -------------------------------------- Type: Editorial Reported by: Alfred Hoenes Section: 2.1, pg. 6 Original Text ------------- The following is an example: SignedData DigestAlg=sha1,sha256 SignerInfo1 SignerInfo2 digestAlg=sha1 digestAlg=sha256 signatureAlg=dsawithsha1 signatureAlg=ecdsawithsha256 signedAttrs= signedAttrs= signingTime1 signingTime1 messageDigest1 messageDigest2 multiSig1= multiSig2= bodyHash=sha256 bodyHash=sha1 signAlg=ecdsawithsha256 signAlg=dsawithsha1 | signAttrsHash= signAttrsHash= | algID=sha1 algID=sha256 | hash=value1 hash=value2 Corrected Text -------------- The following is an example: SignedData DigestAlg=sha1,sha256 SignerInfo1 SignerInfo2 digestAlg=sha1 digestAlg=sha256 signatureAlg=dsawithsha1 signatureAlg=ecdsawithsha256 signedAttrs= signedAttrs= signingTime1 signingTime1 messageDigest1 messageDigest2 multiSig1= multiSig2= bodyHash=sha256 bodyHash=sha1 signAlg=ecdsawithsha256 signAlg=dsawithsha1 | signAttrsHash= signAttrsHash= | algID=sha1 algID=sha256 | hash=value1 hash=value2 Notes ----- Rationale: Fixed indentation for consistency and clarity (visual indication of subordinate elements). Instructions: ------------- This errata 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 (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5752 (draft-ietf-smime-multisig-05) -------------------------------------- Title : Multiple Signatures in Cryptographic Message Syntax (CMS) Publication Date : January 2010 Author(s) : S. Turner, J. Schaad Category : PROPOSED STANDARD Source : S/MIME Mail Security Area : Security Stream : IETF Verifying Party : IESG From wwwrun@rfc-editor.org Fri Jan 29 12:56:40 2010 Return-Path: X-Original-To: smime@core3.amsl.com Delivered-To: smime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1D6843A67DA for ; Fri, 29 Jan 2010 12:56:40 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.562 X-Spam-Level: X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, NO_RELAYS=-0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PwqlO4xYPOsM for ; Fri, 29 Jan 2010 12:56:39 -0800 (PST) Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 7000E3A659A for ; Fri, 29 Jan 2010 12:56:39 -0800 (PST) Received: by rfc-editor.org (Postfix, from userid 30) id 306FDE06B4; Fri, 29 Jan 2010 12:57:03 -0800 (PST) To: turners@ieca.com, jimsch@exmsft.com, tim.polk@nist.gov, pasi.eronen@nokia.com, turners@ieca.com, blaker@gmail.com From: RFC Errata System Message-Id: <20100129205703.306FDE06B4@rfc-editor.org> Date: Fri, 29 Jan 2010 12:57:03 -0800 (PST) Cc: ah@TR-Sys.de, rfc-editor@rfc-editor.org, smime@ietf.org Subject: [smime] [Editorial Errata Reported] RFC5752 (2029) X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2010 20:56:40 -0000 The following errata report has been submitted for RFC5752, "Multiple Signatures in Cryptographic Message Syntax (CMS)". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5752&eid=2029 -------------------------------------- Type: Editorial Reported by: Alfred Hoenes Section: 4.1, pg. 7 Original Text ------------- - The signer MUST: -- Retain the existing signerInfo objects. | -- Include their signerInfo object(s). Corrected Text -------------- - The signer MUST: -- Retain the existing signerInfo objects. | -- Include their own signerInfo object(s). Notes ----- Rationale: Remove possible ambiguity of language. (Keep for update!) Instructions: ------------- This errata 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 (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5752 (draft-ietf-smime-multisig-05) -------------------------------------- Title : Multiple Signatures in Cryptographic Message Syntax (CMS) Publication Date : January 2010 Author(s) : S. Turner, J. Schaad Category : PROPOSED STANDARD Source : S/MIME Mail Security Area : Security Stream : IETF Verifying Party : IESG From turners@ieca.com Fri Jan 29 13:12:34 2010 Return-Path: X-Original-To: smime@core3.amsl.com Delivered-To: smime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 693083A688B for ; Fri, 29 Jan 2010 13:12:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rUkA8BCFY6iQ for ; Fri, 29 Jan 2010 13:12:33 -0800 (PST) Received: from smtp102.biz.mail.re2.yahoo.com (smtp102.biz.mail.re2.yahoo.com [68.142.229.216]) by core3.amsl.com (Postfix) with SMTP id 4A5653A6889 for ; Fri, 29 Jan 2010 13:12:33 -0800 (PST) Received: (qmail 70963 invoked from network); 29 Jan 2010 21:12:54 -0000 Received: from pool-96-231-119-106.washdc.east.verizon.net (turners@96.231.119.106 with plain) by smtp102.biz.mail.re2.yahoo.com with SMTP; 29 Jan 2010 13:12:53 -0800 PST X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ X-YMail-OSG: rux9OtEVM1lidYC.1oSl0ilM7iT037vY4gxGngxMSeU5dlf4xQNwV2R3p3uGaf4hw6aCHY6fENE5WT5_as7_u8BZu6ga0xlZbi0IxUfF5Vf3fzOqtH9xDR7OMDbJ55eCSY.pX4f0U0NEAxdvw4iZpiISA.jO_N8ZnHhjW6zfuD.cLOsCnx65OEjiUnz_bhyiuZd4Tp8jNAO.FyAhWpf6.8yYbzRfzi1i8IPM1AEhfsNkRIsjswhG0YdKOT9rKVAtFLxhWZV_4k_KAsyzdTqWgzkW2sk4X08fvcnuhxtmplQz4JqriZ7FYR5u2dURNDPvcD3lcpwdzV32bRDR7xb0F_pd5_Ao8w99fe7LyOdqPw7ldzgd9ckq1JNLqAlS8JgtHcFuzD4gCRF.ONBWw3J8VhrEaVN2g.kKoj0D4_ugVo.JvQa1YNdI0ZMccLfibpfaTJeMJRkRM6vMYorPJ5pUFwkGLDMH_uFKmS_HZAxiFFLAcHWUpIPsRwI8GhXbUlKbn.h5ppjXgY0OfOsoHgQGnFXxsFxXSUyJUj6YEpLLD8kxxX7U.U91qoDB2LWm4M27MLwKyt8dNYIUme8- X-Yahoo-Newman-Property: ymail-3 Message-ID: <4B634F55.4040306@ieca.com> Date: Fri, 29 Jan 2010 16:12:53 -0500 From: Sean Turner User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: RFC Errata System References: <20100128090112.8A12A130001@rfc-editor.org> In-Reply-To: <20100128090112.8A12A130001@rfc-editor.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ah@TR-Sys.de, smime@ietf.org, pasi.eronen@nokia.com Subject: Re: [smime] [Editorial Errata Reported] RFC5652 (2026) X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2010 21:12:34 -0000 The proposed correction is appropriate, and does not result in a technical change to the RFC. I have no objection to this errata. spt RFC Errata System wrote: > The following errata report has been submitted for RFC5652, > "Cryptographic Message Syntax (CMS)". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=5652&eid=2026 > > -------------------------------------- > Type: Editorial > Reported by: Alfred Hoenes > > Section: 5.3, pg. 15 > > Original Text > ------------- > [[ around the page break from page 14 to page 15: ]] > > digestAlgorithm identifies the message digest algorithm, and any > associated parameters, used by the signer. The message digest is > computed on either the content being signed or the content > << page break >> > together with the signed attributes using the process described in > Section 5.4. The message digest algorithm SHOULD be among those > | listed in the digestAlgorithms field of the associated SignerData. > ^^^^^^^^^^ > Implementations MAY fail to validate signatures that use a digest > algorithm that is not included in the SignedData digestAlgorithms > set. > > > Corrected Text > -------------- > digestAlgorithm identifies the message digest algorithm, and any > associated parameters, used by the signer. The message digest is > computed on either the content being signed or the content > together with the signed attributes using the process described in > Section 5.4. The message digest algorithm SHOULD be among those > | listed in the digestAlgorithms field of the associated SignedData. > Implementations MAY fail to validate signatures that use a digest > algorithm that is not included in the SignedData digestAlgorithms > set. > > > Notes > ----- > Rationale: > There's no such ASN.1 type/object named "SignerData" in relevant > specifications. Text should refer to "SignedData" instead. > This is an undetected legacy flaw inherited literally from RFC 2630, > RFC 3369, and RFC 3852. > > Instructions: > ------------- > This errata 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 (IESG) > 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 turners@ieca.com Fri Jan 29 13:14:58 2010 Return-Path: X-Original-To: smime@core3.amsl.com Delivered-To: smime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 847EC3A688B for ; Fri, 29 Jan 2010 13:14:58 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 49KiUKAzm5SG for ; Fri, 29 Jan 2010 13:14:57 -0800 (PST) Received: from smtp104.biz.mail.re2.yahoo.com (smtp104.biz.mail.re2.yahoo.com [206.190.52.173]) by core3.amsl.com (Postfix) with SMTP id 5918D3A6889 for ; Fri, 29 Jan 2010 13:14:57 -0800 (PST) Received: (qmail 10912 invoked from network); 29 Jan 2010 21:15:18 -0000 Received: from pool-96-231-119-106.washdc.east.verizon.net (turners@96.231.119.106 with plain) by smtp104.biz.mail.re2.yahoo.com with SMTP; 29 Jan 2010 13:15:17 -0800 PST X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ X-YMail-OSG: _Pj9uRYVM1nAuVqJp84fnzovlllqXZzvOP37dAzDWpVWyIxGSxDoZuputwFAnQBDTjo7SdHJH87eslVGusi7wPv.J6ryeM7UeZb8djOvUkJevFgTkQLJkvBgPHNsPY_Hjr2.ygKlMT4uaGHkCv5J.b_KkgMe.oe9Fzb2OLzSNyM_g0G3wxugavjBq5lDjpQStPrNTCXOhH_y49d5Vlv32kQoDdfWAZ99PakmITk8fHZlSBDC2Bg_dAEr4b5s9fI3l2d37INdrepCi.RJ__yVn._.BZsjAPyAhGhW0SY6YkntW32Uhe7NBbi.DC_jr4CPan2XyyxgYum9__OOtSmA.ymWAz4wgm9.I0ldBGQnkynOd4SHy0FjeS4eRZWY8vqbMCbdcEa3ktC8rigk8Dlcy.x91eKELt7BVQ4OCoSIdvpN24wOc3J0ix1BbzxyuPTQ6Fm250mp2fgzIiH4GZsDr6x8a0KjQxNygT9W0iaYg2QXw5yzw1.llps_buJlOT1.vMTyMs.ZYhZSbn5gB7y6Xhgv7Gu2GAEQMXRHip7.NDI0Yl6mmJ_FnW.h5d3zpJMLGf5x.T7av3tt.98- X-Yahoo-Newman-Property: ymail-3 Message-ID: <4B634FE5.9040203@ieca.com> Date: Fri, 29 Jan 2010 16:15:17 -0500 From: Sean Turner User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: RFC Errata System References: <20100129205123.15FC1E06B0@rfc-editor.org> In-Reply-To: <20100129205123.15FC1E06B0@rfc-editor.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ah@TR-Sys.de, smime@ietf.org, pasi.eronen@nokia.com, jimsch@exmsft.com Subject: Re: [smime] [Technical Errata Reported] RFC5752 (2027) X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2010 21:14:58 -0000 The proposed correction is appropriate. I have no objection to this errata. spt RFC Errata System wrote: > The following errata report has been submitted for RFC5752, > "Multiple Signatures in Cryptographic Message Syntax (CMS)". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=5752&eid=2027 > > -------------------------------------- > Type: Technical > Reported by: Alfred Hoenes > > Section: 5, pg. 8 > > Original Text > ------------- > This section describes recommended processing of signatures when > | there are more than one SignerInfo present in a message. This may be > due to either multiple SignerInfo objects being present in a single > | SignedData object or multiple SignerData objects embedded in each > other. > > [...] > > Order of operations: > > 1) Evaluate each SignerInfo object independently. > > 2) Combine the results of all SignerInfo objects at the same level > | (i.e., attached to the same SignerData object). > > | 3) Combine the results of the nested SignerData objects. Note that > this should ignore the presence of other CMS objects between the > SignedData objects. > > > > Corrected Text > -------------- > This section describes recommended processing of signatures when > | there is more than one SignerInfo object present in a message. This > may be due to either multiple SignerInfo objects being present in a > | single SignedData object or multiple SignedData objects embedded in > each other. > > [...] > > Order of operations: > > 1) Evaluate each SignerInfo object independently. > > 2) Combine the results of all SignerInfo objects at the same level > | (i.e., attached to the same SignedData object). > > | 3) Combine the results of the nested SignedData objects. Note that > this should ignore the presence of other CMS objects between the > SignedData objects. > > > > Notes > ----- > Rationale: > There's no such ASN.1 type/object "SignerData". > Based on the importance of referencing the correct type/object, > the correction to "SignedData" is classified as 'Technical'. > Also a clarification and fix is applied in the first sentence. > > Instructions: > ------------- > This errata 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 (IESG) > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC5752 (draft-ietf-smime-multisig-05) > -------------------------------------- > Title : Multiple Signatures in Cryptographic Message Syntax (CMS) > Publication Date : January 2010 > Author(s) : S. Turner, J. Schaad > Category : PROPOSED STANDARD > Source : S/MIME Mail Security > Area : Security > Stream : IETF > Verifying Party : IESG > From turners@ieca.com Fri Jan 29 13:15:55 2010 Return-Path: X-Original-To: smime@core3.amsl.com Delivered-To: smime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D6EB83A6967 for ; Fri, 29 Jan 2010 13:15:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7lNOzJU6+roa for ; Fri, 29 Jan 2010 13:15:54 -0800 (PST) Received: from smtp106.biz.mail.re2.yahoo.com (smtp106.biz.mail.re2.yahoo.com [206.190.52.175]) by core3.amsl.com (Postfix) with SMTP id 653713A6943 for ; Fri, 29 Jan 2010 13:15:54 -0800 (PST) Received: (qmail 62249 invoked from network); 29 Jan 2010 21:16:13 -0000 Received: from pool-96-231-119-106.washdc.east.verizon.net (turners@96.231.119.106 with plain) by smtp106.biz.mail.re2.yahoo.com with SMTP; 29 Jan 2010 13:16:13 -0800 PST X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ X-YMail-OSG: lBIZlOEVM1l52w_tIlp0ZehBoekF_jdxJybJiWPQlYfi6PaR_gkrfauEjAUV1Y3VjeKSfIHAv6iNh6h5veHQ_z82R1yJojrh6tHvDmJVeOWvPUyWZaTjFEhPpapTLxWQZ841SfgSeeRaOwCZ7vg9HT20y5dbkXnp4Mvb4dRbXtAddAsPN1x6R8KZZaunYHkhGCpedF5TSU00pl1TARtTlaQBXJGCm2Nn01geG.qWPJ6I7MjimT9mEda.FjHHf.99FinKPpSsEl__DpRivlhXmAxEMOf0iW6JD87s9iVyAGIKlfWy.hTwiRQiolS.acj7PL9ok5InoM_BNweKCTmNtnnmKpnKG7juSMW4Og1bnwhA2zowc8Lj.nzglNQl.zWAP7plw1SFe4Yr1cXpdUiz_u9SrHSeRchtBuQVe7TPv55aRiP9e5AzRwZRxkuIqw_O9cpYvflxwU6SQt4gwQw3lljWFUV5LvZkt6coZCZFlhaWGz59W0Zrx_kkm_THIIShv.DTmg1zZ.KuiNPpApPEwqUeCi8bchh8yw1tWJESXd31apvC9jsq9CPHm.tZTDvVBAwJkjZ2E7UPCa8- X-Yahoo-Newman-Property: ymail-3 Message-ID: <4B63501C.9080701@ieca.com> Date: Fri, 29 Jan 2010 16:16:12 -0500 From: Sean Turner User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: RFC Errata System References: <20100129205451.749E7E06B3@rfc-editor.org> In-Reply-To: <20100129205451.749E7E06B3@rfc-editor.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ah@TR-Sys.de, smime@ietf.org, pasi.eronen@nokia.com, jimsch@exmsft.com Subject: Re: [smime] [Editorial Errata Reported] RFC5752 (2028) X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2010 21:15:56 -0000 The proposed correction is appropriate, and does not result in a technical change to the RFC. I have no objection to this errata. spt RFC Errata System wrote: > The following errata report has been submitted for RFC5752, > "Multiple Signatures in Cryptographic Message Syntax (CMS)". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=5752&eid=2028 > > -------------------------------------- > Type: Editorial > Reported by: Alfred Hoenes > > Section: 2.1, pg. 6 > > Original Text > ------------- > The following is an example: > > SignedData > DigestAlg=sha1,sha256 > SignerInfo1 SignerInfo2 > digestAlg=sha1 digestAlg=sha256 > signatureAlg=dsawithsha1 signatureAlg=ecdsawithsha256 > signedAttrs= signedAttrs= > signingTime1 signingTime1 > messageDigest1 messageDigest2 > multiSig1= multiSig2= > bodyHash=sha256 bodyHash=sha1 > signAlg=ecdsawithsha256 signAlg=dsawithsha1 > | signAttrsHash= signAttrsHash= > | algID=sha1 algID=sha256 > | hash=value1 hash=value2 > > > > > Corrected Text > -------------- > The following is an example: > > SignedData > DigestAlg=sha1,sha256 > SignerInfo1 SignerInfo2 > digestAlg=sha1 digestAlg=sha256 > signatureAlg=dsawithsha1 signatureAlg=ecdsawithsha256 > signedAttrs= signedAttrs= > signingTime1 signingTime1 > messageDigest1 messageDigest2 > multiSig1= multiSig2= > bodyHash=sha256 bodyHash=sha1 > signAlg=ecdsawithsha256 signAlg=dsawithsha1 > | signAttrsHash= signAttrsHash= > | algID=sha1 algID=sha256 > | hash=value1 hash=value2 > > > > > Notes > ----- > Rationale: > Fixed indentation for consistency and clarity > (visual indication of subordinate elements). > > Instructions: > ------------- > This errata 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 (IESG) > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC5752 (draft-ietf-smime-multisig-05) > -------------------------------------- > Title : Multiple Signatures in Cryptographic Message Syntax (CMS) > Publication Date : January 2010 > Author(s) : S. Turner, J. Schaad > Category : PROPOSED STANDARD > Source : S/MIME Mail Security > Area : Security > Stream : IETF > Verifying Party : IESG > From turners@ieca.com Fri Jan 29 13:16:31 2010 Return-Path: X-Original-To: smime@core3.amsl.com Delivered-To: smime@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 384363A6A50 for ; Fri, 29 Jan 2010 13:16:31 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NVLZyc+I6aSB for ; Fri, 29 Jan 2010 13:16:30 -0800 (PST) Received: from smtp102.biz.mail.re2.yahoo.com (smtp102.biz.mail.re2.yahoo.com [68.142.229.216]) by core3.amsl.com (Postfix) with SMTP id 1E2B73A6943 for ; Fri, 29 Jan 2010 13:16:30 -0800 (PST) Received: (qmail 73937 invoked from network); 29 Jan 2010 21:16:53 -0000 Received: from pool-96-231-119-106.washdc.east.verizon.net (turners@96.231.119.106 with plain) by smtp102.biz.mail.re2.yahoo.com with SMTP; 29 Jan 2010 13:16:53 -0800 PST X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ X-YMail-OSG: vXVseRYVM1m10.8VUUAgUXtzJUZvWATf.OD2U1gTRSi3RcAXXZQeq2v_FrmAv3ULnMA3JqPoGdIMliBI8KjXW6WPHUNVRZsWkqJwmJP9r9FoY42vZ1u3wcEUiDPhA6WagBkclpKpoq3t_ihujfrtSwS32Y5a3p0wmwtjCY3KRzjD18IB2m8pPH6sifOCtinjeobdWtI2rMSVdbIvou1h0Fil7DT3Yw91FlUS.4gUimr.bPQOOtxck25hmR2iJSkIKcJSSHZcB.tLsRwrPWBAR8438D3R70ode46TzAQcXwGuq3yyX6hfszU0x1Rkwpy22W_RTwPkwL9ue.xXb29CP.AecnLuolMjVIdkI2dBuBT66Jzmxx48X8ySvUve84SVlKz12rQdjlIc9KZBwWaNc2FapckPxqRtoJNCpxZSt1nq2BYq593mDfdUlm7eCVrIggeMVGtCXuxq4YU9ctz_1ZXgjNqmCn26G857ciF_7zyPBdbgp_l5SvrasTfXSojYdafVB5YZ8zBofqkEQ.0HHTYfA2h5R.0s0B_iDHgWxgClN99ZbCrDNqbTEc.urCnnDqK1VJ35UrRgXgc- X-Yahoo-Newman-Property: ymail-3 Message-ID: <4B635044.10507@ieca.com> Date: Fri, 29 Jan 2010 16:16:52 -0500 From: Sean Turner User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: RFC Errata System References: <20100129205703.306FDE06B4@rfc-editor.org> In-Reply-To: <20100129205703.306FDE06B4@rfc-editor.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ah@TR-Sys.de, smime@ietf.org, pasi.eronen@nokia.com, jimsch@exmsft.com Subject: Re: [smime] [Editorial Errata Reported] RFC5752 (2029) X-BeenThere: smime@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: SMIME Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2010 21:16:31 -0000 The proposed correction is appropriate, and does not result in a technical change to the RFC. I have no objection to this errata. spt RFC Errata System wrote: > The following errata report has been submitted for RFC5752, > "Multiple Signatures in Cryptographic Message Syntax (CMS)". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=5752&eid=2029 > > -------------------------------------- > Type: Editorial > Reported by: Alfred Hoenes > > Section: 4.1, pg. 7 > > Original Text > ------------- > - The signer MUST: > > -- Retain the existing signerInfo objects. > > | -- Include their signerInfo object(s). > > > Corrected Text > -------------- > - The signer MUST: > > -- Retain the existing signerInfo objects. > > | -- Include their own signerInfo object(s). > > > Notes > ----- > Rationale: Remove possible ambiguity of language. > (Keep for update!) > > Instructions: > ------------- > This errata 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 (IESG) > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC5752 (draft-ietf-smime-multisig-05) > -------------------------------------- > Title : Multiple Signatures in Cryptographic Message Syntax (CMS) > Publication Date : January 2010 > Author(s) : S. Turner, J. Schaad > Category : PROPOSED STANDARD > Source : S/MIME Mail Security > Area : Security > Stream : IETF > Verifying Party : IESG >