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.

Sign up for GitHub

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

Jump to bottom

Note that UDP 443 means nothing, in either direction of inference. #482

Merged
merged 3 commits into from
Jul 5, 2022
Merged

Note that UDP 443 means nothing, in either direction of inference. #482

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
28224c2
Note that UDP 443 means nothing, in either direction of inference.
britram May 18, 2022
09338a7
whitespaaaaaaaaaaaaaaace
britram May 18, 2022
fa80c4f
Update draft-ietf-quic-manageability.md
mirjak May 31, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 4 additions & 2 deletions draft-ietf-quic-manageability.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -567,8 +567,10 @@ Connections {{?I-D.ietf-dprive-dnsoquic}}. These are both known at the time
of writing to have active Internet deployments, so an assumption that all
QUIC traffic is HTTP/3 is not valid. HTTP/3 uses UDP port 443 by
convention but various methods can be used to specify alternate port numbers.
Simple assumptions about whether a given flow is using QUIC based upon a UDP
port number may therefore not hold; see also {{Section 5 of RFC7605}}.
Other applications (e.g. Microsoft's SMB over QUIC) also use UDP port 443 by
mirjak marked this conversation as resolved.
Show resolved Hide resolved
default. Therefore, simple assumptions about whether a given flow is using
QUIC, or indeed which application it might be using QUIC, based solely upon
a UDP port number may not hold; see also {{Section 5 of RFC7605}}.

While the second-most-significant bit (0x40) of the first octet is set to 1 in
most QUIC packets of the current version (see {{public-header}} and {{Section 17
Expand Down