Re: [quicwg/base-drafts] Rework section on persistent congestion (#3961)

[Kazuho Oku <[e-mail]>]

@kazuho commented on this pull request.

Thank you for working on this. I think it is much better.

Q. Do you plan to have a separate PR for requiring RTT to be established on the far edge of the persistent congestion period?

> +
+This design uses an explicit duration instead of consecutive PTO events since
+the PTO timer is restarted every time an ack-eliciting packet is sent. An
+application that trickles data restarts the PTO timer repeatedly, preventing the
+PTO timer from expiring for a potentially long period of time. A consequence of
+this design is that persistent congestion can be established without the
+occurrence of any PTOs.
+
+### Declaring Persistent Congestion
+
+A sender declares persistent congestion on receiving an acknowledgement, if the
+following conditions are true:
+
+* there are at least two ack-eliciting packets that are declared lost;
+
+* the duration between the send times of these two packets exceeds the

```suggestion
* the duration between the send times of these packets exceeds the
```

"two" was a bit confusing for me, because the previous sentence talks about "at least two."

-- 
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/3961#pullrequestreview-456297996