metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 5751: Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message Specification

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8551.

Current document in this lineage: RFC 8551 — Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Message Specification

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

This document defines Secure/Multipurpose Internet Mail Extensions (S/MIME) version 3.2. S/MIME provides a consistent way to send and receive secure MIME data. Digital signatures provide authentication, message integrity, and non-repudiation with proof of origin. Encryption provides data confidentiality. Compression can be used to reduce data size. This document obsoletes RFC 3851. [STANDARDS-TRACK]

Document record

Document ID
RFC5751
Published
January 2010
Authors
B. Ramsdell; S. Turner
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
45
Also known as
—
Obsoletes:
RFC 3851
Obsoleted by:
RFC 8551

Topics

Standards lineage

This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.

  1. RFC 2633 (1999)
  2. RFC 3851 (2004)
  3. RFC 5751 (2010)
  4. RFC 8551 (2019) ✓

Read the full history of Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Message Specification →

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.

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/5751-secure-multipurpose-internet-mail-extensions-s-mime-version-3-2-message-specific