A track is a sequence of groups (Section 2.3). It is the entity against which a subscriber issues a subscription request. A subscriber can request to receive individual tracks starting at a group boundary, including any new objects pushed by the publisher while the track is active.
2.4.1. Track Naming
In MOQT, every track is identified by a Full Track Name, consisting of a Track Namespace and a Track Name.
Track Namespace is an ordered set of between 0 and 32 Track Namespace Fields, encoded as described in Section 8.7.
The structured nature of Track Namespace allows relays and applications to manipulate prefixes of a namespace.
Track Name is a sequence of bytes, possibly empty, that identifies an individual track within the namespace.
In this specification, both the Track Namespace Fields and the Track Name are not constrained to a specific encoding. They carry a sequence of bytes and comparison between two Track Namespace Fields or Track Names is done by exact comparison of the bytes. Specifications that use MOQT may constrain the information in these fields, for example by restricting them to UTF-8. Any such specification needs to specify the canonicalization into the bytes in the Track Namespace Fields or Track Name such that exact comparison works.
2.4.2. Reserved Namespaces
MOQT reserves all Track Namespace values whose first tuple field begins with
a period (0x2e, .). These namespaces MUST NOT be used unless their meaning
is defined through IANA registration. Unless otherwise specified, an
endpoint that receives a request for an unrecognized reserved namespace MUST
pass it to the Application, so that future extensions can define new reserved
namespaces without breaking older implementations.
A Track Namespace whose first field is exactly . (a single period, 0x2e)
is reserved and MUST NOT be used for any purpose; endpoints MUST NOT publish
tracks or namespaces under it and MUST reject requests referencing it with
DOES_NOT_EXIST.