--- Begin Message ---
On Apr 1, 2020, at 11:51 AM, Michael Richardson wrote:
> 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
--- Begin Message ---
On Mar 22, 2020, at 11:40 AM, Francois-Xavier Le Bail
wrote:
> 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
--- Begin Message ---
On Mar 26, 2020, at 7:10 PM, Guy Harris via tcpdump-workers
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
--- Begin Message ---
On Mar 22, 2020, at 10:29 AM, Guy Harris via tcpdump-workers
wrote:
> 5) ... and put pcap under the pcapng team as per the same reason as 4).
Done. It's pointed to by
https://github.com/pcapng/pcapng
and the XML source is at
--- 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
--- Begin Message ---
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 indirectly tied to pcap/pcapng, and putting the pcap format in the
pcapng team because
--- Begin Message ---
On Mar 21, 2020, at 2:31 PM, Mario Rugiero via tcpdump-workers
wrote:
> El sáb., 21 mar. 2020 18:15, Guy Harris via tcpdump-workers
> escribió:
>
>> 1) has the slight disadvantage that the name for the team suggests it's
>> for pcapng only; it appears that teams can be
--- Begin Message ---
El sáb., 21 mar. 2020 18:15, Guy Harris via tcpdump-workers <
tcpdump-workers@lists.tcpdump.org> escribió:
> 1) has the slight disadvantage that the name for the team suggests it's
> for pcapng only; it appears that teams can be renamed:
>
>
>
--- Begin Message ---
On 21/03/2020 22:14, Guy Harris via tcpdump-workers wrote:
> 1) has the slight disadvantage that the name for the team suggests it's for
> pcapng only; it appears that teams can be renamed:
>
>
>
--- Begin Message ---
There should probably be RFC-style specifications for 1) the pcap file format
and 2) the rpcapd protocol used for remote capturing.
Currently, on GitHub, there's a "pcapng" team:
https://github.com/pcapng
with one repository containing the pcapng specification,
11 matches
Mail list logo
