[smime] RFC 5990 on Use of the RSA-KEM Key Transport Algorithm in the Cryptographic Message Syntax (CMS)

rfc-editor@rfc-editor.org Thu, 23 September 2010 15:30 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: smime@core3.amsl.com
Delivered-To: smime@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8460F3A6AD9; Thu, 23 Sep 2010 08:30:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.055
X-Spam-Level:
X-Spam-Status: No, score=-102.055 tagged_above=-999 required=5 tests=[AWL=-0.055, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VkON05E278JH; Thu, 23 Sep 2010 08:30:24 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 8E6FB3A6AE5; Thu, 23 Sep 2010 08:30:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 72076E06A6; Thu, 23 Sep 2010 08:30:54 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100923153054.72076E06A6@rfc-editor.org>
Date: Thu, 23 Sep 2010 08:30:54 -0700
Cc: smime@ietf.org, rfc-editor@rfc-editor.org
Subject: [smime] RFC 5990 on Use of the RSA-KEM Key Transport Algorithm in the Cryptographic Message Syntax (CMS)
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Sep 2010 15:30:28 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5990

        Title:      Use of the RSA-KEM Key 
                    Transport Algorithm in the Cryptographic Message 
                    Syntax (CMS) 
        Author:     J. Randall, B. Kaliski,
                    J. Brainard, S. Turner
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2010
        Mailbox:    jdrandall@comcast.net, 
                    kaliski_burt@emc.com, 
                    jbrainard@rsa.com,  turners@ieca.com
        Pages:      27
        Characters: 52579
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-smime-cms-rsa-kem-13.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5990.txt

The RSA-KEM Key Transport Algorithm is a one-pass (store-and-forward)
mechanism for transporting keying data to a recipient using the recipient's
RSA public key.  ("KEM" stands for "key encapsulation mechanism".)  This 
document specifies the conventions for using the RSA-KEM Key Transport
Algorithm with the Cryptographic Message Syntax (CMS).  The ASN.1 syntax is
aligned with an expected forthcoming change to American National Standard 
(ANS) X9.44.

This document is a product of the S/MIME Mail Security Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC