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

Bruce Greenblatt <bgreenblatt@directory-applications.com> Tue, 16 March 1999 18:59 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 NAA12559 for <smime-archive@odin.ietf.org>; Tue, 16 Mar 1999 13:59:39 -0500 (EST)
Received: (from majordomo@localhost) by mail.proper.com (8.8.8/8.8.5) id JAA23668 for ietf-smime-bks; Tue, 16 Mar 1999 09:43:43 -0800 (PST)
Received: from ns2.walltech.com (ns2.walltech.com [208.195.156.18]) by mail.proper.com (8.8.8/8.8.5) with ESMTP id JAA23664 for <ietf-smime@imc.org>; Tue, 16 Mar 1999 09:43:42 -0800 (PST)
Received: from iris (user51.sj.dialup.innetix.com [209.172.68.114]) by ns2.walltech.com (8.8.7/8.8.7/walltech-1.28h) with SMTP id JAA12013; Tue, 16 Mar 1999 09:49:55 -0800 (PST)
Message-Id: <3.0.6.32.19990316094910.007baa30@pop.walltech.com>
X-Sender: bgreenblatt@pop.walltech.com
X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32)
Date: Tue, 16 Mar 1999 09:49:10 -0800
To: Russ Housley <housley@spyrus.com>, ietf-smime@imc.org
From: Bruce Greenblatt <bgreenblatt@directory-applications.com>
Subject: Re: More on KEKIdentifiers, and a suggested addition to CMS
In-Reply-To: <4.1.19990313171127.009d8cc0@mail.spyrus.com>
References: <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>

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
================================================