CurrentPROPOSED STANDARDIETF stream

RFC 3560: Use of the RSAES-OAEP Key Transport Algorithm in Cryptographic Message Syntax (CMS)

In plain English — editorial summary, not part of the RFC

This document describes the conventions for using the RSAES-OAEP key transport algorithm with the Cryptographic Message Syntax (CMS). The CMS specifies the enveloped-data content type, which consists of an encrypted content and encrypted content-encryption keys for one or more recipients. The RSAES-OAEP key transport algorithm can be used to encrypt content-encryption keys for intended recipients. [STANDARDS-TRACK]

Document record

Document ID
RFC3560
Published
July 2003
Authors
R. Housley
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
18
Also known as

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/3560-use-of-the-rsaes-oaep-key-transport-algorithm-in-cryptographic-message-syntax-cm