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 stateless reset short header packet type #1315

Merged
merged 2 commits into from
Apr 24, 2018
Merged

fix stateless reset short header packet type #1315

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
29d7a9f
fix stateless reset short header packet type
marten-seemann Apr 23, 2018
b98784a
Mike's review
marten-seemann Apr 24, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 5 additions & 6 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2031,12 +2031,11 @@ this value differs from previous packets. Ths results in two problems:
about this.

The Packet Number field is set to a randomized value. The server SHOULD send a
packet with a short header and a type of 0x1F. This produces the shortest
possible packet number encoding, which minimizes the perceived gap between the
last packet that the server sent and this packet. A server MAY use a different
short header type, indicating a different packet number length, but a longer
packet number encoding might allow this message to be identified as a stateless
reset more easily using heuristics.
packet with a short header and a packet number length of 1 octet. Using the
shortest possible packet number encoding minimizes the perceived gap between the
last packet that the server sent and this packet. A server MAY indicate a
different packet number length, but a longer packet number encoding might allow
this message to be identified as a stateless reset more easily using heuristics.

After the Packet Number, the server pads the message with an arbitrary
number of octets containing random values.
Expand Down