Use of the RSAES-OAEP Key Transport Algorithm in Cryptographic Message Syntax
RFC 3560, “Use of the RSAES-OAEP Key Transport Algorithm in Cryptographic Message Syntax”, is a Proposed Standard document published in July 2003 by R. Housley. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 3560 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3559 Multicast Address Allocation MIB
- RFC 3561 Ad hoc On-Demand Distance Vector Routing
- RFC 3558 RTP Payload Format for Enhanced Variable Rate Codecs and Selectable Mode Vocoders
- RFC 3562 Key Management Considerations for the TCP MD5 Signature Option
- RFC 3557 RTP Payload Format for European Telecommunications Standards Institute European Standard ES 201 108 Distributed Speech Recognition Encoding
- RFC 3563 Cooperative Agreement Between the ISOC/IETF and ISO/IEC Joint Technical Committee 1/Sub Committee 6 on IS-IS Routing Protocol Development
- RFC 3556 Session Description Protocol Bandwidth Modifiers for RTP Control Protocol Bandwidth
- RFC 3564 Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering