Skip to content

Commit c58974b

Browse files
authored
Comments
1 parent 6f644ac commit c58974b

File tree

1 file changed

+8
-9
lines changed

1 file changed

+8
-9
lines changed

draft-ietf-quic-recovery.md

Lines changed: 8 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -310,9 +310,9 @@ MaxAckDelay excludes ack delays that aren't included in an RTT sample because
310310
they're too large and excludes those which reference an ack-only packet.
311311

312312
QUIC diverges from TCP by calculating MaxAckDelay dynamically, instead of
313-
assuming a constant value for all connections. It includes this in all probe
314-
timeouts, because it assume the ack delay may come into play, regardless of
315-
the number of packets outstanding. TCP's TLP assumes if at least 2
313+
assuming a constant delayed ack timeout for all connections. QUIC includes
314+
this in all probe timeouts, because it assume the ack delay may come into play,
315+
regardless of the number of packets outstanding. TCP's TLP assumes if at least 2
316316
packets are outstanding, acks will not be delayed.
317317

318318
A PTO value of at least 1.5*SRTT ensures that the ACK is overdue. The 1.5
@@ -367,15 +367,14 @@ reducing the probability of consecutive RTO events.
367367

368368
QUIC's RTO algorithm differs from TCP in that the firing of an RTO alarm is not
369369
considered a strong enough signal of packet loss, so does not result in an
370-
immediate change to CWND or recovery state. An RTO alarm fires only when
371-
there's a prolonged period of network silence, which could be caused by a change
372-
in the underlying network RTT.
370+
immediate change to congestion window or recovery state. An RTO alarm fires only
371+
when there's a prolonged period of network silence, which could be caused by a
372+
change in the underlying network RTT.
373373

374374
QUIC also diverges from TCP by including MaxAckDelay in the RTO period. QUIC is
375375
able to explicitly model the ack delay via the ack delay field in the ack frame.
376-
Because QUIC is subtracting this delay from both SRTT and it is expected to
377-
reduce RTTVar, it is necessary to add it back, in order to compensate for
378-
the smaller SRTT and RTTVar.
376+
Since QUIC corrects for this delay in its SRTT and RTTVAR computations, it is
377+
necessary to add this delay explicitly in the RTO computation.
379378

380379
When an acknowledgment is received for a packet sent on an RTO event, any
381380
unacknowledged packets with lower packet numbers than those acknowledged MUST be

0 commit comments

Comments
 (0)