@@ -223,15 +223,16 @@ and implementers are encouraged to explore this space.
223223
224224# ## Early Retransmit
225225
226- Unacknowledged packets close to the tail may have fewer than kReorderingThreshold
227- congestion-controlled packets sent after them.
228- Loss of such packets cannot be detected via Fast Retransmit. To enable ack-based loss
229- detection of such packets, receipt of an acknowledgment for the last outstanding
230- congestion-controlled packet triggers the Early Retransmit process, as follows.
231-
232- If there are unacknowledged congestion-controlled packets still pending, they should
233- be marked as lost. To compensate for the reduced reordering resilience, the sender
234- SHOULD set an alarm for a small period of time. If the unacknowledged
226+ Unacknowledged packets close to the tail may have fewer than
227+ kReorderingThreshold congestion-controlled packets sent after them.
228+ Loss of such packets cannot be detected via Fast Retransmit. To enable
229+ ack-based loss detection of such packets, receipt of an acknowledgment for the
230+ last outstanding congestion-controlled packet triggers the Early Retransmit
231+ process, as follows.
232+
233+ If there are unacknowledged congestion-controlled packets still pending, they
234+ should be marked as lost. To compensate for the reduced reordering resilience, the
235+ sender SHOULD set an alarm for a small period of time. If the unacknowledged
235236congestion-controlled packets are not acknowledged during this time, then these
236237packets MUST be marked as lost.
237238
0 commit comments