-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Early retransmit code #934
Comments
Note: Questions are better asked on the mailing list. |
Ya it was a bit fuzzy on whether this was a bug in the draft, so I raised this as an issue. |
I think this is not an issue any more |
sorry this is so old that i forgot why i raised this, will discuss with @ianswett offline and then close properly. |
More concrete example:
since largest_acked != largest_sent delay_until_lost = infinite so packet 3 is not lost in this round and needs to go through another round |
@siyengar You volunteered to write a PR, can you try fixing this issue you filed? |
will do |
@siyengar, some time has passed. Do you still intend to do this? |
@martinthomson put up #2021. Sorry about the delay |
I think this issue goes away with #1974.
…On Mon, Nov 19, 2018 at 4:38 PM Subodh Iyengar ***@***.***> wrote:
@martinthomson <https://github.com/martinthomson> put up #2021
<#2021>. Sorry about the delay
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#934 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AKjg1NfVp_OyMttHIYbz6nu0SG2GJ5Vfks5uw08WgaJpZM4QffCp>
.
|
@janaiyengar i think #1974 depends on how we add early retransmit timer back to that current PR. I think we might need something like this as well |
If we're in the early retransmit mode, a loss_time is set. If the timer is not yet fired, however we send a packet when the timer is armed, the largest_sent_packet changes. When the timer does fire before this new packet is acked, largest_sent_packet != largest_acked_packet, so delay_until_lost == infinite and none of the packets will be declared lost, however we would instead set a TLP alarm.
Is this intentional? Seems a bit weird.
The text was updated successfully, but these errors were encountered: