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.

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

Fix handling of Retry in recovery #3148

Merged
merged 2 commits into from
Oct 29, 2019
Merged
Changes from 1 commit
Commits
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-recovery.md
Original file line number Diff line number Diff line change
Expand Up @@ -575,7 +575,7 @@ dictated by packet and time threshold mechanisms; see {{ack-loss-detection}}.

A Retry packet causes a client to send another Initial packet, effectively
restarting the connection process. A Retry packet indicates that the Initial
was received, but not processed. A Retry packet cannot be treated as an
was received, but not processed. A Retry packet MUST NOT be treated as an
acknowledgment.

Clients that receive a Retry packet reset congestion control and loss recovery
Expand Down