Mike Karels (firstname.lastname@example.org)
Mon, 08 Dec 86 10:15:31 PST
The timeout for TCP on 4.2/3 is rather longer than 30 sec.
The actual time depends on the round-trip time, as the limit
is on the number of retransmissions. On 4.3, the timeout
is at least 108 sec. with short RTT's. The limit on 4.2
was nearer 45 sec. As Van Jacobson says in his message,
the keepalive time will have to be adjusted for long RTT's
as well, but I doubt that Craig is using the keepalive timer.
How can the TCP "just" inform the application about the problem?
Unless there's a control channel to the application that allows
the passage of status data, a send call must return an error.
After that error, the application can't tell how much of the data,
if any, was transmitted. "Reliable byte stream with possible gaps
in case of error" isn't very satisfying.
This archive was generated by hypermail 2.0b3 on Thu Mar 09 2000 - 14:37:00 GMT