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

Fix nits in recovery draft #1700

Merged
merged 1 commit into from Aug 24, 2018
Merged

Fix nits in recovery draft #1700

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.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions draft-ietf-quic-recovery.md
View file
Open in desktop
Expand Up @@ -490,7 +490,7 @@ caused by losing previously sent ACK frames, at the cost of larger ACK frames.
ACK frames SHOULD always acknowledge the most recently received packets, and the
more out-of-order the packets are, the more important it is to send an updated
ACK frame quickly, to prevent the peer from declaring a packet as lost and
spuriusly retransmitting the frames it contains.
spuriously retransmitting the frames it contains.

Below is one recommended approach for determining what packets to include in an
ACK frame.
Expand Down Expand Up @@ -764,7 +764,7 @@ Pseudocode for OnPacketAcked follows:
if (rto_count > 0 &&
acked_packet.packet_number > largest_sent_before_rto):
OnRetransmissionTimeoutVerified(
acket_packet.packet_number)
acked_packet.packet_number)
handshake_count = 0
tlp_count = 0
rto_count = 0
Expand Down