RFC 6990: RTP Control Protocol (RTCP) Extended Report (XR) Block for MPEG-2 Transport Stream (TS) Program Specific Information (PSI) Independent Decodability Statistics Metrics Reporting
In plain English — editorial summary, not part of the RFC
An MPEG-2 Transport Stream (TS) is a standard container format used in the transmission and storage of multimedia data. Unicast/ multicast MPEG-2 TS over RTP is widely deployed in IPTV systems. This document defines an RTP Control Protocol (RTCP) Extended Report (XR) block that allows the reporting of MPEG-2 TS decodability statistics metrics related to transmissions of MPEG-2 TS over RTP. The metrics specified in the RTCP XR block are not dependent on Program Specific Information (PSI) carried in MPEG-2 TS.
Document record
- Document ID
- RFC6990
- Published
- August 2013
- Authors
- R. Huang; Q. Wu; H. Asaeda; G. Zorn
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7097RTP Control Protocol (RTCP) Extended Report (XR) for RLE of Discarded PacketsCurrent
January 2014
- RFC 6849An Extension to the Session Description Protocol (SDP) and Real-time Transport Protocol (RTP) for Media LoopbackCurrent
February 2013
- RFC 7728RTP Stream Pause and ResumeCurrent
February 2016
- RFC 7825A Network Address Translator (NAT) Traversal Mechanism for Media Controlled by the Real-Time Streaming Protocol (RTSP)Current
December 2016
- RFC 8858Indicating Exclusive Support of RTP and RTP Control Protocol (RTCP) Multiplexing Using the Session Description Protocol (SDP)Current
January 2021
- RFC 3605Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)Current
October 2003
- RFC 7272Inter-Destination Media Synchronization (IDMS) Using the RTP Control Protocol (RTCP)Current
June 2014
- RFC 6404Session PEERing for Multimedia INTerconnect (SPEERMINT) Security Threats and Suggested CountermeasuresCurrent
November 2011
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?