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

Flow control intro sentence #4719

Merged
merged 3 commits into from Jan 12, 2021
Merged

Flow control intro sentence #4719

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1f27cfd
It is necessary => Receivers need to
MikeBishop Jan 8, 2021
781d239
Apply suggestions from code review
MikeBishop Jan 11, 2021
4223c78
Rewrap
MikeBishop Jan 11, 2021
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
6 changes: 3 additions & 3 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -822,9 +822,9 @@ frame.
Receivers need to limit the amount of data that they are required to buffer, in
order to prevent a fast sender from overwhelming them or a malicious sender from
consuming a large amount of memory. To enable a receiver to limit memory
commitment to a connection and to apply back pressure on the sender, streams are
flow controlled both individually and as an aggregate. A QUIC receiver controls
the maximum amount of data the sender can send on a stream at any time, as
commitments for a connection, streams are
flow controlled both individually and across a connection as a whole. A QUIC receiver controls
the maximum amount of data the sender can send on a stream as well as across all streams at any time, as
described in {{data-flow-control}} and {{fc-credit}}.

Similarly, to limit concurrency within a connection, a QUIC endpoint controls
Expand Down