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

Synchronize related media

05

Sender reports map each RTP clock to a shared wall-clock reference.

Related RFCs and changes

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

RFC 3550 · § 6.4.1EXAMPLE
3 / 3
Synchronize related mediaSender reports map each RTP clock to a shared wall-clock reference. Current state: Common identity.Synchronize related mediaaudio RTP clockvideo RTP clockSR mappingSR mappingCNAME associates the related sources
03
Common identity

Use the CNAME and mappings to align related streams.

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

Different media can use different RTP timestamp rates.

  • Different media can use different RTP timestamp rates.
  • An SR pairs an NTP timestamp with an RTP timestamp for one source.
  • A common CNAME helps associate related streams for synchronization.
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
RFC 9700 / CHAPTERS

Chapters

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

RFC status and corrections ↗