Merge pull request #4218 from quicwg/ianswett-noncompliant-acks

Excess ack_delay could be non-compiance
quicwg · Oct 15, 2020 · 1e6e346 · 1e6e346
2 parents 53a17e3 + e906bb6
commit 1e6e346
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/draft-ietf-quic-recovery.md b/draft-ietf-quic-recovery.md
@@ -374,9 +374,9 @@ min_rtt.
 After the handshake is confirmed, any acknowledgement delays reported by the
 peer that are greater than the peer's max_ack_delay are attributed to
 unintentional but potentially repeating delays, such as scheduler latency at the
-peer or loss of previous acknowledgements. Therefore, these extra delays are
-considered effectively part of path delay and incorporated into the RTT
-estimate.
+peer or loss of previous acknowledgements.  Excess delays could also be due to
+a non-compliant receiver.  Therefore, these extra delays are considered
+effectively part of path delay and incorporated into the RTT estimate.
 
 Therefore, when adjusting an RTT sample using peer-reported acknowledgement
 delays, an endpoint: