tree 0c31993c208ffb35dd89d1f25d4079d583865366
parent d249e53db5364c7a67a8c51205f34e30f5562686
author vasilvv <vasilvv@google.com> 1724871693 -0700
committer Copybara-Service <copybara-worker@google.com> 1724871757 -0700

Introduce Object ACKs (OACKs) to MoQT.

OACKs let the application receiver acknowledge that it has received (and potentially processed) the object.  In addition to that, we also communicate how far off from the deadline the object was received.

The sender want to know this information if it is in a position to adjust the send rate:
- when it's a 1:1 connection and it controls the video bitrate,
- when it's doing sender-side ABR.

The reason we want to do MoQ-level ACKs is that the alternatives are not as good:
- using QUIC ACKs directly breaks layering and is infeasible with web APIs
- using a building up queue as a signal is possible, but the queue takes a time to build up, thus making it a delayed signal

PiperOrigin-RevId: 668549384