Invariants in Transport Parameters #1672
Labels
-invariants
-transport
editorial
An issue that does not affect the design of the protocol; does not require consensus.
The transport draft says:
"When an endpoint accepts multiple QUIC versions, it can potentially
interpret transport parameters as they are defined by any of the QUIC
versions it supports. The version field in the QUIC packet header is
authenticated using transport parameters. The position and the
format of the version fields in transport parameters MUST either be
identical across different QUIC versions, or be unambiguously
different to ensure no confusion about their interpretation. One way
that a new format could be introduced is to define a TLS extension
with a different codepoint."
It seems that this actually belongs in the invariants draft.
The text was updated successfully, but these errors were encountered: