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

Note that the QUIC bit cannot be used with forwarding mode #89

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions draft-ietf-masque-quic-proxy.md
Original file line number Diff line number Diff line change
Expand Up @@ -734,6 +734,21 @@ headers does not apply.
A proxy MAY additionally add ECN markings to signal congestion being experienced
on the proxy itself.

## QUIC Version Independence

When forwarding mode is enabled, the client and target MAY negotiate any QUIC
version, and MAY send packets of that version through the forwarding path.
The proxy does not know what version they are using, so it can only require that
these packets conform to the QUIC invariants for short-header packets
({{?RFC8999}}, Section 5.2).

QUIC version 1 specifies a Fixed Bit (a.k.a. the "QUIC bit") with a fixed value
to support sharing a 5-tuple with other protocols such as DTLS, but the QUIC
invariants do not guarantee the value of this bit. Accordingly proxies with
forwarding mode enabled MUST NOT rely on this bit for protocol identification,
and SHOULD send and accept the `grease_quic_bit` transport parameter
{{?QUIC-GREASE=RFC9297}} to avoid ossification of the forwarding mode path.

# Example

Consider a client that is establishing a new QUIC connection through the proxy.
Expand Down