RFC 2634: Enhanced Security Services for S/MIME
In plain English — editorial summary, not part of the RFC
This document describes four optional security service extensions for S/MIME. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2634
- Published
- June 1999
- Authors
- P. Hoffman
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 58
- Also known as
- —
- Updated by:
- RFC 5035
Topics
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.
- RFC 3850Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate HandlingObsoleted
July 2004
- RFC 3851Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message SpecificationObsoleted
July 2004
- RFC 3854Securing X.400 Content with Secure/Multipurpose Internet Mail Extensions (S/MIME)Current
July 2004
- RFC 2633S/MIME Version 3 Message SpecificationObsoleted
June 1999
- RFC 2632S/MIME Version 3 Certificate HandlingObsoleted
June 1999
- RFC 3156MIME Security with OpenPGPCurrent
August 2001
- RFC 3855Transporting Secure/Multipurpose Internet Mail Extensions (S/MIME) Objects in X.400Current
July 2004
- RFC 4490Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with Cryptographic Message Syntax (CMS)Current
May 2006
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?