S/MIME Minutes - CMS section
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 KAA02748 for <smime-archive@odin.ietf.org>; Fri, 9 Apr 1999 10:16:14 -0400 (EDT)
Received: (from majordomo@localhost) by mail.proper.com (8.8.8/8.8.5) id GAA27587 for ietf-smime-bks; Fri, 9 Apr 1999 06:18:54 -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 GAA27581 for <ietf-smime@imc.org>; Fri, 9 Apr 1999 06:18:39 -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 PAA11614; Fri, 9 Apr 1999 15:18:47 +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 PAA28334; Fri, 9 Apr 1999 15:18:31 +0200 (DFT)
Message-ID: <370DFE2E.DB5CC234@bull.net>
Date: Fri, 09 Apr 1999 15:18:39 +0200
From: Denis Pinkas <Denis.Pinkas@bull.net>
Organization: Bull
X-Mailer: Mozilla 4.06 [fr] (Win95; I)
MIME-Version: 1.0
To: John Pawling <jsp@jgvandyke.com>, Russ Housley <housley@spyrus.com>
CC: S-MIME / IETF <ietf-smime@imc.org>
Subject: S/MIME Minutes - CMS section
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
John, I only got the time to look at the minutes yesterday and observed a difference between what happened during the meeting and what is written. In the section about CMS, it is said: " Russ asked if there were any other unresolved issued regarding CMS. Denis Pinkas stated that he believes that CMS should specify how key validation is performed. He is especially concerned with the case in which multiple Certification Authority (CA) certificates contain the same public key. A vast majority of the meeting attendees decided that the PKIX X.509 Certificate and CRL Profile (RFC2459) (referred to by the CERT I-D) specifies how key validation is performed and that CMS should not replicate that information." On that point, during the session Russ said that he was willing to incorporate additional text in the security consideration section that I had provided to him to address this concern. I did not commented on this and no one else. There was no strawpol either on this issue. A more correct formulation should be: "Russ said Denis Pinkas had been asking for some addditional text to explain how the right public key to perform the verification of the signature was obtained in section 5.6. Denis Pinkas had provided to Russ some text for additional materail to the security consideration section and a pointer to it in the section 5.6. Russ said he would incoporate the new text in the next draft. " Note that this has nothing to do with how key validation is performed, which is indeed explained in the PKIX X.509 Certificate and CRL Profile (RFC2459) (referred to by the CERT I-D), so it does not duplicate any text. After the meeting Russ sent me privately an E-mail to say that he finally founded the text too big and instead proposed me to change some text of the section 5.6. I replied that this was acceptable (although I would have prefered the first way). Now when looking at the document (cms-12) I find the text unchanged. I would like that we correct the minutes, if possible, but what I care much more is the content of CMS. I am still requesting changes to CMS section 5.6. one way or the other to address this issue. Russ ? Regards, Denis
- S/MIME Minutes - CMS section Denis Pinkas
- Re: S/MIME Minutes - CMS section John Pawling
- Re: S/MIME Minutes - CMS section Denis Pinkas