<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.richardson-opsawg-pcapng-extras" target="https://datatracker.ietf.org/doc/html/draft-richardson-opsawg-pcapng-extras-01">
   <front>
      <title>Additional block types for PCAP Next Generation (pcapng) Capture File Format</title>
      <author initials="M." surname="Tüxen" fullname="Michael Tüxen">
         <organization>Muenster University of Applied Sciences</organization>
      </author>
      <author initials="F." surname="Risso" fullname="Fulvio Risso">
         <organization>Politecnico di Torino</organization>
      </author>
      <author initials="J." surname="Bongertz" fullname="Jasper Bongertz">
         <organization>Airbus Defence and Space CyberSecurity</organization>
      </author>
      <author initials="G." surname="Combs" fullname="Gerald Combs">
         <organization>Wireshark Foundation</organization>
      </author>
      <author initials="G." surname="Harris" fullname="Guy Harris">
         </author>
      <author initials="E." surname="Chaudron" fullname="Eelco Chaudron">
         <organization>Red Hat</organization>
      </author>
      <author initials="M." surname="Richardson" fullname="Michael Richardson">
         <organization>Sandelman Software Works</organization>
      </author>
      <date month="July" day="29" year="2022" />
      <abstract>
	 <t>   This document contains a number of extensions to the PCAPng file
   format which are outside of the IETF networking mandate.

Discussion Venues

   This note is to be removed before publishing as an RFC.

   Discussion of this document takes place on the OPSAWG Working Group
   mailing list (opsawg@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/browse/opsawg/.

   Source for this draft and an issue tracker can be found at
   https://github.com/pcapng/pcapng.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-richardson-opsawg-pcapng-extras-01" />
   
</reference>
