RFC 3156: MIME Security with OpenPGP
In plain English — editorial summary, not part of the RFC
This document describes how the OpenPGP Message Format can be used to provide privacy and authentication using the Multipurpose Internet Mail Extensions (MIME) security content types described in RFC 1847. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3156
- Published
- August 2001
- Authors
- M. Elkins; D. Del Torto; R. Levien; T. Roessler
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 15
- Also known as
- —
- Updates:
- RFC 2015
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2440OpenPGP Message FormatObsoleted
November 1998
- RFC 3195Reliable Delivery for syslogCurrent
November 2001
- RFC 3647Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices FrameworkCurrent
November 2003
- RFC 2634Enhanced Security Services for S/MIMEUpdated
June 1999
- RFC 2527Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices FrameworkObsoleted
March 1999
- 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 2459Internet X.509 Public Key Infrastructure Certificate and CRL ProfileObsoleted
January 1999
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?