RFC 5939: Session Description Protocol (SDP) Capability Negotiation
In plain English — editorial summary, not part of the RFC
The Session Description Protocol (SDP) was intended to describe multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. SDP was not intended to provide capability indication or capability negotiation; however, over the years, SDP has seen widespread adoption and as a result it has been gradually extended to provide limited support for these, notably in the form of the offer/answer model defined in RFC 3264. SDP does not define how to negotiate one or more alternative transport protocols (e.g., RTP profiles) or attributes. This makes it difficult to deploy new RTP profiles such as Secure RTP or RTP with RTCP-based feedback, negotiate use of different security keying mechanisms, etc. It also presents problems for some forms of media negotiation. The purpose of this document is to address these shortcomings by extending SDP with capability negotiation parameters and associated offer/answer procedures to use those parameters in a backwards compatible manner. The document defines a general SDP Capability Negotiation framework. It also specifies how to provide attributes and transport protocols as capabilities and negotiate them using the framework. Extensions for other types of capabilities (e.g., media types and media formats) may be provided in other documents. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5939
- Published
- September 2010
- Authors
- F. Andreasen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 77
- Also known as
- —
- Updated by:
- RFC 6871
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5956Forward Error Correction Grouping Semantics in the Session Description ProtocolCurrent
September 2010
- RFC 5964Specifying Holes in Location-to-Service Translation (LoST) Service BoundariesCurrent
August 2010
- RFC 5898Connectivity Preconditions for Session Description Protocol (SDP) Media StreamsCurrent
July 2010
- RFC 5888The Session Description Protocol (SDP) Grouping FrameworkUpdated
June 2010
- RFC 5863DomainKeys Identified Mail (DKIM) Development, Deployment, and OperationsCurrent
May 2010
- RFC 6026Correct Transaction Handling for 2xx Responses to Session Initiation Protocol (SIP) INVITE RequestsCurrent
September 2010
- RFC 5839An Extension to Session Initiation Protocol (SIP) Events for Conditional Event NotificationCurrent
May 2010
- RFC 6086Session Initiation Protocol (SIP) INFO Method and Package FrameworkCurrent
January 2011
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?