Quoting Ian McDonald: | Doesn't this rely on the receiver sending back the RTT which | it can't know at that point of time?? It's only had the request then | so rtt can only be determined by the receiver. But I could be wrong | here and I will go back and read the code/rfcs when back at home. It samples the RTT from the initial SYN (Request/Response) exchange: * the client adds a timestamp option when sending its Request * it then enters the REQUEST state and waits for the matching Response * when the server replies with a timestamp echo option, the client subtracts this value from t_now, and also the elapsed_time (if supplied) * if there is no timestamp echo option in the reply, it does not set the field Using the SYN exchange is suggested both in the erratum to RFC 4342 and in draft 3448bis. - Gerrit - To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
