RFC 2015: MIME Security with Pretty Good Privacy (PGP)
In plain English — editorial summary, not part of the RFC
This document describes how Pretty Good Privacy (PGP) can be used to provide privacy and authentication using the Multipurpose Internet Mail Extensions (MIME) security content types described in RFC1847. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2015
- Published
- October 1996
- Authors
- M. Elkins
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 8
- Also known as
- —
- Updated by:
- RFC 3156
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 2139RADIUS AccountingObsoleted
April 1997
- RFC 2898PKCS #5: Password-Based Cryptography Specification Version 2.0Obsoleted
September 2000
- RFC 2059RADIUS AccountingObsoleted
January 1997
- RFC 2065Domain Name System Security ExtensionsObsoleted
January 1997
- RFC 2084Considerations for Web Transaction SecurityCurrent
January 1997
- RFC 2440OpenPGP Message FormatObsoleted
November 1998
- RFC 2459Internet X.509 Public Key Infrastructure Certificate and CRL ProfileObsoleted
January 1999
- RFC 2527Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices FrameworkObsoleted
March 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?