OpenPGP Message Format
RFC 4880, “OpenPGP Message Format”, is a Proposed Standard document published in November 2007 by J. Callas, L. Donnerhacke, H. Finney, D. Shaw, R. Thayer. It obsoletes RFC 1991, RFC 2440. It has since been updated by RFC 5581. It has been obsoleted by RFC 9580 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 4880 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4879 Clarification of the Third Party Disclosure Procedure in RFC 3979
- RFC 4881 Low-Latency Handoffs in Mobile IPv4
- RFC 4878 Definitions and Managed Objects for Operations, Administration, and Maintenance Functions on Ethernet-Like Interfaces
- RFC 4882 IP Address Location Privacy and Mobile IPv6: Problem Statement
- RFC 4877 Mobile IPv6 Operation with IKEv2 and the Revised IPsec Architecture
- RFC 4883 Benchmarking Terminology for Resource Reservation Capable Routers
- RFC 4876 A Configuration Profile Schema for Lightweight Directory Access Protocol -Based Agents
- RFC 4884 Extended ICMP to Support Multi-Part Messages