MIME Security with OpenPGP
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 15
- Abstract
- 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]
- Publication Date
- 2001-08-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC3156- Link
- https://doi.org/10.17487/RFC3156
- Author(s)
- Michael ElkinsDave Del TortoRaph LevienThomas Roessler
- Keyword(s)
- MIME-PGP, MIME, PGP, Authentication, Encryption
Latest version of IETF RFC 3156
Document Versions — IETF RFC 3156
-
▶ IETF RFC 3156 (2001-08-01)THIS DOC [ACTIVE] [LATEST VERSION]
Bibliographic Reference(s)
- IETF RFC 1847 [Active*]
- IETF RFC 1848 [Active*]
- IETF RFC 1991 [Superseded*]
- IETF RFC 2015 [Active*]
- IETF RFC 2046 [Active, Amended*]
- IETF RFC 2440 [Superseded*]
- IETF RFC 2480 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3156.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 3156, MIME Security with OpenPGP. Available at https://doi.org/10.17487/RFC3156
Snippet:
IETF RFC 3156, MIME Security with OpenPGP. Available at https://doi.org/10.17487/RFC3156
HTML (ISO 690 compliant)
Preview:
IETF RFC 3156, MIME Security with OpenPGP. Available at https://doi.org/10.17487/RFC3156
Snippet:
<span class="citation"><cite>IETF RFC 3156</cite>, MIME Security with OpenPGP. Available at <a href="https://doi.org/10.17487/RFC3156" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3156</a></span>
SMPTE's HTML Pub
Preview:
Snippet:
<li> <cite id="bib-rfc3156">IETF RFC 3156</cite>, MIME Security with OpenPGP <span class="doi">10.17487/RFC3156</span> </li>
Referenced By
- IETF RFC 3335 [Active*]
- IETF RFC 3676 [Active*]
- IETF RFC 4086 [Active*]
- IETF RFC 4227 [Active*]
- IETF RFC 4880 [Superseded*]
- IETF RFC 4952 [Superseded*]
- IETF RFC 6530 [Active*]
- IETF RFC 6532 [Active*]