§8.9.

SUBSCRIBE_ERROR

A publisher sends a SUBSCRIBE_ERROR control message in response to a failed SUBSCRIBE.

SUBSCRIBE_ERROR Message {
  Type (i) = 0x5,
  Length (16),
  Request ID (i),
  Error Code (i),
  Error Reason (Reason Phrase),
}
Figure 11: MOQT SUBSCRIBE_ERROR Message
  • Request ID: The Request ID of the SUBSCRIBE this message is replying to Section 8.7.

  • Error Code: Identifies an integer error code for subscription failure.

  • Error Reason: Provides the reason for subscription error. See Section 1.3.3.

The application SHOULD use a relevant error code in SUBSCRIBE_ERROR, as defined below:

Table 4
Code Reason
0x0 Internal Error
0x1 Unauthorized
0x2 Timeout
0x3 Not Supported
0x4 Track Does Not Exist
0x5 Invalid Range
0x10 Malformed Auth Token
0x12 Expired Auth Token
  • Internal Error - An implementation specific or generic error occurred.

  • Unauthorized - The subscriber is not authorized to subscribe to the given track.

  • Timeout - The subscription could not be completed before an implementation specific timeout. For example, a relay could not establish an upstream subscription within the timeout.

  • Not Supported - The endpoint does not support the SUBSCRIBE method.

  • Track Does Not Exist - The requested track is not available at the publisher.

  • Invalid Range - The end of the SUBSCRIBE range is earlier than the beginning, or the end of the range has already been published.

  • Malformed Auth Token - Invalid Auth Token serialization during registration (see Section 8.2.1.1).

  • Expired Auth Token - Authorization token has expired Section 8.2.1.1).

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