Sending Multiple RTP Streams in a Single RTP Session
RFC 8108, “Sending Multiple RTP Streams in a Single RTP Session”, is a Proposed Standard document published in March 2017 by J. Lennox, M. Westerlund, Q. Wu, C. Perkins. It updates RFC 3550, RFC 4585. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 8108 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8107 Advertising Digital Identifier URN Namespace Definition
- RFC 8109 Initializing a DNS Resolver with Priming Queries
- RFC 8106 IPv6 Router Advertisement Options for DNS Configuration
- RFC 8110 Opportunistic Wireless Encryption
- RFC 8105 Transmission of IPv6 Packets over Digital Enhanced Cordless Telecommunications Ultra Low Energy
- RFC 8111 Locator/ID Separation Protocol Delegated Database Tree
- RFC 8104 Pseudowire Endpoint Fast Failure Protection
- RFC 8112 Locator/ID Separation Protocol Delegated Database Tree Referral Internet Groper