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

Restore missing 'in' #4585

Merged
merged 1 commit into from Jan 7, 2021
Merged

Restore missing 'in' #4585

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 @@ -4809,7 +4809,7 @@ used for any new packets that are sent; as described in {{retry-continue}},
reusing packet numbers could compromise packet protection.

A client only receives acknowledgments for its 0-RTT packets once the handshake
is complete, as defined Section 4.1.1 of {{QUIC-TLS}}.
is complete, as defined in Section 4.1.1 of {{QUIC-TLS}}.

A client MUST NOT send 0-RTT packets once it starts processing 1-RTT packets
from the server. This means that 0-RTT packets cannot contain any response to
Expand Down