Re: [tcpdump-workers] [Wireshark-dev] New RFCs for 1) pcap file format and 2) rpcapd protocol?

[Michael Tuexen via tcpdump-workers]

--- 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] [OPSAWG] I-D Action: draft-ietf-opsawg-pcapng-00.txt

[Michael Tuexen via tcpdump-workers]

--- Begin Message ---
> On 25. Jan 2023, at 21:33, Carsten Bormann  wrote:
> 
> On 25. Jan 2023, at 17:42, Michael Richardson  wrote:
>> 
>> I am not sure that pcap*NG* is so incredibly established that we can't change
>> it.  I just hate "Next Generation" for anything, particularly when time 
>> moves on.
>> What about if we kept N and G, but changed what they meant?
> 
> (SenML started as an XML vocabulary, but now is mostly JSON and CBOR — so we 
> turned the “ML” into “Measurement Lists”.
> Which is somewhat bizarre, but keeps the acronym.
> For retronyming PCAPNG, what is central to PCAPNG that would explain the P, 
> N, and G?)
pcap, now generalized?

Best regards
Michael
> 
> Grüße, Carsten
> 
> ___
> OPSAWG mailing list
> ops...@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg

--- End Message ---
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers