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

Fix some of the nits in #3214 #4016

Merged
merged 14 commits into from Aug 26, 2020
4 changes: 2 additions & 2 deletions draft-ietf-quic-transport.md
Expand Up @@ -1772,8 +1772,8 @@ completes, the client uses the transport parameters established in the
handshake. Not all transport parameters are remembered, as some do not apply to
future connections or they have no effect on use of 0-RTT.

The definition of a new transport parameter ({{new-transport-parameters}}) is
REQUIRED to specify whether it MUST, MAY, or MUST NOT be stored for 0-RTT. A
The definition of a new transport parameter ({{new-transport-parameters}}) MUST
specify whether that storing the transport parameter for 0-RTT is mandatory, optional, or prohibited. A
client need not store a transport parameter it cannot process.

A client MUST NOT use remembered values for the following parameters:
Expand Down