Comments on draft-ietf-smime-cmskea-02
"Jim Schaad (Exchange)" <jimsch@EXCHANGE.MICROSOFT.com> Thu, 18 November 1999 19:18 UTC
Received: from ns.secondary.com (ns.secondary.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11058 for <smime-archive@odin.ietf.org>; Thu, 18 Nov 1999 14:18:24 -0500 (EST)
Received: (from majordomo@localhost) by ns.secondary.com (8.9.3/8.9.3) id KAA02688 for ietf-smime-bks; Thu, 18 Nov 1999 10:40:39 -0800 (PST)
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59]) by ns.secondary.com (8.9.3/8.9.3) with ESMTP id KAA02683 for <ietf-smime@imc.org>; Thu, 18 Nov 1999 10:40:38 -0800 (PST)
Received: by dfssl with Internet Mail Service (5.5.2650.21) id <W8XXNPP5>; Thu, 18 Nov 1999 10:41:33 -0800
Message-ID: <EAB5B8B61A04684198FF1D0C1B3ACD194A7131@dino.dns.microsoft.com>
From: "Jim Schaad (Exchange)" <jimsch@EXCHANGE.MICROSOFT.com>
To: "John Pawling (E-mail)" <jsp@jgvandyke.com>
Cc: "Ietf-Smime (E-mail)" <ietf-smime@imc.org>
Subject: Comments on draft-ietf-smime-cmskea-02
Date: Thu, 18 Nov 1999 10:40:38 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF31F4.896D87C2"
Sender: owner-ietf-smime@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-ID: <ietf-smime.imc.org>
List-Unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>
1. It would be useful if section references to CMS included section numbers rather than just section titles. An example is the first paragraph of section 4. 2. Section 4.2.2 --- One of the discussion that I have every so often with you and Russ deals with the question of validating the originators certificate during the decrypt process. The current text makes no reference to doing this or what should happen if this validation fails. Is this what you want? Do you want to put in some text about doing the validation and what to do if it fails? Suggested text could run along the lines of "If the originators certificate is used for the purposes of origination authenticiation, then the originators certificate MUST be validated prior to decrypting the message and the decryption MUST NOT proceed if the validation fails." 3. The document is missing the specification of the SMimeCapability field to be used for CMSKEA. Please include a small section with the necessary parameters and a binary version of the encoded attribute so that everyone uses the same byte sequence. jim
- Comments on draft-ietf-smime-cmskea-02 Jim Schaad (Exchange)
- RE: Comments on draft-ietf-smime-cmskea-02 Pawling, John
- RE: Comments on draft-ietf-smime-cmskea-02 Jim Schaad (Exchange)