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

A media packet has two clocks

01

The sequence number orders packets; the timestamp locates media in its sampling timeline.

Related RFCs and changes

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

DIAGRAM§ 5.1 ↗
RFC 3550 · § 5.1EXAMPLE
3 / 3
A media packet has two clocksThe sequence number orders packets; the timestamp locates media in its sampling timeline. Current state: SSRC.A media packet has two clocksseq: 17timestamp: 9000SSRC: Amedia timesource AidentityHeader field widths are schematic.
03
SSRC

Associate the packet with a synchronization source.

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
WHAT CHANGED
RFC 1889RFC 3550 Appendix B

RFC 3550 revises the earlier RTP specification, including more scalable RTCP timing and expanded implementation guidance.

Read the updated RFC section ↗
KEY POINT

The sequence number increments for every RTP data packet.

  • The sequence number increments for every RTP data packet.
  • The timestamp represents the sampling instant of the first payload octet.
  • The SSRC identifies the synchronization source within a session.
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 ↗