You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems (to me) to be a fencepost error in the discussion about Setting the Reordering Threshold value. I think that the Reordering Threshold value should be set to the same value as RFC 9000's kPacketThreshold.
Example: Loss detection with kPacketThreshold set to 3 would perfectly catch the reported missing packets in the Table 1 example. Please check the pseudocode in A.10 of RFC 9002, where the condition for declaring a packet as lost is:
There seems (to me) to be a fencepost error in the discussion about Setting the Reordering Threshold value. I think that the
Reordering Threshold
value should be set to the same value as RFC 9000'skPacketThreshold
.Example: Loss detection with kPacketThreshold set to 3 would perfectly catch the reported missing packets in the Table 1 example. Please check the pseudocode in A.10 of RFC 9002, where the condition for declaring a packet as lost is:
See also the quicdev Slack message: https://quicdev.slack.com/archives/CTDAH4H71/p1725959899164449
The text was updated successfully, but these errors were encountered: