Guy Harris via tcpdump-workers wrote:
> It's complex, too - and I don't know whether anybody's done a CMake
> version of that.
> Would it make more sense to put the rpcap I-D into either 1) a separate
> team and repository or 2) another repository in the pcapng group, so
>
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.
> This would require the rules in the pcapng
ats, these lists are
> probably better places for discussion than having two pull requests and
> discussing them in comments there.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works
t 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!
tion.
I would like to restart the opsawg work on an IETF specification for this.
--
Michael Richardson , Sandelman Software Works
-= IPv6 IoT consulting =-
signature.asc
Description: PGP signature
___
Sent via:Wireshark-
ppen to have the secret available before
> seeing any packets that require the secret *could* write it directly.
Agreed.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
]
k. Consumers
> can read and decrypt in one pass. Disadvantage: requires producers to
> post-process (rewrite) the capture file to insert secrets.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works
