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

Russ Housley <housley@spyrus.com> Tue, 16 March 1999 17:08 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 MAA11593 for <smime-archive@odin.ietf.org>; Tue, 16 Mar 1999 12:08:07 -0500 (EST)
Received: (from majordomo@localhost) by mail.proper.com (8.8.8/8.8.5) id HAA22280 for ietf-smime-bks; Tue, 16 Mar 1999 07:28:53 -0800 (PST)
Received: from spyrus.com (mail.spyrus.com [207.212.34.30]) by mail.proper.com (8.8.8/8.8.5) with ESMTP id HAA22276 for <ietf-smime@imc.org>; Tue, 16 Mar 1999 07:28:51 -0800 (PST)
Received: from rhousley_laptop.spyrus.com (dial01.spyrus.com [207.212.34.121]) by spyrus.com (8.7.6/8.7.3/arc) with SMTP id HAA06021 for <ietf-smime@imc.org>; Tue, 16 Mar 1999 07:34:47 -0800 (PST)
Message-Id: <4.1.19990313171127.009d8cc0@mail.spyrus.com>
Message-Id: <4.1.19990313171127.009d8cc0@mail.spyrus.com>
X-Sender: rhousley@mail.spyrus.com (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Sat, 13 Mar 1999 17:22:21 -0500
To: ietf-smime@imc.org
From: Russ Housley <housley@spyrus.com>
Subject: Re: More on KEKIdentifiers, and a suggested addition to CMS
In-Reply-To: <4.2.0.29.19990311134917.0096df00@mail.imc.org>
References: <00e901be6c2a$ded01e40$0400000a@jrwork>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
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: 8bit

All:

I agree with Paul Hoffman.  We should proceed with CMS so that the S/MIME
v3 set of documents can become Proposed Standards.  Using the list, we can
discuss the best way to handle password-based key management.  We can do as
many Internet-Drafts as necessary to sort this out.  Once we reach
concensus, we can add the that technique to CMS when the document
progresses from Proposed Standard to Draft Standard.

Of the suggestions discussed so far, I am leaning toward the one made by
Magnus Nyström.  This seems to provide all of the capability needed for
PKCS#15.

On the other hand, the proposal made by Rich Ankney (and seconded by John
Ross) provides a open solution for new techniques are they are needed.  I
have concerns that this may not be the best solution for interoperability.
Rich can you post the ANSI X9F3 requirements for CKM?  Please start a new
thread for that topic.

Russ


At 01:53 PM 3/11/99 -0800, Paul Hoffman / IMC wrote:
>Folks:
>
>Peter has posted an Internet Draft for an addition to CMS. I think it is 
>very late for us to be adding things for which there is disagreement on how 
>to put it in. We can discuss Peter's draft and decide if we want to pass it 
>out of the working group. If we do, it can be a stand-alone RFC. If it gets 
>two independent implementations, we might fold it into the CMS RFC (if we 
>ever get there.....) when we move from Proposed Standard to Draft Standard.
>
>--Paul Hoffman, Director
>--Internet Mail Consortium