RFC 5583: Signaling Media Decoding Dependency in the Session Description Protocol (SDP)
In plain English — editorial summary, not part of the RFC
This memo defines semantics that allow for signaling the decoding dependency of different media descriptions with the same media type in the Session Description Protocol (SDP). This is required, for example, if media data is separated and transported in different network streams as a result of the use of a layered or multiple descriptive media coding process. A new grouping type "DDP" -- decoding dependency -- is defined, to be used in conjunction with RFC 3388 entitled "Grouping of Media Lines in the Session Description Protocol". In addition, an attribute is specified describing the relationship of the media streams in a "DDP" group indicated by media identification attribute(s) and media format description(s). [STANDARDS-TRACK]
Document record
- Document ID
- RFC5583
- Published
- July 2009
- Authors
- T. Schierl; S. Wenger
- 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 5044Marker PDU Aligned Framing for TCP SpecificationUpdated
October 2007
- RFC 5041Direct Data Placement over Reliable TransportsUpdated
October 2007
- RFC 5040A Remote Direct Memory Access Protocol SpecificationUpdated
October 2007
- RFC 7306Remote Direct Memory Access (RDMA) Protocol ExtensionsCurrent
June 2014
- RFC 5582Location-to-URL Mapping Architecture and FrameworkCurrent
September 2009
- RFC 5585DomainKeys Identified Mail (DKIM) Service OverviewCurrent
July 2009
- RFC 5576Source-Specific Media Attributes in the Session Description Protocol (SDP)Current
June 2009
- RFC 5617DomainKeys Identified Mail (DKIM) Author Domain Signing Practices (ADSP)Updated
August 2009
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?