§9.19.

TRACK_STATUS

A potential subscriber sends a TRACK_STATUS message on the control stream to obtain information about the current status of a given track.

The TRACK_STATUS message format is identical to the SUBSCRIBE message (Section 9.9).

The receiver of a TRACK_STATUS message treats it identically as if it had received a SUBSCRIBE message, except it does not create downstream subscription state or send any Objects. If successful, the publisher responds with a REQUEST_OK message with the same parameters it would have set in a SUBSCRIBE_OK. Track Alias is not used. A publisher responds to a failed TRACK_STATUS with an appropriate REQUEST_ERROR message.

Relays without an Established subscription MAY forward TRACK_STATUS to one or more publishers, or MAY initiate a subscription (subject to authorization) as described in Section 8.5 to determine the response. The publisher does not send PUBLISH_DONE for this request, and the subscriber cannot send SUBSCRIBE_UPDATE or UNSUBSCRIBE.

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