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

Document TCP RTO vs QUIC PTO #3441

Merged
merged 21 commits into from
Mar 10, 2020
Merged
Changes from 1 commit
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
10 changes: 5 additions & 5 deletions draft-ietf-quic-recovery.md
Original file line number Diff line number Diff line change
Expand Up @@ -230,11 +230,11 @@ more accurate round-trip time estimate (see Section 13.2 of {{QUIC-TRANSPORT}}).

### Probe Timeout Replaces RTO and TLP

QUIC uses a probe timeout (see {{pto}}), with a timer based on TCP's
RTO period computation. QUIC's PTO period includes the peer's maximum expected acknowledgement delay (max_ack_delay, Section XX),
instead of using a fixed minimum period. Unlike TCP, which collapses
the congestion window upon expiry of an RTO, QUIC does not change the congestion window
and instead sends probe packets whenever the timer expires. This is
QUIC uses a probe timeout (see {{pto}}), with a timer based on TCP's RTO
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RTO abbreviation is spelled out in a later chapter, but it would be helpful to state what RTO means. To a lesser extend this also applies to the section where PTO is defined because RTO is mentioned, but there is comes with a TCP doc reference and is not needed for understanding PTO.

computation. QUIC's PTO includes the peer's maximum expected acknowledgement
delay instead of using a fixed minimum timeout. Unlike TCP, which collapses
the congestion window upon expiry of an RTO, QUIC does not change the congestion
window and instead sends probe packets whenever the timer expires. This is
similar to TCP with F-RTO, but it does allow more packets to be sent when the
congestion window was not fully utilized when the probe timeout expires. Though
ianswett marked this conversation as resolved.
Show resolved Hide resolved
this is slightly more aggressive than TCP RTO, it's less aggressive than if the
Expand Down