metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 2632: S/MIME Version 3 Certificate Handling

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

Current document in this lineage: RFC 8550 — Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 4.0 Certificate Handling

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

S/MIME (Secure/Multipurpose Internet Mail Extensions), provides a method to send and receive secure MIME messages. Before using a public key to provide security services, the S/MIME agent MUST certify that the public key is valid. S/MIME agents MUST use PKIX certificates to validate public keys as described in the Internet X.509 Public Key Infrastructure (PKIX) Certificate and CRL Profile. [STANDARDS-TRACK]

Document record

Document ID
RFC2632
Published
June 1999
Authors
B. Ramsdell
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
13
Also known as
—
Obsoleted by:
RFC 3850

Topics

Standards lineage

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

  1. RFC 2632 (1999)
  2. RFC 3850 (2004)
  3. RFC 5750 (2010)
  4. RFC 8550 (2019) ✓

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

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/2632-s-mime-version-3-certificate-handling