RE: More on KEKIdentifiers, and a suggested addition to CMS

jsp@jgvandyke.com (John Pawling) Fri, 12 March 1999 16:10 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 LAA04339 for <smime-archive@odin.ietf.org>; Fri, 12 Mar 1999 11:10:20 -0500 (EST)
Received: (from majordomo@localhost) by mail.proper.com (8.8.8/8.8.5) id GAA15718 for ietf-smime-bks; Fri, 12 Mar 1999 06:40:51 -0800 (PST)
Received: from apollo.jgvandyke.com (apollo.jgvandyke.com [158.189.10.100]) by mail.proper.com (8.8.8/8.8.5) with ESMTP id GAA15714 for <ietf-smime@imc.org>; Fri, 12 Mar 1999 06:40:50 -0800 (PST)
Received: from ajsn101.jgvandyke.com (ajsn101.jgvandyke.com [158.189.2.101]) by apollo.jgvandyke.com (8.8.8/8.8.8) with SMTP id JAA22316; Fri, 12 Mar 1999 09:52:52 -0500 (EST)
Received: from ajpc81 by ajsn101.jgvandyke.com (SMI-8.6/SMI-SVR4) id JAA07743; Fri, 12 Mar 1999 09:50:11 -0500
Date: Fri, 12 Mar 1999 09:50:11 -0500
Message-Id: <199903121450.JAA07743@ajsn101.jgvandyke.com>
X-Sender: jsp@ajsn101
X-Mailer: Windows Eudora Version 1.4.4
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: ietf-smime@imc.org
From: jsp@jgvandyke.com
Subject: RE: More on KEKIdentifiers, and a suggested addition to CMS
Cc: burt@RSA.COM
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>

Jim and Friends,

I agree with Jim's message.  When I expressed support for Peter's proposal
to enhance the CMS RecipientInfo syntax, I assumed that there was consensus
in the PKCS-15 community regarding the proposal.  Based on subsequent e-mail
traffic, that assumption has been proved to be false.  Therefore, I agree
with Jim that the CMS RecipientInfo syntax should remain unchanged.

- John Pawling 


At 10:20 AM 3/10/99 -0800, Jim Schaad (Exchange) wrote:
>John & Peter,
>
>At this point in time I am not willing to support this. I have two reasons
>for this
>
>1.  I want to get CMS approved, and there are other options for how to
>approach this (such as a new I-D) and we know a new version of CMS is coming
>soon to deal with OEAP
>
>2.  I don't think this is the correct set of items that are needed.  You
>have not proposed an appropriate set of text for section 12.  I don't
>understand why the Content Encrytion Alg should be encoded twice.  I don't
>understand why the KEK Wrap algorithm is not specified.  I just don't think
>this is complete yet.
>
>jim
>
>