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

Update name of TPs #2539

Merged
merged 6 commits into from Apr 9, 2019
Merged

Update name of TPs #2539

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
b9abf32
Update name of TPs
martinduke Mar 21, 2019
a3e585c
whitespace
martinduke Mar 21, 2019
42e784a
Update draft-ietf-quic-transport.md
martinthomson Mar 21, 2019
6e8ff86
Update draft-ietf-quic-transport.md
martinthomson Mar 21, 2019
9295788
Update draft-ietf-quic-transport.md
ianswett Mar 21, 2019
1bd4e97
unplural
martinthomson Apr 9, 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
2 changes: 1 addition & 1 deletion draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -5258,7 +5258,7 @@ higher-numbered stream ID is received. Thus, on a new connection, opening
stream 2000001 opens 1 million streams, as required by the specification.

The number of active streams is limited by the initial_max_streams_bidi and
initial-max-streams-uni transport parameters, as explained in
initial_max_streams_uni transport parameters, as explained in
{{controlling-concurrency}}. If chosen judiciously, this limit mitigates the
martinduke marked this conversation as resolved.
Show resolved Hide resolved
effect of the stream commitment attack. However, setting the limit too low
could affect performance when applications expect to open large number of
Expand Down