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

Clarify loss epoch #3213

Merged
merged 2 commits into from
Nov 12, 2019
Merged

Clarify loss epoch #3213

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
41583ce
Clarify loss epoch
ianswett Nov 11, 2019
babf706
Another try
ianswett Nov 11, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 7 additions & 6 deletions draft-ietf-quic-recovery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -217,12 +217,13 @@ not available.

### Clearer Loss Epoch

QUIC ends a loss epoch when a packet sent after loss is declared is
acknowledged. TCP waits for the gap in the sequence number space to be filled,
and so if a segment is lost multiple times in a row, the loss epoch may not
end for several round trips. Because both should reduce their congestion windows
only once per epoch, QUIC will do it correctly once for every round trip that
experiences loss, while TCP may only do it once across multiple round trips.
QUIC starts a loss epoch when a packet is lost and ends one when any packet
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/one/it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I actually think one reads more clearly, but maybe that's me?

sent after the epoch starts is acknowledged. TCP waits for the gap in the
sequence number space to be filled, and so if a segment is lost multiple times
in a row, the loss epoch may not end for several round trips. Because both
should reduce their congestion windows only once per epoch, QUIC will do it
correctly once for every round trip that experiences loss, while TCP may only
do it once across multiple round trips.

### No Reneging

Expand Down