RFC 9580 on OpenPGP

A new Request for Comments is now available in online RFC libraries.

        RFC 9580

        Title:      OpenPGP 
        Author:     P. Wouters, Ed.,
                    D. Huigens,
                    J. Winter,
                    Y. Niibe
        Status:     Standards Track
        Stream:     IETF
        Date:       July 2024
        Mailbox:    paul.wouters@aiven.io,
                    d.huigens@protonmail.com,
                    justus@sequoia-pgp.org,
                    gniibe@fsij.org
        Pages:      166
        Obsoletes:  RFC 4880, RFC 5581, RFC 6637

        I-D Tag:    draft-ietf-openpgp-crypto-refresh-13.txt

        URL:        https://www.rfc-editor.org/info/rfc9580

        DOI:        10.17487/RFC9580

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").

This document is a product of the Open Specification for Pretty Good Privacy Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC