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

Consider a different fallback behavior for QUIC-only endpoints #73

Open
bemasc opened this issue Nov 6, 2019 · 0 comments
Labels
wg

Comments

@bemasc
Copy link
Collaborator

@bemasc bemasc commented Nov 6, 2019

Currently, if a server publishes a QUIC-only HTTPSSVC RRSet with ESNI, there is no way for a client to fall back to a non-QUIC connection, because doing so would reveal the SNI. This could increase the likelihood of partial outages for server admins who haven't considered the small fraction of users whose network path does not support QUIC.

Reviewers have reported concerns that this creates an undesirable level of fragility. We should consider whether there is an alternative design that would be less likely to result in accidental breakage.

@bemasc bemasc added the wg label Nov 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.