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

additional ack blocks limitation requirement #357

Open
hhrsscc opened this issue Oct 18, 2024 · 2 comments
Open

additional ack blocks limitation requirement #357

hhrsscc opened this issue Oct 18, 2024 · 2 comments

Comments

@hhrsscc
Copy link

hhrsscc commented Oct 18, 2024

When using QUIC datagrams, there is no retransmission mechanism, so in networks with packet loss, the number of ACK blocks continues to grow. This can result in an ACK frame size exceeding 1000 bytes, which is too large. Is it possible to introduce a setting that limits the maximum number of additional ACK blocks?

@mjoras
Copy link
Contributor

mjoras commented Oct 18, 2024

We don't have a way to do that but it wouldn't be that hard to add. Is this something you've observed using mvfst?

@hhrsscc
Copy link
Author

hhrsscc commented Oct 18, 2024

I’m using mvfst to send and receive QUIC datagrams, with each datagram being very small (less than 100 bytes). However, in networks with packet loss, the ACK frames consume too much bandwidth compared to the application data. Therefore, I’d like to have a limit on the number of ACK blocks.

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

No branches or pull requests

2 participants