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

fix incorrect field name #2478

Merged
merged 2 commits into from Feb 18, 2019
Merged

fix incorrect field name #2478

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8420fe3
fix incorrect field name
kazuho Feb 18, 2019
e805db0
Wrap
martinthomson Feb 18, 2019
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
6 changes: 3 additions & 3 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -2317,9 +2317,9 @@ of bytes following it that are set to unpredictable values. The last 16 bytes
of the datagram contain a Stateless Reset Token.

A stateless reset will be interpreted by a recipient as a packet with a short
header. For the packet to appear as valid, the Random Bits field needs to
include at least 182 bits of data (or 23 bytes, less the two fixed bits). This
is intended to allow for a Destination Connection ID of the maximum length
header. For the packet to appear as valid, the Unpredictable Bits field needs
to include at least 182 bits of data (or 23 bytes, less the two fixed bits).
This is intended to allow for a Destination Connection ID of the maximum length
permitted, with a minimal packet number, and payload. The Stateless Reset Token
corresponds to the minimum expansion of the packet protection AEAD. More
unpredictable bytes might be necessary if the endpoint could have negotiated a
Expand Down