Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider dynamic hybrid between time-based and packet-based loss detection #1986

Closed
maolson-msft opened this issue Nov 10, 2018 · 3 comments
Closed
Assignees
Labels
-recovery design An issue that affects the design of the protocol; resolution requires consensus.

Comments

@maolson-msft
Copy link

The IETF RACK/TLP draft for TCP has a dynamic hybrid of RACK ("time-based") and dupthresh ("packet-based") recovery: dupthresh is used at first, but then turned off when any reordering is detected. The idea being that a packet-based threshold is too sensitive on networks with moderate reordering. It would be easy to adapt this to QUIC.

Along with the dynamic time-based reordering threshold that is a MAY in the QUIC spec right now iirc, this would go under the general heading of "reordering tolerance." The main dissent I've heard is that we shouldn't ship code that tolerates reordering because it might incentivize use of technologies that introduce reordering. Link bonding, for instance, can introduce such reordering supposedly, although that's a bit surprising since you could just hash tuples to NICs. Anyway, that's the narrative.

@martinthomson martinthomson added design An issue that affects the design of the protocol; resolution requires consensus. -recovery labels Nov 12, 2018
@ianswett ianswett self-assigned this Nov 20, 2018
@mnot mnot added this to Recovery in Transport / Recovery / TLS Jan 10, 2019
@ianswett
Copy link
Contributor

Now that the draft has moved to PTO from TLP/RTO, if you'd like to make a specific proposal, it'd be a good time.

@janaiyengar
Copy link
Contributor

@maolson-msft : Would you like to propose a PR?

@maolson-msft
Copy link
Author

Hi, sorry for letting this issue sit. Adding dynamic reordering tolerance is far from noncontroversial, so I'll close this for now. Maybe we can consider it in the next version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
-recovery design An issue that affects the design of the protocol; resolution requires consensus.
Projects
No open projects
Development

No branches or pull requests

4 participants