Re: [tcpdump-workers] [Wireshark-dev] New RFCs for 1) pcap file format and 2) rpcapd protocol?
--- 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" team: > >> https://github.com/the-tcpdump-group >> with repositories for libpcap, tcpdump, and the tcpdump.org Web site. > >> It makes sense to me to keep those specifications on a site such as >> GitHub; GitHub comes to mind first because that's where pcapng >> currently is. > >> 1) add them as repositories to the pcapng team; > >> 1) has the slight disadvantage that the name for the team suggests it's >> for pcapng only; it appears that teams can be renamed: > > ... > >> Were we to rename it, I don't know what would be a good new name. > > I'm good with pcapng, because I also have no other suggestion. > I would like to restart the opsawg work on an IETF specification for this. I would support this. However, last time I tried this, I was not successful. There were not very interested in defining a file format... Maybe things have changed, but I don't know. Best regards Michael > > -- > Michael Richardson , Sandelman Software Works > -= IPv6 IoT consulting =- > > > > ___ > Sent via:Wireshark-dev mailing list > 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 --- End Message --- ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] [Wireshark-dev] New RFCs for 1) pcap file format and 2) rpcapd protocol?
--- 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 https://tools.ietf.org/html/rfc3827) and, for non-capture-file formats: https://tools.ietf.org/html/rfc8536#section-3--- End Message --- ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] New RFCs for 1) pcap file format and 2) rpcapd protocol?
--- 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 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).--- End Message --- ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
Re: [tcpdump-workers] New RFCs for 1) pcap file format and 2) rpcapd protocol?
--- 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 --- ___ tcpdump-workers mailing list tcpdump-workers@lists.tcpdump.org https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
