RFC 5725: Post-Repair Loss RLE Report Block Type for RTP Control Protocol (RTCP) Extended Reports (XRs)
In plain English — editorial summary, not part of the RFC
This document defines a new report block type within the framework of RTP Control Protocol (RTCP) Extended Reports (XRs). One of the initial XR report block types is the Loss Run Length Encoding (RLE) Report Block. This report conveys information regarding the individual Real-time Transport Protocol (RTP) packet receipt and loss events experienced during the RTCP interval preceding the transmission of the report. The new report, which is referred to as the Post-repair Loss RLE report, carries information regarding the packets that remain lost after all loss-repair methods are applied. By comparing the RTP packet receipts/losses before and after the loss repair is completed, one can determine the effectiveness of the loss- repair methods in an aggregated fashion. This document also defines the signaling of the Post-repair Loss RLE report in the Session Description Protocol (SDP). [STANDARDS-TRACK]
Document record
- Document ID
- RFC5725
- Published
- February 2010
- Authors
- A. Begen; D. Hsu; M. Lague
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5956Forward Error Correction Grouping Semantics in the Session Description ProtocolCurrent
September 2010
- RFC 6015RTP Payload Format for 1-D Interleaved Parity Forward Error Correction (FEC)Current
October 2010
- RFC 6659Considerations for Deploying the Rapid Acquisition of Multicast RTP Sessions (RAMS) MethodCurrent
July 2012
- RFC 5109RTP Payload Format for Generic Forward Error CorrectionCurrent
December 2007
- RFC 2733An RTP Payload Format for Generic Forward Error CorrectionObsoleted
December 1999
- RFC 5775Asynchronous Layered Coding (ALC) Protocol InstantiationCurrent
April 2010
- RFC 5651Layered Coding Transport (LCT) Building BlockCurrent
October 2009
- RFC 5576Source-Specific Media Attributes in the Session Description Protocol (SDP)Current
June 2009
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?