Re: [quicwg/base-drafts] Editorial recovery fixes (#1551)

[janaiyengar <[e-mail]>]

janaiyengar commented on this pull request.



> +the acknowledgement indicates that a later packet was received, while the
+reordering threshold provides some tolerance for reordering of packets in the
+network.
+
+The RECOMMENDED initial value for kReorderingThreshold is 3, based on
+TCP loss recovery {{?RFC5681}} {{?RFC6675}}. Some networks may exhibit higher
+degrees of reordering, causing a sender to detect spurious losses. Spuriously
+declaring packets lost leads to unnecessary retransmissions and may result in
+degraded performance due to the actions of the congestion controller upon
+detecting loss. Implementers MAY use algorithms developed for TCP, such as
+TCP-NCR {{?RFC4653}}, to improve QUIC's reordering resilience.
+
+QUIC implementations may use time-based loss detection to deal with reordering.
+time-based loss detection allows a certain amount of reordering above
+max(SRTT, latest_rtt).  The RECOMMENDED reordering tolerance is
+1/8 max(SRTT, latest_rtt).

This should be reworded. How about: "QUIC implementations can use time-based loss detection to handle reordering based on time elapsed since the packet was sent, instead of a packet reordering threshold. The RECOMMENDED time threshold, expressed as a fraction of the round-trip time (kTimeReorderingFraction), is 1/8." (The details of SRTT, etc are in the algo below, so I think being generic is ok here.)

-- 
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/1551#pullrequestreview-137249484