RFC 4566: SDP: Session Description Protocol
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8866.
Current document in this lineage: RFC 8866 — SDP: Session Description Protocol
In plain English — editorial summary, not part of the RFC
This memo defines the Session Description Protocol (SDP). SDP is intended for describing multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4566
- Published
- July 2006
- Authors
- M. Handley; V. Jacobson; C. Perkins
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 49
- Also known as
- —
- Obsoleted by:
- RFC 8866
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 2327 (1998)
- RFC 3266 (2002)
- RFC 4566 (2006)
- RFC 8866 (2021) ✓
Read the full history of SDP: Session Description Protocol →
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 3264An Offer/Answer Model with Session Description Protocol (SDP)Updated
July 2002
- RFC 2543SIP: Session Initiation ProtocolObsoleted
March 1999
- RFC 4629RTP Payload Format for ITU-T Rec. H.263 VideoCurrent
January 2007
- RFC 4916Connected Identity in the Session Initiation Protocol (SIP)Current
June 2007
- RFC 3853S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP)Current
July 2004
- RFC 5393Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking ProxiesCurrent
December 2008
- RFC 3513Internet Protocol Version 6 (IPv6) Addressing ArchitectureObsoleted
April 2003
- RFC 3265Session Initiation Protocol (SIP)-Specific Event NotificationObsoleted
July 2002
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?