Considerations for Deploying the Rapid Acquisition of Multicast RTP Sessions Method
RFC 6659, “Considerations for Deploying the Rapid Acquisition of Multicast RTP Sessions Method”, is an Informational document published in July 2012 by A. Begen. The canonical text is published by the RFC Editor.
Abstract
The Rapid Acquisition of Multicast RTP Sessions (RAMS) solution is a method based on RTP and the 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. This document is not an Internet Standards Track specification; it is published for informational purposes.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 6659 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6658 Packet Pseudowire Encapsulation over an MPLS PSN
- RFC 6660 Encoding Three Pre-Congestion Notification States in the IP Header Using a Single Diffserv Codepoint
- RFC 6657 Update to MIME regarding "charset" Parameter Handling in Textual Media Types
- RFC 6661 Pre-Congestion Notification Boundary-Node Behavior for the Controlled Load Mode of Operation
- RFC 6656 Description of Cisco Systems' Subnet Allocation Option for DHCPv4
- RFC 6662 Pre-Congestion Notification Boundary-Node Behavior for the Single Marking Mode of Operation
- RFC 6663 Requirements for Signaling of Pre-Congestion Information in a Diffserv Domain
- RFC 6655 AES-CCM Cipher Suites for Transport Layer Security