Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Don't retransmit lost packets that are acked later #3957

Merged
merged 8 commits into from Sep 1, 2020
Merged

Don't retransmit lost packets that are acked later #3957

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
d2658fd
retain info on lost packets
janaiyengar Jul 24, 2020
98c9d04
rewrite based on feedback
janaiyengar Jul 24, 2020
b0ed70a
smithing
janaiyengar Jul 24, 2020
e8db499
split up sentence
janaiyengar Jul 24, 2020
7abdc4b
wait for one PTO, not 3
janaiyengar Jul 27, 2020
e3999ba
sync recovery
janaiyengar Jul 27, 2020
89ff7fa
add ref to transport
janaiyengar Jul 28, 2020
2e534ad
Ian's comment
janaiyengar Jul 28, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions draft-ietf-quic-recovery.md
View file
Open in desktop
Expand Up @@ -1008,8 +1008,8 @@ packet number and crypto context and store the per-packet fields
({{sent-packets-fields}}) for loss recovery and congestion control.

After a packet is declared lost, the endpoint can still maintain state for it
for an amount of time, such as a PTO, to allow for packet reordering. This
enables a sender to detect spurious retransmissions.
for an amount of time to allow for packet reordering; see Section 13.3 of
{{QUIC-TRANSPORT}}. This enables a sender to detect spurious retransmissions.

Sent packets are tracked for each packet number space, and ACK
processing only applies to a single space.
Expand Down