RTP Control Protocol: Difference between revisions

Revision as of 00:58, 29 April 2021

Revision as of 01:45, 29 April 2021

Line 2:

{{short description|Sister protocol of the Real-time Transport Protocol that provides control information}}

<ref>{{Cite journal|last=Henderson|first=Yoko O.|last2=Nalloor|first2=Rebecca|last3=Vazdarjanova|first3=Almira|last4=Murphy|first4=Anne Z.|last5=Parent|first5=Marise B.|date=2017-05|title=Sex-dependent effects of early life inflammatory pain on sucrose intake and sucrose-associated hippocampal Arc expression in adult rats|url=http://dx.doi.org/10.1016/j.physbeh.2017.01.025|journal=Physiology & Behavior|volume=173|pages=1–8|doi=10.1016/j.physbeh.2017.01.025|issn=0031-9384}}</ref>The '''RTP Control Protocol''' ('''RTCP''') is a sister protocol of the [[Real-time Transport Protocol]] (RTP). Its basic functionality and packet structure is defined in RFC 3550. RTCP provides [[Out-of-band signaling|out-of-band]] statistics and control information for an RTP session. It partners with RTP in the delivery and packaging of multimedia data, but does not transport any media data itself.

The primary function of RTCP is to provide feedback on the [[quality of service]] (QoS) in media distribution by periodically sending statistics information such as transmitted [[Octet (computing)|octet]] and packet counts, [[packet loss]], [[packet delay variation]], and [[round-trip delay time]] to participants in a streaming multimedia session. An application may use this information to control quality of service parameters, perhaps by limiting flow, or using a different [[codec]].