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

Retry MUST NOT -> cannot be treated as an acknowledgement #3171

Merged
merged 4 commits into from
Oct 31, 2019
Merged

Retry MUST NOT -> cannot be treated as an acknowledgement #3171

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
e67136d
Retry MUST NOT -> cannot be treated as an acknowledgement
ianswett Oct 30, 2019
7923888
Martin's reason
ianswett Oct 30, 2019
b44efce
Update draft-ietf-quic-recovery.md
ianswett Oct 30, 2019
0e759f0
Update draft-ietf-quic-recovery.md
ianswett Oct 31, 2019
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
5 changes: 3 additions & 2 deletions draft-ietf-quic-recovery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -575,8 +575,9 @@ 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 MUST NOT be treated as an
acknowledgment.
was received, but not processed. A Retry packet cannot be treated as an
acknowledgment, because it does not indicate that a packet was processed or
specify the packet number.

Clients that receive a Retry packet reset congestion control and loss recovery
state, including resetting any pending timers. Other connection state, in
Expand Down