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

Short header: reserved bits #1511

Closed
rpaulo opened this issue Jul 2, 2018 · 2 comments
Closed

Short header: reserved bits #1511

rpaulo opened this issue Jul 2, 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.

Comments

@rpaulo
Copy link
Contributor

rpaulo commented Jul 2, 2018

The test says:

Reserved: The sixth, seventh, and eighth bits (0x7) of octet 0 are reserved for experimentation.

But there's no guidance on what they should be set to, so I think it should be:

Reserved: The sixth, seventh, and eighth bits (0x7) of octet 0 are reserved for experimentation and MUST be set to zero.

@martinthomson
Copy link
Member

Sure. You have to say what to do with the values if you get them. That is, you can't have recipients discard the packet if the value happens to be 1, because that might prevent the bits from being used.

@larseggert
Copy link
Member

larseggert commented Jul 3, 2018

MUST grease on tx (unless participating in experiment), MUST ignore on RX (unless participating in experiment)?

martinthomson added a commit that referenced this issue Jul 4, 2018
@martinthomson martinthomson added design An issue that affects the design of the protocol; resolution requires consensus. -transport labels Jul 4, 2018
@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
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.
Projects
None yet
Development

No branches or pull requests

4 participants