Date:        Sun, 17 Aug 2003 05:29:17 -0400 (EDT)
    From:        der Mouse <mouse@Rodents.Montreal.QC.CA>
    Message-ID:  <200308170941.FAA25093@Sparkle.Rodents.Montreal.QC.CA>

  | Actually, I wonder if the ideal thing wouldn't be to start a timer,
  | with a value equal to the time it takes for the TCP stack to drop a
  | connection for lack of response to data segments, and if the address
  | hasn't come back by the time the timer expires, kill the connections.

If the connection in question is attempting to send something, that will
happen anyway.   So, this would only affect idle connections.   I think
I'd prefer them to stay untouched, until something causes a change in
state.

Another example, I pop my wireless card from my laptop, address goes
away, your timer starts.   Laptop sleeps (suspend mode), does nothing
for a day (or 3 or 4).   Laptop resumes, time flies forward very rapidly,
your timer goes off, connection terminated.  Meanwhile, I am re-inserting
the wireless card, DHCP is giving me the same address back, and the
(assumed patient) other end of the connection is just sitting there
waiting to talk to me...

kre