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

Add MTU vs. extra packet considerations for Acknowledgements when using datagrams #85

Closed
mengelbart opened this issue May 11, 2023 · 2 comments · Fixed by #102
Closed
Assignees

Comments

@mengelbart
Copy link
Owner

QUIC acknowledgment frames can be sent in the same packet as stream or datagram frames, which adds overhead and reduces the maximum size of datagram frames. If a packetizer is configured to produce packets at a fixed maximum MTU, the sender may need to send many extra QUIC packets for acknowledgments. It may be helpful to reference the acknowledgment frequency draft, which could help to reduce the overhead somewhat.

Maybe relevant: https://www.rfc-editor.org/rfc/rfc9000#section-13

@SpencerDawkins
Copy link
Collaborator

The fundamental problem this issue is pointing to, is that the RTP sender (and receiver) does not have visibility to non-data frames that a QUIC sender may include in an outgoing QUIC packet. So, not just QUIC ACKs. We can provide a description of the trade-offs in the document now, but we probably can't make specific recommendations ("do this, not that") in the document, at least not yet.

@SpencerDawkins
Copy link
Collaborator

If we find that we are able to make specific recommendations, these recommendations may be added under a follow-up issue.

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

Successfully merging a pull request may close this issue.

2 participants