Considerations for Deploying the Rapid Acquisition of Multicast RTP Sessions (RAMS) Method
draft-ietf-avtext-rams-scenarios-04

The information below is for an old version of the document
Document Type Active Internet-Draft (avtext WG)
Last updated 2012-04-23 (latest revision 2012-04-18)
Replaces draft-begen-avtext-rams-scenarios
Stream IETF
Intended RFC status Informational
Formats plain text pdf html
Stream WG state Submitted to IESG for Publication
Consensus Unknown
Document shepherd Keith Drage
IESG IESG state IESG Evaluation
Telechat date
Needs a YES.
Responsible AD Gonzalo Camarillo
IESG note Keith Drage (keith.drage@alcatel-lucent.com) is the document shepherd.
Send notices to avtext-chairs@tools.ietf.org, draft-ietf-avtext-rams-scenarios@tools.ietf.org
AVTEXT                                                          A. Begen
Internet-Draft                                                     Cisco
Intended status:  Informational                           April 18, 2012
Expires:  October 20, 2012

  Considerations for Deploying the Rapid Acquisition of Multicast RTP
                         Sessions (RAMS) Method
                  draft-ietf-avtext-rams-scenarios-04

Abstract

   The Rapid Acquisition of Multicast RTP Sessions (RAMS) solution is a
   method based on RTP and RTP Control Protocol (RTCP) that enables an
   RTP receiver to rapidly acquire and start consuming the RTP multicast
   data.  Upon a request from the RTP receiver, an auxiliary unicast RTP
   retransmission session is set up between a retransmission server and
   the RTP receiver, over which the reference information about the new
   multicast stream the RTP receiver is about to join is transmitted at
   an accelerated rate.  This often precedes, but may also accompany,
   the multicast stream itself.  When there is only one multicast stream
   to be acquired, the RAMS solution works in a straightforward manner.
   However, when there are two or more multicast streams to be acquired
   from the same or different multicast RTP sessions, care should be
   taken to configure each RAMS session appropriately.  This document
   provides example scenarios and discusses how the RAMS solution could
   be used in such scenarios.

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 October 20, 2012.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the

Begen                   Expires October 20, 2012                [Page 1]
Internet-Draft             RAMS Considerations                April 2012

   document authors.  All rights reserved.

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Background . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  Example Scenarios  . . . . . . . . . . . . . . . . . . . . . .  4
     3.1.  Scenario #1: Two Multicast Groups  . . . . . . . . . . . .  4
     3.2.  Scenario #2: One Multicast Group . . . . . . . . . . . . .  5
     3.3.  Scenario #3: SSRC Multiplexing . . . . . . . . . . . . . .  6
     3.4.  Scenario #4: Payload-Type Multiplexing . . . . . . . . . .  7
   4.  Feedback Target and SSRC Signaling Issues  . . . . . . . . . .  7
   5.  FEC during RAMS and Bandwidth Issues . . . . . . . . . . . . .  7
     5.1.  Scenario #1  . . . . . . . . . . . . . . . . . . . . . . .  8
     5.2.  Scenario #2  . . . . . . . . . . . . . . . . . . . . . . .  9
     5.3.  Scenario #3  . . . . . . . . . . . . . . . . . . . . . . . 10
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 10
   8.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 11
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 11
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 11
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12

Begen                   Expires October 20, 2012                [Page 2]
Internet-Draft             RAMS Considerations                April 2012

1.  Introduction

   The Rapid Acquisition of Multicast RTP Sessions (RAMS) solution is a
   method based on RTP and RTP Control Protocol (RTCP) that enables an
   RTP receiver to rapidly acquire and start consuming the RTP multicast
Show full document text