%% You should probably cite draft-koch-librepgp instead of this I-D.
@techreport{koch-openpgp-2015-rfc4880bis-00,
    number =    {draft-koch-openpgp-2015-rfc4880bis-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-koch-openpgp-2015-rfc4880bis/00/},
    author =    {Werner Koch and brian m. carlson and Ronald Henry Tse and Derek Atkins and Daniel Kahn Gillmor},
    title =     {{OpenPGP Message Format}},
    pagetotal = 135,
    year =      2022,
    month =     sep,
    day =       7,
    abstract =  {\{ Work in progress to update the OpenPGP specification from RFC4880 \} \{ This version is on the Git head with rfc4880bis-10 before the great refactoring. That refactoring, dubbed crypto-refresh, basically started from scratch with lots of re-formatting and switching to a Gitlab based approach with merge requests mainly prepared in advance by one of the chairs. This was done despite that -10 was basically ready for last call after a long iterative process adding feature by feature with rough consent from the WG. Due to the IETF submission system the draft has a new name but nevertheless is the direct successor of draft-ietf-openpgp- rfc4880bis-10 \} 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.},
}