RE: proposed tcpdump dinner @IETF55

["Fulvio Risso" <risso () polito it>]

Hi.
Unfortunately, none of us can be there.

> -----Original Message-----
> From: owner-tcpdump-workers () sandelman ottawa on ca
> [mailto:owner-tcpdump-workers () sandelman ottawa on ca]On Behalf Of
> Michael Richardson
> Sent: Wednesday, November 06, 2002 21:25
> To: tcpdump-workers () tcpdump org
> Subject: [tcpdump-workers] proposed tcpdump dinner @IETF55
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
>
>
> I'd like to propose a dinner in Atlanta, possibly Tuesday evening.
> There is no social event on Tuesday evening.
>
> 1800-1930 Break
> 1930-2200 Evening Sessions
> Salon IV  APP crisp Cross Registry Information Service Protocol WG
> Salon II  INT mobileip IP Routing for Wireless/Mobile Hosts WG *
> Consulate OPS sming Next Generation Structure of Management Information WG
> Salon A         SEC smime S/MIME Mail Security WG
> Salon III SUB sub-ip SUB-IP Area Meeting *
> Salon B         TSV ippm IP Performance Metrics WG
> Salon I         TSV sip Session Initiation Protocol WG
>
> It might be that Fenner won't even have AD duties at that time,
> so we might not
> even be restricted to end at 7:30pm (1.5 hours at Pittypat's is tight)
>
> A nice Cajun place that I've been to several times is Pittypat's Porch.
>   http://www.accessatlanta.com/auto_docs/dining/22368.html
>
> If we can get a count, we can make a reservation (recommended that we do
> this!). Other suggestions welcome.
>
> Topics I'd like to discuss:
>
>        1) windows code integration (status? feelings? etc..)

As far we are concerned, the integration has been done this summer.
We don't know of any pending issues.
Maybe, we can make a phone call to Michael next week, so that we get updated
with the latest news.
Unfortunately, 7.30pm is during the night here, so I cannot place a phone
call during the dinner.

        fulvio


>        2) tcpdump 4.x
>         a) my "netdissect" branch.
>         b) documenting the internal interfaces of tcpdump.
>         c) getting rid of redundant "utility" functions
>         d) the I/O interface - FILE vs (*outputfunc).
>         e) attacks on the tool itself.
>         f) what else?
>
>        3) libpcap 1.0
>         a) does anyone care? (I think so, but...)
>         b) what are your requirements?
>         c) new formats
>         d) future formats
>         e) any IETF interaction here?   (INCH? other stuff?)
>
>        4) add yours here.
>
> ]       ON HUMILITY: to err is human. To moo, bovine.           |
>  firewalls  [
> ]   Michael Richardson, Sandelman Software Works, Ottawa, ON
> |net architect[
> ] mcr () sandelman ottawa on ca http://www.sandelman.ottawa.on.ca/
> |device driver[
> ] panic("Just another Debian GNU/Linux using, kernel hacking,
> security guy"); [
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
> Comment: Finger me for keys
>
> iQCVAwUBPcl6fYqHRg3pndX9AQGA7gQArp1oZ65pFaXJhQ2mtxspBpDjfxCOtowx
> 4uvRl4UZoLX7J4dcDIYK+AvKbcA7Q8Boc1xDIAaEpJWqJRzCLZiiEajqfU4GF22B
> rY7xCcuabrGMhUdL7Ggk5ub63c+sU8yYx5+hUoLerTXtZ5jmiIInAZYPTOgeg1vu
> oN+DNK3QgFc=
> =F1LM
> -----END PGP SIGNATURE-----
> -
> This is the TCPDUMP workers list. It is archived at
> http://www.tcpdump.org/lists/workers/index.html
> To unsubscribe use
mailto:tcpdump-workers-request () tcpdump org?body=unsubscribe

-
This is the TCPDUMP workers list. It is archived at
http://www.tcpdump.org/lists/workers/index.html
To unsubscribe use mailto:tcpdump-workers-request () tcpdump org?body=unsubscribe