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

Add section number to reference #2525

Merged
merged 1 commit into from
Mar 16, 2019
Merged

Add section number to reference #2525

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
9 changes: 5 additions & 4 deletions draft-ietf-quic-recovery.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -423,10 +423,11 @@ Upon timeout, the sender MUST retransmit all unacknowledged CRYPTO data if
possible.

Until the server has validated the client's address on the path, the amount of
data it can send is limited, as specified in {{QUIC-TRANSPORT}}. If not all
unacknowledged CRYPTO data can be sent, then all unacknowledged CRYPTO data sent
in Initial packets should be retransmitted. If no data can be sent, then no
alarm should be armed until data has been received from the client.
data it can send is limited, as specified in Section 8.1 of {{QUIC-TRANSPORT}}.
If not all unacknowledged CRYPTO data can be sent, then all unacknowledged
CRYPTO data sent in Initial packets should be retransmitted. If no data can be
sent, then no alarm should be armed until data has been received from the
client.

Because the server could be blocked until more packets are received, the client
MUST start the crypto retransmission timer even if there is no unacknowledged
Expand Down