RFC 2312: S/MIME Version 2 Certificate Handling
In plain English — editorial summary, not part of the RFC
This memo describes the mechanisms S/MIME uses to create and validate keys using certificates. This memo provides information for the Internet community. It does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2312
- Published
- March 1998
- Authors
- S. Dusse; P. Hoffman; B. Ramsdell; J. Weinstein
- Status
- HISTORIC
- Stream
- Legacy
- Area
- —
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2311S/MIME Version 2 Message SpecificationCurrent
March 1998
- RFC 2632S/MIME Version 3 Certificate HandlingObsoleted
June 1999
- RFC 2633S/MIME Version 3 Message SpecificationObsoleted
June 1999
- RFC 5750Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate HandlingObsoleted
January 2010
- RFC 5751Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message SpecificationObsoleted
January 2010
- RFC 2278IANA Charset Registration ProceduresObsoleted
January 1998
- RFC 2422Toll Quality Voice - 32 kbit/s ADPCM MIME Sub-type RegistrationObsoleted
September 1998
- RFC 2424Content Duration MIME Header DefinitionObsoleted
September 1998
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?