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

Transport Parameters are not APLN Specific #3973

Merged
merged 4 commits into from Jul 31, 2020
Merged

Transport Parameters are not APLN Specific #3973

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9a2b672
Transport Parameters are not APLN Specific
nibanks Jul 29, 2020
f518bf6
Martin's suggestion
nibanks Jul 30, 2020
95c5919
Jana's suggestion
nibanks Jul 30, 2020
967fcd5
PR Feedback
nibanks Jul 31, 2020
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
9 changes: 9 additions & 0 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -1741,6 +1741,15 @@ parameters as a connection error of type TRANSPORT_PARAMETER_ERROR.
Endpoints use transport parameters to authenticate the negotiation of
connection IDs during the handshake; see {{cid-auth}}.

Application Layer Protocol Negotiation (ALPN; see {{?ALPN=RFC7301}}) allows
clients to offer multiple application protocols during connection
establishment. The transport parameters that a client includes during the
handshake apply to all application protocols that the client offers. Application
protocols can recommend values for transport parameters, such as the initial
flow control limits. However, application protocols that set constraints on
values for transport parameters could make it impossible for a client to offer
multiple application protocols if these constraints conflict.


### Values of Transport Parameters for 0-RTT {#zerortt-parameters}

Expand Down