--- 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,
--- Begin Message ---
On Mar 20, 2020, at 11:14 PM, Nick Kelsey wrote:
> I figure there will be interest in this protocol as we start to see ATSC 3.0
> test broadcasts. Our ATSC 3.0 hardware can output pcap data over HTTP in real
> time so ALP can be captured to file with a simple curl/wget
--- Begin Message ---
On 3/20/2020 9:42 PM, Guy Harris wrote:
> On Mar 20, 2020, at 2:39 PM, Nick Kelsey via tcpdump-workers
wrote:
>
>> Pull request created (#919):
>>
>> https://github.com/the-tcpdump-group/libpcap/pull/919
>
> I've added a proposed description as a comment to the pull
