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

Reset connection state on retry and VN #2040

Merged
merged 2 commits into from
Nov 27, 2018
Merged
Changes from all commits
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
14 changes: 9 additions & 5 deletions draft-ietf-quic-recovery.md
Original file line number Diff line number Diff line change
Expand Up @@ -433,11 +433,15 @@ When crypto packets are outstanding, the TLP and RTO timers are not active.
#### Retry and Version Negotiation

A Retry or Version Negotiation packet causes a client to send another Initial
packet, effectively restarting the connection process.

Either packet indicates that the Initial was received but not processed.
Neither packet can be treated as an acknowledgment for the Initial, but they MAY
be used to improve the RTT estimate.
packet, effectively restarting the connection process and resetting congestion
control and loss recovery state, including resetting any pending timers. Either
packet indicates that the Initial was received but not processed. Neither
packet can be treated as an acknowledgment for the Initial.

The client MAY however compute an RTT estimate to the server as the time period
from when the first Initial was sent to when a Retry or a Version Negotiation
packet is received. The client MAY use this value to seed the RTT estimator for
a subsequent connection attempt to the server.

### Tail Loss Probe {#tlp}

Expand Down