RFC 3388: Grouping of Media Lines in the Session Description Protocol (SDP)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5888.
Current version: RFC 5888 — The Session Description Protocol (SDP) Grouping Framework
In plain English — editorial summary, not part of the RFC
This document defines two SDP attributes: 'groupe' and 'mid'. They allow to group together several 'm' lines for two different purposes: for lip synchronization and for receiving media from a single flow (several media streams), encoded in different formats during a particular session, in different ports and host interfaces.
Document record
- Document ID
- RFC3388
- Published
- December 2002
- Authors
- G. Camarillo; G. Eriksson; J. Holler; H. Schulzrinne
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 11
- Also known as
- —
- Obsoleted by:
- RFC 5888
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 3264An Offer/Answer Model with Session Description Protocol (SDP)Updated
July 2002
- RFC 3524Mapping of Media Streams to Resource Reservation FlowsCurrent
April 2003
- RFC 3605Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)Current
October 2003
- RFC 3108Conventions for the use of the Session Description Protocol (SDP) for ATM Bearer ConnectionsCurrent
May 2001
- RFC 3890A Transport Independent Bandwidth Modifier for the Session Description Protocol (SDP)Current
September 2004
- RFC 4435A Framework for the Usage of Internet Media Guides (IMGs)Current
April 2006
- RFC 5576Source-Specific Media Attributes in the Session Description Protocol (SDP)Current
June 2009
- RFC 3322Signaling Compression (SigComp) Requirements & AssumptionsCurrent
January 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?