RFC 8082: Using Codec Control Messages in the RTP Audio-Visual Profile with Feedback with Layered Codecs
In plain English — editorial summary, not part of the RFC
This document updates RFC 5104 by fixing a shortcoming in the specification language of the Codec Control Message Full Intra Request (FIR) description when using it with layered codecs. In particular, a decoder refresh point needs to be sent by a media sender when a FIR is received on any layer of the layered bitstream, regardless of whether those layers are being sent in a single or in multiple RTP flows. The other payload-specific feedback messages defined in RFC 5104 and RFC 4585 (which was updated by RFC 5506) have also been analyzed, and no corresponding shortcomings have been found.
Document record
- Document ID
- RFC8082
- Published
- March 2017
- Authors
- S. Wenger; J. Lennox; B. Burman; M. Westerlund
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 11
- Also known as
- —
- Updates:
- RFC 5104
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8081The "font" Top-Level Media TypeCurrent
February 2017
- RFC 8079Guidelines for End-to-End Support of the RTP Control Protocol (RTCP) in Back-to-Back User Agents (B2BUAs)Current
February 2017
- RFC 8076A Usage for Shared Resources in RELOAD (ShaRe)Current
March 2017
- RFC 8088How to Write an RTP Payload FormatUpdated
May 2017
- RFC 8089The "file" URI SchemeUpdated
February 2017
- RFC 8068Session Initiation Protocol (SIP) Recording Call FlowsCurrent
February 2017
- RFC 8098Message Disposition NotificationCurrent
February 2017
- RFC 8048Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): PresenceCurrent
December 2016
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?