RFC 4880: OpenPGP Message Format

This document is maintained in order to publish all necessary information needed to develop interoperable applications based on the OpenPGP format. It is not…

Read RFC 4880 on the RFC Editor

Outgoing relationships (14 related RFCs)

Obsoletes, Informative reference — RFC 2440: OpenPGP Message Format
Obsoletes, Informative reference — RFC 1991: PGP Message Exchange Formats
Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 3629: UTF-8, a transformation format of ISO 10646
Normative reference — RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
Normative reference — RFC 4086: Randomness Requirements for Security
Normative reference — RFC 2434: Guidelines for Writing an IANA Considerations Section in RFCs
Normative reference — RFC 2822: Internet Message Format
Normative reference — RFC 3447: Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1
Normative reference — RFC 1951: DEFLATE Compressed Data Format Specification version 1.3
Normative reference — RFC 3156: MIME Security with OpenPGP
Normative reference — RFC 1950: ZLIB Compressed Data Format Specification version 3.3
Normative reference — RFC 2144: The CAST-128 Encryption Algorithm
Informative reference — RFC 1423: Privacy Enhancement for Internet Electronic Mail: Part III: Algorithms, Modes, and Identifiers

Incoming relationships (27 related RFCs)

Updated by, Normatively referenced by — RFC 5581: The Camellia Cipher in OpenPGP
Obsoleted by, Informatively referenced by — RFC 9580: OpenPGP
Normatively referenced by — RFC 6189: ZRTP: Media Path Key Agreement for Unicast Secure RTP
Normatively referenced by — RFC 6091: Using OpenPGP Keys for Transport Layer Security (TLS) Authentication
Normatively referenced by — RFC 7929: DNS-Based Authentication of Named Entities (DANE) Bindings for OpenPGP
Normatively referenced by — RFC 5848: Signed Syslog Messages
Informatively referenced by — RFC 6125: Representation and Verification of Domain-Based Application Service Identity within Internet Public Key Infrastructure Using X.509 (PKIX) Certificates in the Context of Transport Layer Security (TLS)
Informatively referenced by — RFC 8085: UDP Usage Guidelines
Informatively referenced by — RFC 5598: Internet Mail Architecture
Informatively referenced by — RFC 6350: vCard Format Specification
Informatively referenced by — RFC 5405: Unicast UDP Usage Guidelines for Application Designers
Informatively referenced by — RFC 7468: Textual Encodings of PKIX, PKCS, and CMS Structures
Informatively referenced by — RFC 6409: Message Submission for Mail
Informatively referenced by — RFC 5929: Channel Bindings for TLS
Informatively referenced by — RFC 5703: Sieve Email Filtering: MIME Part Tests, Iteration, Extraction, Replacement, and Enclosure
Informatively referenced by — RFC 7070: An Architecture for Reputation Reporting
Informatively referenced by — RFC 5585: DomainKeys Identified Mail (DKIM) Service Overview
Informatively referenced by — RFC 8188: Encrypted Content-Encoding for HTTP
Informatively referenced by — RFC 8689: SMTP Require TLS Option
Informatively referenced by — RFC 6476: Using Message Authentication Code (MAC) Encryption in the Cryptographic Message Syntax (CMS)
Informatively referenced by — RFC 7958: DNSSEC Trust Anchor Publication for the Root Zone
Informatively referenced by — RFC 5854: The Metalink Download Description Format
Informatively referenced by — RFC 5981: Authorization for NSIS Signaling Layer Protocols
Informatively referenced by — RFC 7681: Email Exchange of Secondary School Transcripts
Informatively referenced by — RFC 8315: Cancel-Locks in Netnews Articles
Informatively referenced by — RFC 8904: DNS Whitelist (DNSWL) Email Authentication Method Extension
Informatively referenced by — RFC 9361: ICANN Trademark Clearinghouse (TMCH) Functional Specifications