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.

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

A tiny nit: the ClientHello is not subject to MAX_STREAM_DATA. #803

Merged
merged 5 commits into from Oct 10, 2017
Merged
Changes from 1 commit
Commits
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
4 changes: 2 additions & 2 deletions draft-ietf-quic-transport.md
Expand Up @@ -2765,9 +2765,9 @@ handshake stream, Stream 0, is exempt from the connection-level data
limits established by MAX_DATA. Data on stream 0 other than the
TLS ClientHello is still subject to stream-level data limits and
Copy link
Contributor

Choose a reason for hiding this comment

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

editorial nit: Can you say "initial cryptographic message from the client" instead of TLS ClientHello, for consistency (here and below)?

MAX_STREAM_DATA. The TLS ClientHello is exempt from flow control because it needs
to be sent in one piece regardless of the server's flow control
to be sent in a single packet regardless of the server's flow control
state. This rule applies even for 0-RTT handshakes where the
remembered value of MAX_STREAM_DATA would not permit sending
remembered value of MAX_STREAM_DATA does not permit sending
a full ClientHello.

Flow control is described in detail in {{flow-control}}, and congestion control
Expand Down