RFC 8872: Guidelines for Using the Multiplexing Features of RTP to Support Multiple Media Streams
In plain English — editorial summary, not part of the RFC
The Real-time Transport Protocol (RTP) is a flexible protocol that can be used in a wide range of applications, networks, and system topologies. That flexibility makes for wide applicability but can complicate the application design process. One particular design question that has received much attention is how to support multiple media streams in RTP. This memo discusses the available options and design trade-offs, and provides guidelines on how to use the multiplexing features of RTP to support multiple media streams.
Document record
- Document ID
- RFC8872
- Published
- January 2021
- Authors
- M. Westerlund; B. Burman; C. Perkins; H. Alvestrand; R. Even
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- wit
- Pages
- 36
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8881Network File System (NFS) Version 4 Minor Version 1 ProtocolCurrent
August 2020
- RFC 8861Sending Multiple RTP Streams in a Single RTP Session: Grouping RTP Control Protocol (RTCP) Reception Statistics and Other FeedbackCurrent
January 2021
- RFC 8860Sending Multiple Types of Media in a Single RTP SessionCurrent
January 2021
- RFC 8888RTP Control Protocol (RTCP) Feedback for Congestion ControlCurrent
January 2021
- RFC 8854WebRTC Forward Error Correction RequirementsCurrent
January 2021
- RFC 8899Packetization Layer Path MTU Discovery for Datagram TransportsCurrent
September 2020
- RFC 8837Differentiated Services Code Point (DSCP) Packet Markings for WebRTC QoSCurrent
January 2021
- RFC 8835Transports for WebRTCCurrent
January 2021
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?