RFC 8860: Sending Multiple Types of Media in a Single RTP Session
In plain English — editorial summary, not part of the RFC
This document specifies how an RTP session can contain RTP streams with media from multiple media types such as audio, video, and text. This has been restricted by the RTP specifications (RFCs 3550 and 3551), and thus this document updates RFCs 3550 and 3551 to enable this behaviour for applications that satisfy the applicability for using multiple media types in a single RTP session.
Document record
- Document ID
- RFC8860
- Published
- January 2021
- Authors
- M. Westerlund; C. Perkins; J. Lennox
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8843Negotiating Media Multiplexing Using the Session Description Protocol (SDP)Obsoleted
January 2021
- RFC 9143Negotiating Media Multiplexing Using the Session Description Protocol (SDP)Current
February 2022
- RFC 9134RTP Payload Format for ISO/IEC 21122 (JPEG XS)Current
October 2021
- RFC 7667RTP TopologiesCurrent
November 2015
- RFC 7478Web Real-Time Communication Use Cases and RequirementsCurrent
March 2015
- RFC 7201Options for Securing RTP SessionsCurrent
April 2014
- RFC 9172Bundle Protocol Security (BPSec)Current
January 2022
- RFC 9173Default Security Contexts for Bundle Protocol Security (BPSec)Current
January 2022
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?