RFC 7509: RTP Control Protocol (RTCP) Extended Report (XR) for Post-Repair Loss Count Metrics
In plain English — editorial summary, not part of the RFC
This document defines an RTP Control Protocol (RTCP) Extended Report (XR) block that allows reporting of a post-repair loss count metric for a range of RTP applications. In addition, another metric, repaired loss count, is also introduced in this report block for calculating the pre-repair loss count when needed, so that the RTP sender or a third-party entity is able to evaluate the effectiveness of the repair methods used by the system.
Document record
- Document ID
- RFC7509
- Published
- May 2015
- Authors
- R. Huang; V. Singh
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 11
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7505A "Null MX" No Service Resource Record for Domains That Accept No MailCurrent
June 2015
- RFC 7529Non-Gregorian Recurrence Rules in the Internet Calendaring and Scheduling Core Object Specification (iCalendar)Current
May 2015
- RFC 7564PRECIS Framework: Preparation, Enforcement, and Comparison of Internationalized Strings in Application ProtocolsObsoleted
May 2015
- RFC 7565The 'acct' URI SchemeCurrent
May 2015
- RFC 7451Extension Registry for the Extensible Provisioning ProtocolCurrent
February 2015
- RFC 7572Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Instant MessagingCurrent
June 2015
- RFC 7573Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): One-to-One Text Chat SessionsCurrent
June 2015
- RFC 7578Returning Values from Forms: multipart/form-dataCurrent
July 2015
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?