RTP Control Protocol: Difference between revisions

Content deleted Content added
Monkbot (talk | contribs)
m Task 18 (cosmetic): eval 3 templates: hyphenate params (1×);
Packet header: Clarifying the length field in the header, and mentioning the so-called compound packets
Line 77:
!
! colspan="1" |32
| colspan="32" |SSRC identifier
|- align="center"
|}
 
* '''Version''': (2 bits) Identifies the version of RTP, which is the same in RTCP packets as in RTP data packets. The version defined by this specification is two (2).<ref name=RFC3550/>
* '''P (Padding)''': (1 bits) Used to indicateIndicates if there are extra padding bytes at the end of the RTP packet. Padding may be used to fill up a block of certain size, for example as required by an encryption algorithm. The last byte of the padding contains the number of padding bytes that were added (including itself).<ref name=RFC3550/>
* '''RC (Reception report count )''': (5 bits) The number of reception report blocks contained in this packet. A value of zero is valid.<ref name=RFC3550/>
* '''PT (Packet type) ''': (8 bits) Contains a constant to identify RTCP packet type.<ref name=RFC3550/>
* '''Length''': (16 bits) Indicates the length of this RTCP packet (including the header itself) in 32-bit units minus one.<ref name=RFC3550/>
* '''SSRC''': (32 bits) ''Synchronization source identifier'' uniquely identifies the source of a stream.<ref name=RFC3550/>
 
Note that multiple reports can be concatenated into a single compound RTCP packet, each with its own packet header.
 
==Message types==