MOQT uses a single bidirectional stream to exchange control messages, as defined in Section 3.3. Every single message on the control stream is formatted as follows:
MOQT Control Message {
Message Type (i),
Message Length (16),
Message Payload (..),
}
The following Message Types are defined:
| ID | Messages |
|---|---|
| 0x01 | RESERVED (SETUP for version 00) |
| 0x40 | RESERVED (CLIENT_SETUP for versions <= 10) |
| 0x41 | RESERVED (SERVER_SETUP for versions <= 10) |
| 0x20 | CLIENT_SETUP (Section 8.3) |
| 0x21 | SERVER_SETUP (Section 8.3) |
| 0x10 | GOAWAY (Section 8.4) |
| 0x15 | MAX_REQUEST_ID (Section 8.5) |
| 0x1A | REQUESTS_BLOCKED (Section 8.6) |
| 0x3 | SUBSCRIBE (Section 8.7) |
| 0x4 | SUBSCRIBE_OK (Section 8.8) |
| 0x5 | SUBSCRIBE_ERROR (Section 8.9) |
| 0x2 | SUBSCRIBE_UPDATE (Section 8.10) |
| 0xA | UNSUBSCRIBE (Section 8.11) |
| 0xB | SUBSCRIBE_DONE (Section 8.12) |
| 0x1D | PUBLISH (Section 8.13) |
| 0x1E | PUBLISH_OK (Section 8.14) |
| 0x1F | PUBLISH_ERROR (Section 8.15) |
| 0x16 | FETCH (Section 8.16) |
| 0x18 | FETCH_OK (Section 8.17) |
| 0x19 | FETCH_ERROR (Section 8.18) |
| 0x17 | FETCH_CANCEL (Section 8.19) |
| 0xD | TRACK_STATUS_REQUEST (Section 8.20) |
| 0xE | TRACK_STATUS (Section 8.21) |
| 0x6 | ANNOUNCE (Section 8.22) |
| 0x7 | ANNOUNCE_OK (Section 8.23) |
| 0x8 | ANNOUNCE_ERROR (Section 8.24) |
| 0x9 | UNANNOUNCE (Section 8.25) |
| 0xC | ANNOUNCE_CANCEL (Section 8.26) |
| 0x11 | SUBSCRIBE_ANNOUNCES (Section 8.27) |
| 0x12 | SUBSCRIBE_ANNOUNCES_OK (Section 8.28) |
| 0x13 | SUBSCRIBE_ANNOUNCES_ERROR (Section 8.29 |
| 0x14 | UNSUBSCRIBE_ANNOUNCES (Section 8.30) |
An endpoint that receives an unknown message type MUST close the session. Control messages have a length to make parsing easier, but no control messages are intended to be ignored. The length is set to the number of bytes in Message Payload, which is defined by each message type. If the length does not match the length of the Message Payload, the receiver MUST close the session with Protocol Violation.