Visual RFC.
ALL RFCs / RFC 3550
Read the RFC ↗
RFC 3550 / MECHANISMS

Reports describe reception

04

RTCP reports communicate reception statistics alongside RTP media.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

DIAGRAM§ 6.4 ↗
RFC 3550 · § 6.4EXAMPLE
3 / 3
Reports describe receptionRTCP reports communicate reception statistics alongside RTP media. Current state: RTCP report.Reports describe receptionSenderReceiverRTP medialossjitterhighest sequenceRTCP reportsender feedbackRTCP timing controls bandwidth; it is not one ACK per packet.
03
RTCP report

Send the applicable report under RTCP timing rules.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
KEY POINT

A sender report includes an NTP timestamp and matching RTP timestamp.

  • A sender report includes an NTP timestamp and matching RTP timestamp.
  • Reception report blocks include loss and jitter statistics.
  • RTCP reporting is bandwidth controlled, not a feedback packet per media packet.
DETAILS

The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.

Read the RFC section ↗

Diagrams simplify the RFC. Read the linked sections for complete requirements.

Privacy
All chapters in this RFC
  1. A media packet has two clocks
  2. A gap is not reliable delivery
  3. Arrival jitter is measurable
  4. Reports describe reception
  5. Synchronize related media

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗