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

[Michael Richardson <mcr () sandelman ca>]

Michael Tuexen via tcpdump-workers <tcpdump-workers () lists tcpdump org> wrote:
    >> Guy Harris via tcpdump-workers <tcpdump-workers () lists tcpdump org> 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.

I know that you worked hard, and it didn't happen.
It is on my agenda to make this happen, and I'll hope that I can depend upon
your help.

With IETF107 going virtual, I will see if opsawg has time consider the
document again. I will look at reposting it today.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr () sandelman ca  http://www.sandelman.ca/        |   ruby on rails    [

Attachment: signature.asc
Description:

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe