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

Proposal to make Version Negotiation more like Retry to punt VN to QUICv2 #2313

Merged
merged 10 commits into from Feb 13, 2019
12 changes: 6 additions & 6 deletions draft-ietf-quic-transport.md
Expand Up @@ -1134,12 +1134,12 @@ expectation that it will eventually receive an Initial packet.
When a client receives a Version Negotiation packet, it MUST abandon the
current connection attempt. Version Negotiation packets are designed to allow
future versions of QUIC to negotiate the version in use between endpoints.
It is therefore expected for future versions of QUIC to change how
implementations which support multiple versions of QUIC react to Version
Negotiation packets when attempting to establish a connection of this version.
How to perform version negotiation is left as future work defined by future
versions of QUIC. In particular, that future work will need to ensure
robustness against version downgrade attacks {{version-downgrade}}.
Future versions of QUIC might change how implementations that support multiple
versions of QUIC react to Version Negotiation packets when attempting to
establish a connection using this version. How to perform version negotiation
is left as future work defined by future versions of QUIC. In particular,
that future work will need to ensure robustness against version downgrade
attacks {{version-downgrade}}.


### Version Negotiation Between Draft Versions
Expand Down