RFC 6843: RTP Control Protocol (RTCP) Extended Report (XR) Block for Delay Metric Reporting
In plain English — editorial summary, not part of the RFC
This document defines an RTP Control Protocol (RTCP) Extended Report (XR) block that allows the reporting of delay metrics for use in a range of Real-time Transport Protocol (RTP) applications. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6843
- Published
- January 2013
- Authors
- A. Clark; K. Gross; Q. Wu
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6839Additional Media Type Structured Syntax SuffixesUpdated
January 2013
- RFC 6838Media Type Specifications and Registration ProceduresUpdated
January 2013
- RFC 6849An Extension to the Session Description Protocol (SDP) and Real-time Transport Protocol (RTP) for Media LoopbackCurrent
February 2013
- RFC 6828Content Splicing for RTP SessionsCurrent
January 2013
- RFC 6871Session Description Protocol (SDP) Media Capabilities NegotiationCurrent
February 2013
- RFC 6809Mechanism to Indicate Support of Features and Capabilities in the Session Initiation Protocol (SIP)Current
November 2012
- RFC 6878IANA Registry for the Session Initiation Protocol (SIP) "Priority" Header FieldCurrent
March 2013
- RFC 6881Best Current Practice for Communications Services in Support of Emergency CallingUpdated
March 2013
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?