Skip to content

Commit

Permalink
Transport Parameters are not APLN Specific
Browse files Browse the repository at this point in the history
  • Loading branch information
nibanks committed Jul 29, 2020
1 parent ca51fd1 commit 9a2b672
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions draft-ietf-quic-transport.md
Expand Up @@ -1741,6 +1741,13 @@ 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}}.

When sent by the client, transport parameters are not specific to a particular
ALPN being negotiated. Therefore, a client cannot have application protocol
specific values in the transport parameters. Application protocols should take
this into account when designing versioning schemes, and not place restrictions
on the values in the transport parameters that might prevent protocol changes
in future version of the application protocol.


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

Expand Down

0 comments on commit 9a2b672

Please sign in to comment.