Duplicating RTP Streams
draft-begen-avtcore-rtp-duplication-01
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2012-09-11 (latest revision 2012-03-10) | ||
| Replaced by | RFC 7198 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-avtext-rtp-duplication | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-begen-avtcore-rtp-duplication-01.txt
Abstract
Packet loss is undesirable for real-time multimedia sessions, but can occur due to congestion, or other unplanned network outages. This is especially true for IP multicast networks, where packet loss patterns can vary greatly between receivers. One technique that can be used to recover from packet loss without incurring unbounded delay for all the receivers is to duplicate the packets and send them in separate redundant streams. This document explains how Real-time Transport Protocol (RTP) streams can be duplicated without breaking RTP media streams, or RTP Control Protocol (RTCP) rules.
Authors
Ali Begen
(abegen@cisco.com)
Colin Perkins
(csp@csperkins.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)