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

What to send on multiple PTOs #2380

Merged
merged 2 commits into from Jan 29, 2019
Merged

What to send on multiple PTOs #2380

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8c452d6
What to send on multiple PTOs
ianswett Jan 28, 2019
04bc4d7
Update draft-ietf-quic-recovery.md
ianswett Jan 28, 2019
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
6 changes: 6 additions & 0 deletions draft-ietf-quic-recovery.md
View file
Open in desktop
Expand Up @@ -535,6 +535,12 @@ MAY use alternate strategies for determining the content of probe packets,
including sending new or retransmitted data based on the application's
priorities.

When the PTO timer expires multiple times and new data cannot be sent,
implementations must choose between sending the same payload every time
or sending different payloads. Sending the same payload may be simpler
and ensures the highest priority frames arrive first. Sending different
payloads each time reduces the chances of spurious retransmission.

When a PTO timer expires, new or previously-sent data may not be available to
send and packets may still be in flight. A sender can be blocked from sending
new data in the future if packets are left in flight. Under these conditions, a
Expand Down