Guy Harris via tcpdump-workers <[email protected]> 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.
--
Michael Richardson <[email protected]>, Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
