RFC 7941: RTP Header Extension for the RTP Control Protocol (RTCP) Source Description Items
In plain English — editorial summary, not part of the RFC
Source Description (SDES) items are normally transported in the RTP Control Protocol (RTCP). In some cases, it can be beneficial to speed up the delivery of these items. The main case is when a new synchronization source (SSRC) joins an RTP session and the receivers need this source's identity, relation to other sources, or its synchronization context, all of which may be fully or partially identified using SDES items. To enable this optimization, this document specifies a new RTP header extension that can carry SDES items.
Document record
- Document ID
- RFC7941
- Published
- August 2016
- Authors
- M. Westerlund; B. Burman; R. Even; M. Zanaty
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 17
- Also known as
- —
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7940Representing Label Generation Rulesets Using XMLCurrent
August 2016
- RFC 7946The GeoJSON FormatCurrent
August 2016
- RFC 7953Calendar AvailabilityCurrent
August 2016
- RFC 7960Interoperability Issues between Domain-based Message Authentication, Reporting, and Conformance (DMARC) and Indirect Email FlowsCurrent
September 2016
- RFC 7904A SIP Usage for REsource LOcation And Discovery (RELOAD)Current
October 2016
- RFC 7984Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP NetworkCurrent
September 2016
- RFC 7986New Properties for iCalendarCurrent
October 2016
- RFC 7989End-to-End Session Identification in IP-Based Multimedia Communication NetworksCurrent
October 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?