On Mar 26, 2020, at 7:10 PM, Guy Harris via tcpdump-workers <tcpdump-work...@lists.tcpdump.org> wrote:
> (Note that its purpose is to document the *existing* format, rather than be a > source of proposed changes.) ...proposed changes to the format. I am, however, planning on proposing a mechanism for vendor-specific "custom" link-layer types, inspired by the pcapng "custom" block types and option types, for use in both pcap and pcapng. That'll be in a separate message. As with pcapng block types and options, anything of *general* use that a vendor would like multiple programs to be able to handle should probably be proposed as a part of the standard, with a register link-layer type/block number/option number. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
