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 recommend stateless reset #1907

Merged
merged 1 commit into from Oct 25, 2018
Merged

Don't recommend stateless reset #1907

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
5 changes: 3 additions & 2 deletions draft-ietf-quic-transport.md
View file
Open in desktop
Expand Up @@ -1030,8 +1030,9 @@ IDs, QUIC processes the packet as part of that connection. Endpoints MUST drop
packets with zero-length Destination Connection ID fields if they do not
correspond to a single connection.

Endpoints SHOULD send a Stateless Reset ({{stateless-reset}}) for any packets
that cannot be attributed to an existing connection.
Endpoints can send a Stateless Reset ({{stateless-reset}}) for any packets that
cannot be attributed to an existing connection. A stateless reset allows a peer
to more quickly identify when a connection becomes unusable.

Packets that are matched to an existing connection, but for which the endpoint
cannot remove packet protection, are discarded.
Expand Down