> -----Original Message-----
> From: ethereal-dev-admin@xxxxxxxxxxxx
> [mailto:ethereal-dev-admin@xxxxxxxxxxxx]On Behalf Of Guy Harris
> Sent: Tuesday, October 24, 2000 00:47
> To: Loris Degioanni
> Cc: Mark Atwood; ethereal-dev@xxxxxxxxxxxx; ethereal-users@xxxxxxxxxxxx
> Subject: Re: R: [Ethereal-dev] Remote online packet capture?
>
>
> > At the moment we have a very basic version for win32 that we
> > have tested with windump and Analyzer. In the future we plan to add
> > features like autentication, cryptography, data compression and remote
> > statistical analysis and then release the code in the winpcap source
> > distribution. Has anyone comments or suggestion on this approach?
>
> It sounds reasonable (at least once there's authentication); you should
> probably send the client code (the "pcap-xxx.c" file) to tcpdump.org for
> inclusion in standard libpcap.
>
> Does the server use libpcap for capturing? If so, sending server code
> to tcpdump.org would probably be a good idea as well, so that a UNIX
> port can be distributed by tcpdump.org.
We agree, although I guess some changes must be done in order to launch the
daemon on both Windows and Unix platform.
> Should an RFC be written for the protocol? (Some protocol spec should
> probably be written up.) I don't know what the process is for getting
> an RFC published - I don't know if it'd first be done as an
> Internet-Draft, or not.
Yes. I-D first, then (maybe) RFC.
In any case:
- we have a prototype but we do not think to have anything reasonable before
2-3 months
- we're working in our spare time, so timing is not certain...
> You might also want to mention this on tcpdump-workers.
I suggest to proceed in that way:
- we start working on it ant we'll produce a draft about this problem
- we submit this to the tcpdump.org / Ethereal community
- we decide what to do and how to do that.
Anyone disagree?
fulvio