Closed kazu-yamamoto closed 2 years ago
Encryption keys are version specific. If a greasing version is used, its encryption key is unknown to the peer. Note that the version field in the long header is always plain without header protection.
Both endpoints support both v2 and the new nego.
Both endpoints support both v2 and the new nego.
A server supports RFC9000 only.
A server supports RFC9000 only.
The client sent CC because version_information is missing.
todo for compatible negotiation:
version_information
version_information
version_information
version_information
is broken, send TRANSPORT_PARAMETER_ERROR
VERSION_NEGOTIATION_ERROR
if version_information
is missingVERSION_NEGOTIATION_ERROR
if version_information
validation failsversion_information
TP dynamically (https://github.com/quicwg/version-negotiation/issues/74)TRANSPORT_PARAMETER_ERROR
if v0 is included.Call for discussion:
version_information
does not exist, it should be treated as 1, [1]
.Done via #24.
https://quicwg.org/quic-v2/draft-ietf-quic-v2.html
https://quicwg.org/version-negotiation/draft-ietf-quic-version-negotiation.html
This replaces Section 6 of RFC 9000.