<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-openpgp-rfc4880bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-openpgp-rfc4880bis-10">
   <front>
      <title>OpenPGP Message Format</title>
      <author initials="W." surname="Koch" fullname="Werner Koch">
         <organization>GnuPG e.V.</organization>
      </author>
      <author initials="B. M." surname="carlson" fullname="brian m. carlson">
         </author>
      <author initials="R. H." surname="Tse" fullname="Ronald Henry Tse">
         <organization>Ribose</organization>
      </author>
      <author initials="D." surname="Atkins" fullname="Derek Atkins">
         </author>
      <author initials="D. K." surname="Gillmor" fullname="Daniel Kahn Gillmor">
         </author>
      <date month="August" day="31" year="2020" />
      <abstract>
	 <t>   { Work in progress to update the OpenPGP specification from RFC4880 }

   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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-openpgp-rfc4880bis-10" />
   
</reference>
