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

Discuss Application-Limited Sending #1637

Merged
merged 13 commits into from Jan 29, 2019
Merged

Discuss Application-Limited Sending #1637

Changes from 1 commit
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
ceab0e2
Discuss Application-Limited Sending
ianswett Aug 7, 2018
a38f3f9
Update draft-ietf-quic-recovery.md
ianswett Aug 7, 2018
b6546ab
Merge branch 'master' into ianswett-app-limited
ianswett Jan 11, 2019
f49e4a4
Rewrite and specifically note pacing
ianswett Jan 11, 2019
10f9ded
Update draft-ietf-quic-recovery.md
ianswett Jan 11, 2019
fb13365
Update draft-ietf-quic-recovery.md
martinthomson Jan 15, 2019
3fb5df1
Update draft-ietf-quic-recovery.md
ianswett Jan 16, 2019
6f6e34c
Merge branch 'master' into ianswett-app-limited
ianswett Jan 23, 2019
f9aaa91
Update draft-ietf-quic-recovery.md
ianswett Jan 23, 2019
bb96c70
Update draft-ietf-quic-recovery.md
janaiyengar Jan 29, 2019
c21ced5
Update draft-ietf-quic-recovery.md
janaiyengar Jan 29, 2019
07ef710
Update draft-ietf-quic-recovery.md
ianswett Jan 29, 2019
06cf5b0
Update draft-ietf-quic-recovery.md
ianswett Jan 29, 2019
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: 4 additions & 3 deletions draft-ietf-quic-recovery.md
View file
Open in desktop
Expand Up @@ -1004,9 +1004,10 @@ under-utilized due to insufficient application data to send or flow control
limits.
ianswett marked this conversation as resolved.
Show resolved Hide resolved

When the sender is pacing (see {{pacing}}) packets, the sender may be unable
to use the full congestion window for a period of time after receiving an
ACK, due to pacing. In this case, the sender should not consider themselves
application limited and should allow the congestion window to increase.
to use the full congestion window for a period of time after receiving
acknowledgements, due to pacing. In this case, the sender should not consider
themselves application limited and should allow the congestion window to
increase.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested rephrasing: "A sender that uses pacing (see {{pacing}}) might delay sending of packets and might not fully utilize the congestion window due to this delay. A sender should not consider itself application limited if it might have utilized the entire congestion window without pacing delay."

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Accepted with minor tweaks.


## Discarding Packet Number Space State

Expand Down