🚀 go-pugleaf

>   It sounds like the
>   implementation you were measuring decided that it was a case of the
>   retransmission being acked and therefore didn't want to corrupt the
>   srtt by including what the implementors thought was bogus data.

Ah, excellent point, but I've managed to rule this one out. I'm monitoring
retransmissions as well, and there aren't any happening at the right time to
account for the behaviour I described. It seems
the SRTT is falling to zero purely due to rounding errors with very
small round trip times. However, this doesnt preclude the resulting
behaviour being due to the implementors allowing for the circumstances
you describe. 

There seems to be two possible approaches (given that it is undesirable to
have a SRTT of zero):
Let the SRTT do whatever it wants, but never let the RTT be rounded to zero,
or do something different with the SRTT if it does reach zero. Clearly
the second approach (whether intentionally or not) is taken in the tcp
I'm using. 
Given this, what alternative value should it be set to? Has anyone
tackled this problem before? And what happens if it *is* left at zero?
(I shall now go away and find out the answer to the last question!)

Steve