RFC 3266: Support for IPv6 in Session Description Protocol (SDP)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 4566.
Current document in this lineage: RFC 8866 — SDP: Session Description Protocol
In plain English — editorial summary, not part of the RFC
This document describes the use of Internet Protocol Version 6 (IPv6) addresses in conjunction with the Session Description Protocol (SDP). Specifically, this document clarifies existing text in SDP with regards to the syntax of IPv6 addresses. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3266
- Published
- July 2002
- Authors
- S. Olson; G. Camarillo; A. B. Roach
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 5
- Also known as
- —
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 3259A Message Bus for Local CoordinationCurrent
May 2002
- RFC 3335MIME-based Secure Peer-to-Peer Business Data Interchange over the InternetCurrent
September 2002
- RFC 3388Grouping of Media Lines in the Session Description Protocol (SDP)Obsoleted
December 2002
- RFC 3108Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer ConnectionsCurrent
May 2001
- RFC 3524Mapping of Media Streams to Resource Reservation FlowsCurrent
April 2003
- RFC 2974Session Announcement ProtocolCurrent
October 2000
- RFC 3605Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)Current
October 2003
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?