Re: [quicwg/base-drafts] Allow alternate restarts after idle (#2187)

[janaiyengar <[e-mail]>]

janaiyengar commented on this pull request.



> -idle depends upon whether pacing is used.
-
-If the sender uses pacing, the connection should limit the initial burst of
-packets to no more than the initial congestion window and subsequent packets
-SHOULD be paced. The congestion window does not change while the connection
-is idle.
-
-A sender that does not use pacing SHOULD reset its congestion window to the
-minimum of the current congestion window and the initial congestion window.
-This recommendation is based on Section 4.1 of {{?RFC5681}}.
+
+## Sending data after an idle period
+
+A sender is considered idle if it has no bytes in flight.  A sender can become
+idle when it is application limited and has no data to send, or when it marks
+packets as lost (and therefore not in flight).

The text that was there was probably leftover from a while ago... at any rate there is no PTO case. There is nothing marked as lost on a PTO, and bytes in flight does not change on a PTO (modulo the two packets that are sent in response).  So a sender cannot become idle on a PTO.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/2187#discussion_r242720105