READ First ***! S/MIME minutes -CMS

Denis Pinkas <Denis.Pinkas@bull.net> Fri, 09 April 1999 14:16 UTC

Received: from mail.proper.com (mail.proper.com [206.86.127.224]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02758 for <smime-archive@odin.ietf.org>; Fri, 9 Apr 1999 10:16:15 -0400 (EDT)
Received: (from majordomo@localhost) by mail.proper.com (8.8.8/8.8.5) id GAA27695 for ietf-smime-bks; Fri, 9 Apr 1999 06:27:44 -0700 (PDT)
Received: from clbull.frcl.bull.fr (clbull.frcl.bull.fr [129.182.1.20]) by mail.proper.com (8.8.8/8.8.5) with ESMTP id GAA27691 for <ietf-smime@imc.org>; Fri, 9 Apr 1999 06:27:41 -0700 (PDT)
Received: from k2.frcl.bull.fr (k2.frcl.bull.fr [129.182.100.2]) by clbull.frcl.bull.fr (8.9.1a/8.9.1) with ESMTP id PAA25678; Fri, 9 Apr 1999 15:27:32 +0200
Received: from bull.net (frcls6118.frcl.bull.fr [129.182.109.213]) by k2.frcl.bull.fr (AIX4.2/UCB 8.7/8.7) with ESMTP id PAA26258; Fri, 9 Apr 1999 15:27:33 +0200 (DFT)
Message-ID: <370E004D.115A5D82@bull.net>
Date: Fri, 09 Apr 1999 15:27:41 +0200
From: Denis Pinkas <Denis.Pinkas@bull.net>
Organization: Bull
X-Mailer: Mozilla 4.06 [fr] (Win95; I)
MIME-Version: 1.0
To: Russ Housley <housley@spyrus.com>
CC: S-MIME / IETF <ietf-smime@imc.org>, John Pawling <jsp@jgvandyke.com>
Subject: READ First ***! S/MIME minutes -CMS
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-smime@imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-Unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>
Content-Transfer-Encoding: 7bit

I just realized that I took the wrong file so half of my comments
are inappropriate.

The minutes are not correct, but the new CMS 12 document does
incorporate some changes.

So, please, Russ accept my apologies.

Here is the text.

5.6  Message Signature Verification Process

   The input to the signature verification process includes the
result
   of the message digest calculation process and the signer's
public
   key.  The recipient may obtain the correct public key for the
signer
   by any means, but the preferred method is from a certificate
obtained
   from the SignedData certificates field.  The selection and
validation
   of the signer's public key may be based on certification path
   validation (see [PROFILE]) as well as other external context,
but is
   beyond the scope of this document.  The details of the
signature
   verification depend on the signature algorithm employed.

Regards,

Denis