RFC 4317: Session Description Protocol (SDP) Offer/Answer Examples
In plain English — editorial summary, not part of the RFC
This document gives examples of Session Description Protocol (SDP) offer/answer exchanges. Examples include codec negotiation and selection, hold and resume, and addition and deletion of media streams. The examples show multiple media types, bidirectional, unidirectional, inactive streams, and dynamic payload types. Common Third Party Call Control (3pcc) examples are also given. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4317
- Published
- December 2005
- Authors
- A. Johnston; R. Sparks
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 24
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4435A Framework for the Usage of Internet Media Guides (IMGs)Current
April 2006
- RFC 4473Requirements for Internet Media Guides (IMGs)Current
May 2006
- RFC 4145TCP-Based Media Transport in the Session Description Protocol (SDP)Updated
September 2005
- RFC 4130MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2 (AS2)Current
July 2005
- RFC 4091The Alternative Network Address Types (ANAT) Semantics for the Session Description Protocol (SDP) Grouping FrameworkObsoleted
June 2005
- RFC 4566SDP: Session Description ProtocolObsoleted
July 2006
- RFC 4567Key Management Extensions for Session Description Protocol (SDP) and Real Time Streaming Protocol (RTSP)Current
July 2006
- RFC 4568Session Description Protocol (SDP) Security Descriptions for Media StreamsCurrent
July 2006
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?