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

Do we need ack frequency control per path? #77

Open
yfmascgy opened this issue Nov 6, 2021 · 4 comments
Open

Do we need ack frequency control per path? #77

yfmascgy opened this issue Nov 6, 2021 · 4 comments

Comments

@yfmascgy
Copy link
Contributor

yfmascgy commented Nov 6, 2021

In our testing, one thing worth noticing is that for different sim cards, the uplink/downlink ratio can be quite different. For example, with a China Mobile 4G card, we measured a downlink at 35Mbps and an uplink at 3Mbps, while with a China Telecom 4G card, we measured a downlink at 45Mbps and an uplink at 23Mbps at the same time in the same spot.

If we want to measure RTT more precisely, we let ACK return from the same path. However, because some sim cards are more asymmetrical than the others, it introduced a question, do we want ack frequency control per path?

In the QUIC ack-frequency draft, one of the motivations is to handle link asymmetry such that the link throughput won't be constraint by ack packets in the reverse direction. My understanding is that some 5G IoT cards can be more asymmetrical, so do we want to add a mechanism to address this issue? What do you think?

@mirjak
Copy link
Collaborator

mirjak commented Jan 11, 2022

I think this is likely rather a separate extension. There are actually two questions here: 1) the per-path ack frequency and 2) guidance on which path to use for acks.

@qdeconinck
Copy link
Contributor

I think that 1) should be an extension of the draft-ietf-quic-ack-frequency. 2) probably deserves some further discussion in the current draft (maybe track this in #33?).

@mirjak
Copy link
Collaborator

mirjak commented Jan 11, 2022

Might be best to open a new separate issue on guidance for sending acks.

@mirjak
Copy link
Collaborator

mirjak commented Jul 6, 2022

opened issue #123 now for ACK guidance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants