Greg Wilkins wrote: > I think fail fast is also desirable, but I'm not sure it is so > desirable that I'd advocate a regular keep-alive message just > failure detection. But if keep-alive messages are required to > keep open connections through transparent proxies, then it could > be 2 birds with 1 stone. Sad keepalive story. I have used a 3G mobile network where a keepalive is needed every 30 seconds to keep an SSH connection alive, and I've used some other NAT where 30 seconds was too long. Keepalives are particularly unwelcome on mobile devices because of the battery drain, but there is often no other easy way to reliably pick up incoming data in a timely fashion. I guess recommended keepalive values are something so go into the HTTP long-polling recommendations document too. We could do with measurements. -- Jamie
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.