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

Can Server Require Connection ID to be Included in Packets Sent by Clients? #789

Closed
nibanks opened this issue Sep 22, 2017 · 2 comments
Closed
Labels
invalid A duplicate, overcome-by-events, ill-formed, or off-topic issue, or a question better asked on-list.

Comments

@nibanks
Copy link
Member

nibanks commented Sep 22, 2017

This is slightly related to #659.

Is it reasonable/acceptable for a server implementation to require that a client always include the connection ID? If so, what exactly should it do if it receives a new connection where the client specified omit_connection_id in its transport parameters? Should it drop the connection? Send an error back (if so, what error)?

It seems to me that if we want to allow servers to restrict the usage of omit_connection_id by the client, we should probably have some mechanism to indicate the client the connection must include the connection ID. One possibility is a new transport parameters that is server specific that indicates connection id is required.

@RyanTheOptimist
Copy link
Contributor

RyanTheOptimist commented Sep 22, 2017 via email

@nibanks
Copy link
Member Author

nibanks commented Sep 22, 2017

So the omit_connection_id indicates to the remote whether or not they should include connection ID. I thought it was indicating the sender was going to omit them. That makes a bit more sense. Thanks.

@nibanks nibanks closed this as completed Sep 22, 2017
@mnot mnot added the invalid label Sep 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid A duplicate, overcome-by-events, ill-formed, or off-topic issue, or a question better asked on-list.
Projects
None yet
Development

No branches or pull requests

3 participants