Browse Prior Art Database

Duplicating RTP Streams (RFC7198) Disclosure Number: IPCOM000236450D
Original Publication Date: 2014-Apr-01
Included in the Prior Art Database: 2014-Apr-26
Document File: 26 page(s) / 29K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

A. Begen: AUTHOR [+1]


The Real-time Transport Protocol (RTP) [RFC3550] is widely used today for delivering IPTV traffic and other real-time multimedia sessions. Many of these applications support very large numbers of receivers and rely on intra-domain UDP/IP multicast for efficient distribution of traffic within the network.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 9% of the total text.

Internet Engineering Task Force (IETF)                          A. Begen Request for Comments: 7198                                         Cisco Category: Standards Track                                     C. Perkins ISSN: 2070-1721                                    University of Glasgow                                                               April 2014

                         Duplicating RTP Streams


   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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at

 Begen & Perkins              Standards Track                    [Page 1]
 RFC 7198                     RTP Duplication                  April 2014

 Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    ( in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without war...