On Mar 21, 2020, at 2:38 PM, Guy Harris via tcpdump-workers <tcpdump-workers@xxxxxxxxxxxxxxxxx> wrote:
> On Mar 21, 2020, at 2:14 PM, Guy Harris via tcpdump-workers <tcpdump-workers@xxxxxxxxxxxxxxxxx> 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 indirectly tied to pcap/pcapng, and putting the pcap format in the pcapng team because you can't have a pcap*ng* without having had a pcap in the first place.
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).
