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

A gap is not reliable delivery

02

Sequence numbers help detect missing packets but RTP does not guarantee their retransmission or arrival.

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 gap is not reliable deliverySequence numbers help detect missing packets but RTP does not guarantee their retransmission or arrival. Current state: Playout policy.A gap is not reliable delivery10111213not receivedreceiver playout policyRTP detects a gap; it does not guarantee retransmission.
03
Playout policy

The receiver must decide how to handle missing media.

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

RTP does not reserve resources or guarantee delivery.

  • RTP does not reserve resources or guarantee delivery.
  • Packets may be lost or reordered.
  • Recovery and playout policy depend on the application and additional mechanisms.
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 ↗