This repository has been archived by the owner on Aug 11, 2020. It is now read-only.
TODO: Implement a maximum retransmission limit #78
Comments
jasnell
added a commit
to jasnell/quic
that referenced
this issue
Dec 3, 2019
Allows monitoring the number of times packets have to be retransmitted because of loss or delayed ack. An implementation experiencing a high number of retransmits may need to be torn down or mitigated in some way. This allows the user code to keep track. Later, we may want to add a setting that enforces a maximum number of retransmissions before failing a connection. Fixes: nodejs#78
jasnell
added a commit
to jasnell/quic
that referenced
this issue
Dec 4, 2019
Allows monitoring the number of times packets have to be retransmitted because of loss or delayed ack. An implementation experiencing a high number of retransmits may need to be torn down or mitigated in some way. This allows the user code to keep track. Later, we may want to add a setting that enforces a maximum number of retransmissions before failing a connection. Fixes: nodejs#78
addaleax
pushed a commit
that referenced
this issue
Dec 11, 2019
Allows monitoring the number of times packets have to be retransmitted because of loss or delayed ack. An implementation experiencing a high number of retransmits may need to be torn down or mitigated in some way. This allows the user code to keep track. Later, we may want to add a setting that enforces a maximum number of retransmissions before failing a connection. Fixes: #78 PR-URL: #207 Reviewed-By: #207
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
QuicSocket/QuicSession ... Implement a maximum retransmission limit. Currently, a QuicSession will attempt retransmission an unlimited number of times. This should be constrained by some user-specific limit with a reasonable default. The retransmission here is used to handle loss packets.
Type: functionality/test
Priority: high
The text was updated successfully, but these errors were encountered: