Glossary
D
Data channel
A data channel is a "pipe" to send and receive random blobs of bytes.
L
Local media track
A local media track is a media track whose source is local to the peer connection, that is which has a local frame-producing media track source. In other words the track is a sender track, which produce frames to be sent to the remote peer.
See also
M
Media
The term media refers to either or both of audio and video. It does not include data channels.
Media track
A media track is a slim entity which bridges a media track source with a transceiver.
See also
Media track source
A media track source is an entity producing some media frames. Those frames are made available to one or more media tracks. The source itself is a standalone object not associated with any particular peer connection, and therefore can be used with multiple tracks from multiple peer connections at the same time.
See also
P
Peer connection
The peer connection is the main entity of WebRTC. It manages a connection to a single remote peer. The peer connection contains a collection of transceivers, which describe which media is sent to and received from the remote peer, as well as a collection of data channels, both of which can be empty.
See also
R
Remote media track
A remote media track is a media track whose source is remote to the peer connection, that is which receives its frame from the remote peer; this is a receiver track.
See also
T
Transceiver
A transceiver is a "pipe" for transporting some media between two peers. Each transceiver is owned by a specific peer connection, and describes how this media is encoded (audio or video codec type and options) and transported (transport options, like bandwidth).
A transceiver always has exactly one local media track (sender) and one remote media track (receiver), both of which can be null. If null, the transceiver acts as if a dummy track existed which draws its media frames from a null source (black frames for video, silence for audio).