RTCP: Difference between revisions

From MultimediaWiki
Jump to navigation Jump to search
(copy RTCP info from the VLC wiki)
 
No edit summary
Line 2: Line 2:
It is based on the periodic transmission of control packets to all participants in the session, using the same distribution mechanism as the data packets. The underlying protocol must provide multiplexing of the data and control packets, for example using separate port numbers with UDP.
It is based on the periodic transmission of control packets to all participants in the session, using the same distribution mechanism as the data packets. The underlying protocol must provide multiplexing of the data and control packets, for example using separate port numbers with UDP.


RTCP provides feedback on the quality of the data distribution.
RTCP can provide feedback on the quality of the data distribution (QoS).
RTCP carries a persistent transport-level identifier for an RTP source called the canonical name or CNAME, which may be used to associate multiple data streams from a given participant in a set of related RTP sessions, for example to synchronize audio and video.
RTCP carries a persistent transport-level identifier for an RTP source called the canonical name or CNAME, which may be used to associate multiple data streams from a given participant in a set of related RTP sessions, for example to synchronize audio and video.


[[Category:Protocols]]
[[Category:Protocols]]

Revision as of 10:09, 9 March 2006

RTP Control Protocol (RTCP) is a sister protocol of the Real-time Transport Protocol (RTP). It is defined in RFC 3550. It is based on the periodic transmission of control packets to all participants in the session, using the same distribution mechanism as the data packets. The underlying protocol must provide multiplexing of the data and control packets, for example using separate port numbers with UDP.

RTCP can provide feedback on the quality of the data distribution (QoS). RTCP carries a persistent transport-level identifier for an RTP source called the canonical name or CNAME, which may be used to associate multiple data streams from a given participant in a set of related RTP sessions, for example to synchronize audio and video.