RFC 5990: Use of the RSA-KEM Key Transport Algorithm in the Cryptographic Message Syntax (CMS)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9690.
Current version: RFC 9690 — Use of the RSA-KEM Algorithm in the Cryptographic Message Syntax (CMS)
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC5990
- Published
- September 2010
- Authors
- J. Randall; B. Kaliski; J. Brainard; S. Turner
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 27
- Also known as
- —
- Obsoleted by:
- RFC 9690
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5996Internet Key Exchange Protocol Version 2 (IKEv2)Obsoleted
September 2010
- RFC 5997Use of Status-Server Packets in the Remote Authentication Dial In User Service (RADIUS) ProtocolCurrent
August 2010
- RFC 5998An Extension for EAP-Only Authentication in IKEv2Current
September 2010
- RFC 6012Datagram Transport Layer Security (DTLS) Transport Mapping for SyslogUpdated
October 2010
- RFC 6024Trust Anchor Management RequirementsCurrent
October 2010
- RFC 6025ASN.1 TranslationCurrent
October 2010
- RFC 6027IPsec Cluster Problem StatementCurrent
October 2010
- RFC 6030Portable Symmetric Key Container (PSKC)Current
October 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?