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

Does the first byte of stateless reset include random bits? #1678

Closed
huitema opened this issue Aug 16, 2018 · 2 comments
Closed

Does the first byte of stateless reset include random bits? #1678

huitema opened this issue Aug 16, 2018 · 2 comments
Labels
-transport design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list. parked An issue that we can't immediately address; for future discussion.

Comments

@huitema
Copy link
Contributor

huitema commented Aug 16, 2018

Section 6.13.4 of draft-transport-14 defines the first byte of the stateless reset packet as:

   +-+-+-+-+-+-+-+-+
   |0|K|1|1|0|0|0|0|
   +-+-+-+-+-+-+-+-+

I notice that the first byte is slightly different from the specification of the short header in section 4.2:

   +-+-+-+-+-+-+-+-+
   |0|K|1|1|0|R R R|
   +-+-+-+-+-+-+-+-+

Is that deliberate, or just an oversight?
@martinthomson martinthomson added design An issue that affects the design of the protocol; resolution requires consensus. -transport parked An issue that we can't immediately address; for future discussion. labels Aug 17, 2018
@martinthomson
Copy link
Member

It was deliberate, but only as a simplification. Once we know what those R values are, we can fix this too.

@martinthomson
Copy link
Member

This has been addressed. The text now shows:

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0|1|               Unpredictable Bits (182..)                ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

@mnot mnot added the has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list. label Mar 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-transport design An issue that affects the design of the protocol; resolution requires consensus. has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list. parked An issue that we can't immediately address; for future discussion.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@martinthomson @mnot @huitema