datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

Duplicating RTP Streams
draft-ietf-avtext-rtp-duplication-06

Document type: Active Internet-Draft (avtext WG)
Document stream: IETF
Last updated: 2014-02-28 (latest revision 2014-02-26)
Intended RFC status: Proposed Standard
Other versions: plain text, pdf, html

IETF State: Submitted to IESG for Publication
Consensus: Unknown
Document shepherd: Jonathan Lennox
Shepherd Write-Up: Last changed 2013-12-05

IESG State: RFC Ed Queue
IANA Review State: IANA OK - No Actions Needed
IANA Action State: No IC
RFC Editor State: AUTH48-DONE
Responsible AD: Gonzalo Camarillo
Send notices to: avtext-chairs@tools.ietf.org, draft-ietf-avtext-rtp-duplication@tools.ietf.org

AVTEXT                                                          A. Begen
Internet-Draft                                                     Cisco
Intended status: Standards Track                              C. Perkins
Expires: August 24, 2014                           University of Glasgow
                                                       February 20, 2014

                        Duplicating RTP Streams
                  draft-ietf-avtext-rtp-duplication-06

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
   potential large number of missing packets.  In multicast
   transmissions, recovery is even more challenging as many receivers
   could be impacted by the outage.  One solution to this challenge
   without incurring 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 Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 24, 2014.

Copyright Notice

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

Begen & Perkins          Expires August 24, 2014                [Page 1]
Internet-Draft               RTP Duplication               February 2014

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) 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 warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology and Requirements Notation . . . . . . . . . . . .   3
   3.  Dual Streaming Use Cases  . . . . . . . . . . . . . . . . . .   3
     3.1.  Temporal Redundancy . . . . . . . . . . . . . . . . . . .   4
     3.2.  Spatial Redundancy  . . . . . . . . . . . . . . . . . . .   4
     3.3.  Dual Streaming over a Single Path or Multiple Paths . . .   5
     3.4.  Requirements  . . . . . . . . . . . . . . . . . . . . . .   6
   4.  Use of RTP and RTCP with Temporal Redundancy  . . . . . . . .   6
     4.1.  RTCP Considerations . . . . . . . . . . . . . . . . . . .   6
     4.2.  Signaling Considerations  . . . . . . . . . . . . . . . .   7
   5.  Use of RTP and RTCP with Spatial Redundancy . . . . . . . . .   8
     5.1.  RTCP Considerations . . . . . . . . . . . . . . . . . . .   8
     5.2.  Signaling Considerations  . . . . . . . . . . . . . . . .   9
   6.  Use of RTP and RTCP with Temporal and Spatial Redundancy  . .   9
   7.  Congestion Control Considerations . . . . . . . . . . . . . .   9
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  11
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     11.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   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.

[include full document text]