RFC 6659: Considerations for Deploying the Rapid Acquisition of Multicast RTP Sessions (RAMS) Method
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC6659
- Published
- July 2012
- Authors
- A. Begen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- art
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6683Guidelines for Implementing Digital Video Broadcasting - IPTV (DVB-IPTV) Application-Layer Hybrid Forward Error Correction (FEC) ProtectionCurrent
August 2012
- RFC 5725Post-Repair Loss RLE Report Block Type for RTP Control Protocol (RTCP) Extended Reports (XRs)Current
February 2010
- RFC 6332Multicast Acquisition Report Block Type for RTP Control Protocol (RTCP) Extended Reports (XRs)Current
July 2011
- RFC 6026Correct Transaction Handling for 2xx Responses to Session Initiation Protocol (SIP) INVITE RequestsCurrent
September 2010
- RFC 5956Forward Error Correction Grouping Semantics in the Session Description ProtocolCurrent
September 2010
- RFC 5576Source-Specific Media Attributes in the Session Description Protocol (SDP)Current
June 2009
- RFC 4756Forward Error Correction Grouping Semantics in Session Description ProtocolObsoleted
November 2006
- RFC 8627RTP Payload Format for Flexible Forward Error Correction (FEC)Current
July 2019
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?