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

Allow alternate restarts after idle #2187

Merged
merged 7 commits into from Dec 18, 2018
Merged

Allow alternate restarts after idle #2187

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
6df0e3a
Allow alternate restarts after idle
janaiyengar Dec 14, 2018
b866ed6
restructure
janaiyengar Dec 15, 2018
2133100
Update draft-ietf-quic-recovery.md
martinthomson Dec 18, 2018
2bbc1ff
Update draft-ietf-quic-recovery.md
martinthomson Dec 18, 2018
6fdb947
more changes
janaiyengar Dec 18, 2018
adfc4a0
becomes
janaiyengar Dec 18, 2018
1053a1f
simpler
janaiyengar Dec 18, 2018
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
7 changes: 2 additions & 5 deletions draft-ietf-quic-recovery.md
View file
Open in desktop
Expand Up @@ -964,11 +964,8 @@ in Linux (3.11 onwards).

## Sending data after an idle period

A sender becomes idle if it has no bytes in flight. A sender can become idle
when it is application limited and has no data to send, or when it marks packets
as lost (and therefore not in flight).

A sender's congestion window MUST not increase while it is idle.
A sender becomes idle if it ceases to send data and has no bytes in flight. A
sender's congestion window MUST not increase while it is idle.

When sending data after becoming idle, a sender MUST reset its congestion window
to the initial congestion window (see Section 4.1 of {{?RFC5681}}), unless it
Expand Down