Duplicating RTP Streams
RFC 7198, “Duplicating RTP Streams”, is a Proposed Standard document published in April 2014 by A. Begen, C. Perkins. The canonical text is published by the RFC Editor.
Abstract
Packet loss is undesirable for real-time multimedia sessions but can occur due to a variety of reasons including unplanned network outages. In unicast transmissions, recovering from such an outage can be difficult depending on the outage duration, due to the potentially large number of missing packets. In multicast transmissions, recovery is even more challenging as many receivers could be impacted by the outage. For this challenge, one solution that does not incur unbounded delay is to duplicate the packets and send them in separate redundant streams, provided that the underlying network satisfies certain requirements. This document explains how Real-time Transport Protocol (RTP) streams can be duplicated without breaking RTP or RTP Control Protocol (RTCP) rules.
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 7198 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 7197 Duplication Delay Attribute in the Session Description Protocol
- RFC 7199 Location Configuration Extensions for Policy Management
- RFC 7196 Making Route Flap Damping Usable
- RFC 7200 A Session Initiation Protocol Load-Control Event Package
- RFC 7195 Session Description Protocol Extension for Setting Audio and Video Media Streams over Circuit-Switched Bearers in the Public Switched Telephone Network
- RFC 7201 Options for Securing RTP Sessions
- RFC 7194 Default Port for Internet Relay Chat via TLS/SSL
- RFC 7202 Securing the RTP Framework: Why RTP Does Not Mandate a Single Media Security Solution