Live content requires significant bandwidth and resources. Failure to set limits will quickly cause resource exhaustion.
MOQT uses stream limits and flow control to impose resource limits at the network layer. Endpoints SHOULD set flow control limits based on the anticipated bitrate.
Endpoints MAY impose a MAX STREAM count limit which would restrict the number of concurrent streams which an application could have in flight.
The publisher prioritizes and transmits streams out of order. Streams might be starved indefinitely during congestion. The publisher and subscriber MUST cancel a stream, preferably the one with the lowest priority, after reaching a resource limit.
A larger MAX_CONTROL_MESSAGE_SIZE (Section 9.1.8) allows larger Parameters, such as Authorization Tokens, but an endpoint that buffers complete control messages commits that much memory per stream. Such an endpoint needs to grant enough flow control for a complete message on each stream, or the endpoints can deadlock.