metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 8108: Sending Multiple RTP Streams in a Single RTP Session

In plain English — editorial summary, not part of the RFC

This memo expands and clarifies the behavior of Real-time Transport Protocol (RTP) endpoints that use multiple synchronization sources (SSRCs). This occurs, for example, when an endpoint sends multiple RTP streams in a single RTP session. This memo updates RFC 3550 with regard to handling multiple SSRCs per endpoint in RTP sessions, with a particular focus on RTP Control Protocol (RTCP) behavior. It also updates RFC 4585 to change and clarify the calculation of the timeout of SSRCs and the inclusion of feedback messages.

Document record

Document ID
RFC8108
Published
March 2017
Authors
J. Lennox; M. Westerlund; Q. Wu; C. Perkins
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
29
Also known as
—
Updates:
RFC 3550, RFC 4585

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/8108-sending-multiple-rtp-streams-in-a-single-rtp-session