The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.
The following terms are used with the first letter capitalized.
- Application:
-
The entity using MOQT to transmit and receive data.
- Client:
-
The party initiating a Transport Session.
- Server:
-
The party accepting an incoming Transport Session.
- Endpoint:
-
A Client or Server.
- Peer:
-
The other endpoint than the one being described
- Publisher:
-
An endpoint that handles subscriptions by sending requested Objects from the requested track.
- Subscriber:
-
An endpoint that subscribes to and receives tracks.
- Original Publisher:
-
The initial publisher of a given track.
- End Subscriber:
-
A subscriber that initiates a subscription and does not send the data on to other subscribers.
- Relay:
-
An entity that is both a Publisher and a Subscriber, but not the Original Publisher or End Subscriber.
- Upstream:
-
In the direction of the Original Publisher
- Downstream:
-
In the direction of the End Subscriber(s)
- Transport Session:
-
A raw QUIC connection or a WebTransport session.
- Stream:
-
A bidirectional or unidirectional bytestream provided by the QUIC transport or WebTransport.
- Congestion:
-
Packet loss and queuing caused by degraded or overloaded networks.
- Group:
-
A temporal sequence of objects. A group represents a join point in a track. See (Section 2.3).
- Object:
-
An object is an addressable unit whose payload is a sequence of bytes. Objects form the base element in the MOQT data model. See (Section 2.1).
- Track:
-
A track is a collection of groups. See (Section 2.4).