Last Call: <draft-ietf-avtext-rams-scenarios-03.txt> (Considerations for Deploying the Rapid Acquisition of Multicast RTP Sessions (RAMS) Method) to Informational RFC

The IESG <iesg-secretary@ietf.org> Tue, 20 March 2012 12:40 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 704FA21F8678; Tue, 20 Mar 2012 05:40:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.52
X-Spam-Level:
X-Spam-Status: No, score=-102.52 tagged_above=-999 required=5 tests=[AWL=0.079, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v1LLK0B5VC7E; Tue, 20 Mar 2012 05:40:15 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B26F821F8659; Tue, 20 Mar 2012 05:40:15 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-avtext-rams-scenarios-03.txt> (Considerations for Deploying the Rapid Acquisition of Multicast RTP Sessions (RAMS) Method) to Informational RFC
X-Test-IDTracker: no
X-IETF-IDTracker: 4.00
Message-ID: <20120320124015.27203.60470.idtracker@ietfa.amsl.com>
Date: Tue, 20 Mar 2012 05:40:15 -0700
Cc: avtext@ietf.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Mar 2012 12:40:16 -0000

The IESG has received a request from the Audio/Video Transport Extensions
WG (avtext) to consider the following document:
- 'Considerations for Deploying the Rapid Acquisition of Multicast RTP
   Sessions (RAMS) Method'
  <draft-ietf-avtext-rams-scenarios-03.txt> as an Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2012-04-03. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

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.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-ietf-avtext-rams-scenarios/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-ietf-avtext-rams-scenarios/ballot/


No IPR declarations have been submitted directly on this I-D.