RFC 4588: RTP Retransmission Payload Format
In plain English — editorial summary, not part of the RFC
RTP retransmission is an effective packet loss recovery technique for real-time applications with relaxed delay bounds. This document describes an RTP payload format for performing retransmissions. Retransmitted RTP packets are sent in a separate stream from the original RTP stream. It is assumed that feedback from receivers to senders is available. In particular, it is assumed that Real-time Transport Control Protocol (RTCP) feedback as defined in the extended RTP profile for RTCP-based feedback (denoted RTP/AVPF) is available in this memo. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4588
- Published
- July 2006
- Authors
- J. Rey; D. Leon; A. Miyazaki; V. Varsa; R. Hakenberg
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 35
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3556Session Description Protocol (SDP) Bandwidth Modifiers for RTP Control Protocol (RTCP) BandwidthCurrent
July 2003
- RFC 4573MIME Type Registration for RTP Payload Format for H.224Current
July 2006
- RFC 4184RTP Payload Format for AC-3 AudioCurrent
October 2005
- RFC 4175RTP Payload Format for Uncompressed VideoUpdated
September 2005
- RFC 3640RTP Payload Format for Transport of MPEG-4 Elementary StreamsUpdated
December 2003
- RFC 3611RTP Control Protocol Extended Reports (RTCP XR)Current
November 2003
- RFC 3558RTP Payload Format for Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)Updated
July 2003
- RFC 3557RTP Payload Format for European Telecommunications Standards Institute (ETSI) European Standard ES 201 108 Distributed Speech Recognition EncodingCurrent
July 2003
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?