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

Clarify text on pacing #3667

Closed
wants to merge 3 commits into from
Closed
Changes from all commits
Commits
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
10 changes: 4 additions & 6 deletions draft-ietf-quic-recovery.md
Expand Up @@ -908,12 +908,10 @@ Or, expressed as an inter-packet interval:
interval = smoothed_rtt * packet_size / congestion_window / N
~~~

Using a value for `N` that is small, but at least 1 (for example, 1.25) ensures
that variations in round-trip time don't result in under-utilization of the
congestion window. Values of 'N' larger than 1 ultimately result in sending
packets as acknowledgments are received rather than when timers fire, provided
the congestion window is fully utilized and acknowledgments arrive at regular
intervals.
Using a value for N that is low, but at least 1 (for example, 1.25) ensures that
variations in round-trip time don't result in under-utilization of the
congestion window. Note that a higher N results in the inter-packet interval
becoming smaller, and a large enough N defeats the purpose of pacing.
ianswett marked this conversation as resolved.
Show resolved Hide resolved

Practical considerations, such as packetization, scheduling delays, and
computational efficiency, can cause a sender to deviate from this rate over time
Expand Down