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

Describe how and why a server might choose connection IDs #514

Closed
janaiyengar opened this issue May 10, 2017 · 3 comments
Closed

Describe how and why a server might choose connection IDs #514

janaiyengar opened this issue May 10, 2017 · 3 comments
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.

Comments

@janaiyengar
Copy link
Contributor

In #493 there are multiple server-chosen connection IDs, and a set of examples describing the intent of the design ought to be useful for implementers and deployments. This may belong in the applicability statement.
@janaiyengar janaiyengar added editorial An issue that does not affect the design of the protocol; does not require consensus. -transport labels May 10, 2017
@igorlord
Copy link
Contributor

I was going to write something up about this in Applicability, once we settle treatment of the Connection ID in the protocol.

@mirjak
Copy link
Contributor

mirjak commented May 25, 2017

Yes please send text; I'll put a place-holder in for now!

@janaiyengar janaiyengar mentioned this issue Mar 13, 2018
Closed
@janaiyengar
Copy link
Contributor Author

Moved to quicwg/ops-drafts#29.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
-transport editorial An issue that does not affect the design of the protocol; does not require consensus.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mirjak @janaiyengar @igorlord