metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 4880: OpenPGP Message Format

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9580.

Current document in this lineage: RFC 9580 — OpenPGP

In plain English — editorial summary, not part of the RFC

This document is maintained in order to publish all necessary information needed to develop interoperable applications based on the OpenPGP format. It is not a step-by-step cookbook for writing an application. It describes only the format and methods needed to read, check, generate, and write conforming packets crossing any network. It does not deal with storage and implementation questions. It does, however, discuss implementation issues necessary to avoid security flaws. OpenPGP software uses a combination of strong public-key and symmetric cryptography to provide security services for electronic communications and data storage. These services include confidentiality, key management, authentication, and digital signatures. This document specifies the message formats used in OpenPGP. [STANDARDS-TRACK]

Document record

Document ID
RFC4880
Published
November 2007
Authors
J. Callas; L. Donnerhacke; H. Finney; D. Shaw; R. Thayer
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
90
Also known as
—
Obsoletes:
RFC 1991, RFC 2440
Obsoleted by:
RFC 9580
Updated by:
RFC 5581

Topics

Standards lineage

This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.

  1. RFC 1991 (1996)
  2. RFC 2440 (1998)
  3. RFC 4880 (2007)
  4. RFC 5581 (2009)
  5. RFC 6637 (2012)
  6. RFC 9580 (2024) ✓

Read the full history of OpenPGP →

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/4880-openpgp-message-format