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 connection id need to be in a consistent location? #293

Closed
ianswett opened this issue Feb 12, 2017 · 3 comments
Closed

Does the connection id need to be in a consistent location? #293

ianswett opened this issue Feb 12, 2017 · 3 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

@ianswett
Copy link
Contributor

@martinthomson created a header proposal that provides a fixed 8 byte connection id in a fixed location.

We need to decide if this is a requirement or a nice to have.

I haven't found any environments it needed to be in a fixed location for all packets, as long as it's easy to determine where it will be from the first byte of the packet.
@martinthomson
Copy link
Member

I thought that it was nice to have, but not a deal-breaker.

@ianswett
Copy link
Contributor Author

Agreed.

@mnot mnot added design An issue that affects the design of the protocol; resolution requires consensus. -transport labels Feb 15, 2017
@janaiyengar janaiyengar mentioned this issue Mar 7, 2017
Merged
@MikeBishop
Copy link
Contributor

#361 purports to address this; please re-open or file a new issue if that's incorrect.

@janaiyengar janaiyengar mentioned this issue Mar 15, 2017
Closed
@mnot mnot added the has-consensus An issue that the Chairs have determined has consensus, by canvassing the mailing list. label Apr 19, 2017
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.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@martinthomson @mnot @MikeBishop @ianswett