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

Don't amplify accidentally when closing #1911

Merged
merged 3 commits into from Oct 28, 2018
Merged

Don't amplify accidentally when closing #1911

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
7a9e8e4
Don't amplify accidentally when closing
martinthomson Oct 25, 2018
e06269b
Always like removing text
martinthomson Oct 25, 2018
3ef0fab
redundant word whack-a-mole
martinthomson Oct 25, 2018
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: 6 additions & 0 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -2228,6 +2228,12 @@ Note:
control, which are not expected to be relevant for a closed connection.
Retransmitting the final packet requires less state.

New packets from unverified addresses could be used to create an amplification
attack (see {{address-validation}}). To avoid this, endpoints MUST either limit
transmission of closing frames to validated addresses or drop packets without
response if the response would be more than three times larger than the received
packet.

After receiving a closing frame, endpoints enter the draining state. An
endpoint that receives a closing frame MAY send a single packet containing a
closing frame before entering the draining state, using a CONNECTION_CLOSE frame
Expand Down