You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OnLossDetectionTimeout in the recovery draft always calls SetLossDetectionTimer, resulting in an infinite loop which continues even after the connection is closed. It would be nice if conditions such as if (connection is open): are added or comments are added.
The text was updated successfully, but these errors were encountered:
SetLossDetectionTimer cancels the timer when there are no ack-eliciting packets in flight, so I can't see how this would create an infinite loop. I'd prefer to not further complicate the pseudo-code here for this corner case.
martinthomson
added
the
invalid
A duplicate, overcome-by-events, ill-formed, or off-topic issue, or a question better asked on-list.
label
Jul 29, 2020
OnLossDetectionTimeout
in the recovery draft always callsSetLossDetectionTimer
, resulting in an infinite loop which continues even after the connection is closed. It would be nice if conditions such asif (connection is open):
are added or comments are added.The text was updated successfully, but these errors were encountered: