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

Russ Housley <housley@spyrus.com> Wed, 17 March 1999 06:06 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 BAA20220 for <smime-archive@odin.ietf.org>; Wed, 17 Mar 1999 01:06:47 -0500 (EST)
Received: (from majordomo@localhost) by mail.proper.com (8.8.8/8.8.5) id VAA14548 for ietf-smime-bks; Tue, 16 Mar 1999 21:08:46 -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 VAA14542 for <ietf-smime@imc.org>; Tue, 16 Mar 1999 21:08:45 -0800 (PST)
Received: from rhousley_laptop.spyrus.com (dial03.spyrus.com [207.212.34.123]) by spyrus.com (8.7.6/8.7.3/arc) with SMTP id VAA23610; Tue, 16 Mar 1999 21:14:10 -0800 (PST)
Message-Id: <4.1.19990317000628.009dc750@mail.spyrus.com>
X-Sender: rhousley@mail.spyrus.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1
Date: Wed, 17 Mar 1999 00:07:30 -0500
To: Bruce Greenblatt <bgreenblatt@directory-applications.com>
From: Russ Housley <housley@spyrus.com>
Subject: Re: More on KEKIdentifiers, and a suggested addition to CMS
Cc: ietf-smime@imc.org
In-Reply-To: <3.0.6.32.19990316094910.007baa30@pop.walltech.com>
References: <4.1.19990313171127.009d8cc0@mail.spyrus.com> <4.2.0.29.19990311134917.0096df00@mail.imc.org> <00e901be6c2a$ded01e40$0400000a@jrwork>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
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>

No.  The current document meets all of the original requirements.  We are
considering an enhancement that is beyond the original charter.

Russ

At 09:49 AM 3/16/99 -0800, Bruce Greenblatt wrote:
>At 05:22 PM 3/13/99 -0500, Russ Housley wrote:
>>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.
>>
>
>I have a question about this.  Are you producing a document with a known
>deficiency that you intend to correct later in the standards process?  It
>appears to me that making the change that has been suggested using the
>extension mechanism after it has been released as PS would likely cause CMS
>to move backwards in the standards process, and not forwards.  Thus, the
>whole process would be substantially delayed.  You're better off correcting
>the problem now with the "..." or extension mechanism or whatever as part
>of WG last call, and moving on rather than attempting to correct it later,
>and then being shifted back in the standardization process...
>
>Bruce
>================================================
>Bruce Greenblatt             
>bgreenblatt@directory-applications.com
>http://www.directory-applications.com
>================================================