%% You should probably cite draft-ietf-openpgp-crypto-refresh-13 instead of this revision.
@techreport{ietf-openpgp-crypto-refresh-05,
    number =    {draft-ietf-openpgp-crypto-refresh-05},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-openpgp-crypto-refresh/05/},
    author =    {Werner Koch and Paul Wouters},
    title =     {{OpenPGP Message Format}},
    pagetotal = 151,
    year =      2022,
    month =     mar,
    day =       7,
    abstract =  {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: RFC 4880 (OpenPGP), RFC 5581 (Camellia in OpenPGP) and RFC 6637 (Elliptic Curves in OpenPGP).},
}