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

Clarify sentence describing a misrouted Stateless Reset #2073

Merged
merged 1 commit into from
Nov 29, 2018
Merged

Clarify sentence describing a misrouted Stateless Reset #2073

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion draft-ietf-quic-transport.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2319,7 +2319,7 @@ Using a randomized connection ID results in two problems:
critical for routing toward the peer, then this packet could be incorrectly
routed. This might also trigger another Stateless Reset in response, see
{{reset-looping}}. A Stateless Reset that is not correctly routed is
ineffective in causing errors to be quickly detected and recovered. In this
an ineffective error detection and recovery mechanism. In this
case, endpoints will need to rely on other methods - such as timers - to
detect that the connection has failed.

Expand Down