Control Messages

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 (..),
}

Figure 3: MOQT Message

The following Message Types are defined:

Table 1
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 9.3)
0x21	SERVER_SETUP (Section 9.3)
0x10	GOAWAY (Section 9.4)
0x15	MAX_REQUEST_ID (Section 9.5)
0x1A	REQUESTS_BLOCKED (Section 9.6)
0x3	SUBSCRIBE (Section 9.7)
0x4	SUBSCRIBE_OK (Section 9.8)
0x5	SUBSCRIBE_ERROR (Section 9.9)
0x2	SUBSCRIBE_UPDATE (Section 9.10)
0xA	UNSUBSCRIBE (Section 9.11)
0xB	PUBLISH_DONE (Section 9.12)
0x1D	PUBLISH (Section 9.13)
0x1E	PUBLISH_OK (Section 9.14)
0x1F	PUBLISH_ERROR (Section 9.15)
0x16	FETCH (Section 9.16)
0x18	FETCH_OK (Section 9.17)
0x19	FETCH_ERROR (Section 9.18)
0x17	FETCH_CANCEL (Section 9.19)
0xD	TRACK_STATUS (Section 9.20)
0xE	TRACK_STATUS_OK (Section 9.21
0xF	TRACK_STATUS_ERROR (Section 9.22)
0x6	PUBLISH_NAMESPACE (Section 9.23)
0x7	PUBLISH_NAMESPACE_OK (Section 9.24)
0x8	PUBLISH_NAMESPACE_ERROR (Section 9.25)
0x9	PUBLISH_NAMESPACE_DONE (Section 9.26)
0xC	PUBLISH_NAMESPACE_CANCEL (Section 9.27)
0x11	SUBSCRIBE_NAMESPACE (Section 9.28)
0x12	SUBSCRIBE_NAMESPACE_OK (Section 9.29)
0x13	SUBSCRIBE_NAMESPACE_ERROR (Section 9.30
0x14	UNSUBSCRIBE_NAMESPACE (Section 9.31)

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.

Sections