§13.6.

Timeouts

draft-19 draft-18 draft-17 draft-16 draft-15 draft-14 draft-13 draft-12 draft-11 draft-10 draft-09 draft-08 · View on IETF ↗

Implementations are advised to use timeouts to prevent resource exhaustion attacks by a peer that does not send expected data within an expected time. Each implementation is expected to set its own timeouts.

13.6.1. Idle Connection Handling

The transport connection (e.g., QUIC) underlying a MOQT session can close due to idle timeout if no data is exchanged, either because there are no established subscriptions or the established subscriptions are not publishing Objects frequently. This includes publisher sessions that have issued a PUBLISH_NAMESPACE and are waiting for subscribers.

Implementations that want to keep idle sessions open have several options:

  • Use transport-layer keep-alive mechanisms, such as QUIC PING frames, to prevent idle timeout closure.

  • Send periodic control messages, for example REQUEST_UPDATE with no modified Message Parameters.

  • Accept that idle connections can close and implement reconnection logic when needed.

The choice of mechanism is implementation-specific.

This is one section of the MoQT specification, rendered per-section for quick reference and citation. The authoritative text is draft-ietf-moq-transport-19 at the IETF.

All draft-19 sections What is MoQT? Debug MoQT with moqtap