--- Begin Message ---
On 22/03/2020 18:29, Guy Harris via tcpdump-workers wrote:
> 5) Treat rpcap as "remote procedure call for libpcap" and put it under the
> the-tcpdump-group team, and put pcap under the pcapng team as per the same
> reason as 4).
Ok.
--- End Message ---
--- Begin Message ---
On Mar 21, 2020, at 2:38 PM, Guy Harris via tcpdump-workers
wrote:
> On Mar 21, 2020, at 2:14 PM, Guy Harris via tcpdump-workers
> wrote:
>
>> The options I see are:
>
> 4) add a new team for rpcap, as it's a protocol rather than a file format,
> and thus only indirect
--- Begin Message ---
On Mar 22, 2020, at 9:49 AM, Michael Tuexen
wrote:
> I would support this. However, last time I tried this, I was not successful.
> There were not very interested in defining a file format...
They've done so in the past:
https://tools.ietf.org/html/rfc1761 (and
h
--- Begin Message ---
> On 21. Mar 2020, at 23:10, Michael Richardson wrote:
>
>
> Guy Harris via tcpdump-workers wrote:
>> Currently, on GitHub, there's a "pcapng" team:
>> https://github.com/pcapng
>
>> with one repository containing the pcapng specification, and a
>> "the-tcpdump-group" te
