RFC 9580: OpenPGP
In plain English — editorial summary, not part of the RFC
This document specifies the message formats used in OpenPGP. OpenPGP provides encryption with public key or symmetric cryptographic algorithms, digital signatures, compression, and key management. 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. This document obsoletes RFCs 4880 ("OpenPGP Message Format"), 5581 ("The Camellia Cipher in OpenPGP"), and 6637 ("Elliptic Curve Cryptography (ECC) in OpenPGP").
Document record
- Document ID
- RFC9580
- Published
- July 2024
- Authors
- P. Wouters; D. Huigens; J. Winter; Y. Niibe
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 166
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9980Post-Quantum Cryptography in OpenPGPCurrent
June 2026
- RFC 3547The Group Domain of InterpretationObsoleted
July 2003
- RFC 2440OpenPGP Message FormatObsoleted
November 1998
- RFC 4051Additional XML Security Uniform Resource Identifiers (URIs)Obsoleted
April 2005
- RFC 9594Key Provisioning for Group Communication Using Authentication and Authorization for Constrained Environments (ACE)Current
September 2024
- RFC 9464Internet Key Exchange Protocol Version 2 (IKEv2) Configuration for Encrypted DNSCurrent
November 2023
- RFC 9787Guidance on End-to-End Email SecurityCurrent
August 2025
- RFC 9788Header Protection for Cryptographically Protected EmailCurrent
August 2025
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?