RFC 2633: S/MIME Version 3 Message Specification

This document describes a protocol for adding cryptographic signature and encryption services to MIME data. [STANDARDS-TRACK]

Read RFC 2633 on the RFC Editor

Incoming relationships (24 related RFCs)

Obsoleted by — RFC 3851: Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification
Normatively referenced by — RFC 3261: SIP: Session Initiation Protocol
Normatively referenced by — RFC 7030: Enrollment over Secure Transport
Normatively referenced by — RFC 3560: Use of the RSAES-OAEP Key Transport Algorithm in Cryptographic Message Syntax (CMS)
Informatively referenced by — RFC 4086: Randomness Requirements for Security
Informatively referenced by — RFC 5652: Cryptographic Message Syntax (CMS)
Informatively referenced by — RFC 2821: Simple Mail Transfer Protocol
Informatively referenced by — RFC 5751: Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification
Informatively referenced by — RFC 3819: Advice for Internet Subnetwork Designers
Informatively referenced by — RFC 8152: CBOR Object Signing and Encryption (COSE)
Informatively referenced by — RFC 2985: PKCS #9: Selected Object Classes and Attribute Types Version 2.0
Informatively referenced by — RFC 9052: CBOR Object Signing and Encryption (COSE): Structures and Process
Informatively referenced by — RFC 3565: Use of the Advanced Encryption Standard (AES) Encryption Algorithm in Cryptographic Message Syntax (CMS)
Informatively referenced by — RFC 3862: Common Presence and Instant Messaging (CPIM): Message Format
Informatively referenced by — RFC 2785: Methods for Avoiding the "Small-Subgroup" Attacks on the Diffie-Hellman Key Agreement Method for S/MIME
Informatively referenced by — RFC 3369: Cryptographic Message Syntax (CMS)
Informatively referenced by — RFC 2797: Certificate Management Messages over CMS
Informatively referenced by — RFC 5750: Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate Handling
Informatively referenced by — RFC 3183: Domain Security Services using S/MIME
Informatively referenced by — RFC 2876: Use of the KEA and SKIPJACK Algorithms in CMS
Informatively referenced by — RFC 3185: Reuse of CMS Content Encryption Keys
Informatively referenced by — RFC 6664: S/MIME Capabilities for Public Key Definitions
Informatively referenced by — RFC 7107: Object Identifier Registry for the S/MIME Mail Security Working Group
Informatively referenced by — RFC 3058: Use of the IDEA Encryption Algorithm in CMS