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

Split conditions for Initial CONNECTION_CLOSE #4003

Merged
merged 1 commit into from Aug 20, 2020
Merged

Split conditions for Initial CONNECTION_CLOSE #4003

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -2824,8 +2824,8 @@ when converting to a CONNECTION_CLOSE of type 0x1c.
CONNECTION_CLOSE frames sent in multiple packet types can be coalesced into a
single UDP datagram; see {{packet-coalesce}}.

An endpoint might send a CONNECTION_CLOSE frame in an Initial packet or in
response to unauthenticated information received in Initial or Handshake
An endpoint can send a CONNECTION_CLOSE frame in an Initial packet. This might
be in response to unauthenticated information received in Initial or Handshake
packets. Such an immediate close might expose legitimate connections to a
denial of service. QUIC does not include defensive measures for on-path attacks
during the handshake; see {{handshake-dos}}. However, at the cost of reducing
Expand Down