Protocol Action: Reuse of CMS Content Encryption Keys to Proposed Standard

The IESG <iesg-secretary@ietf.org> Mon, 01 October 2001 11:47 UTC

Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA11934 for <smime-archive@odin.ietf.org>; Mon, 1 Oct 2001 07:47:39 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.6/8.11.3) id f91Ax1X08248 for ietf-smime-bks; Mon, 1 Oct 2001 03:59:01 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by above.proper.com (8.11.6/8.11.3) with ESMTP id f91AwxD08244 for <ietf-smime@imc.org>; Mon, 1 Oct 2001 03:59:00 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10682; Mon, 1 Oct 2001 06:58:54 -0400 (EDT)
Message-Id: <200110011058.GAA10682@ietf.org>
To: IETF-Announce:;
Cc: RFC Editor <rfc-editor@isi.edu>
Cc: Internet Architecture Board <iab@isi.edu>
Cc: ietf-smime@imc.org
From: The IESG <iesg-secretary@ietf.org>
Subject: Protocol Action: Reuse of CMS Content Encryption Keys to Proposed Standard
Date: Mon, 01 Oct 2001 06:58:54 -0400
Sender: owner-ietf-smime@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smime/mail-archive/>
List-ID: <ietf-smime.imc.org>
List-Unsubscribe: <mailto:ietf-smime-request@imc.org?body=unsubscribe>



The IESG has approved the Internet-Draft 'Reuse of CMS Content
Encryption Keys' <draft-ietf-smime-rcek-04.txt> as a Proposed
Standard.  This document is the product of the S/MIME Mail Security
Working Group.  The IESG contact persons are Jeffrey Schiller and
Marcus Leech.

 
Technical Summary
 
  SMIME's Cryptographic Message Syntax (CMS) provides a way to use
  public key cryptography to encrypt a symmetric key which in turn is
  used to encrypt the content of the message.

  There are applications where two parties may need to exchange
  multiple messages and wish to avoid the overhead of the public key
  operation (public key cryptography is much more computationally
  expensive then symmetric algorithms).

  This document defines a secure way of labeling the symmetric key
  (called the Content Encryption Key or CEK) in a message such that it
  may be used as a Key Encrypting Key (KEK) for a later message.

  This technique is not advisable for just any application and the
  document explains where it makes sense and where it doesn't.

Working Group Summary

  The S/MIME Working Group came to consensus on this document.

Protocol Quality

  This protocol was reviewed for the IESG by Jeffrey I. Schiller.