RFC 5576: Source-Specific Media Attributes in the Session Description Protocol (SDP)
In plain English — editorial summary, not part of the RFC
The Session Description Protocol (SDP) provides mechanisms to describe attributes of multimedia sessions and of individual media streams (e.g., Real-time Transport Protocol (RTP) sessions) within a multimedia session, but does not provide any mechanism to describe individual media sources within a media stream. This document defines a mechanism to describe RTP media sources, which are identified by their synchronization source (SSRC) identifiers, in SDP, to associate attributes with these sources, and to express relationships among sources. It also defines several source-level attributes that can be used to describe properties of media sources. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5576
- Published
- June 2009
- Authors
- J. Lennox; J. Ott; T. Schierl
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2733An RTP Payload Format for Generic Forward Error CorrectionObsoleted
December 1999
- RFC 7104Duplication Grouping Semantics in the Session Description ProtocolCurrent
January 2014
- RFC 7604Comparison of Different NAT Traversal Techniques for Media Controlled by the Real-Time Streaming Protocol (RTSP)Current
September 2015
- RFC 3388Grouping of Media Lines in the Session Description Protocol (SDP)Obsoleted
December 2002
- RFC 8627RTP Payload Format for Flexible Forward Error Correction (FEC)Current
July 2019
- RFC 5459G.729.1 RTP Payload Format Update: Discontinuous Transmission (DTX) SupportCurrent
January 2009
- RFC 5775Asynchronous Layered Coding (ALC) Protocol InstantiationCurrent
April 2010
- RFC 5371RTP Payload Format for JPEG 2000 Video StreamsCurrent
October 2008
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?