RFC 6332: Multicast Acquisition Report Block Type for RTP Control Protocol (RTCP) Extended Reports (XRs)
In plain English — editorial summary, not part of the RFC
In most RTP-based multicast applications, the RTP source sends inter- related data. Due to this interdependency, randomly joining RTP receivers usually cannot start consuming the multicast data right after they join the session. Thus, they often experience a random acquisition delay. An RTP receiver can use one or more different approaches to achieve rapid acquisition. Yet, due to various factors, performance of the rapid acquisition methods usually varies. Furthermore, in some cases, the RTP receiver can do a simple multicast join (in other cases, it is compelled to do so). For quality reporting, monitoring, and diagnostic purposes, it is important to collect detailed information from the RTP receivers about their acquisition and presentation experiences. This document addresses this issue by defining a new report block type, called the Multicast Acquisition (MA) report block, within the framework of RTP Control Protocol (RTCP) Extended Reports (XRs) (RFC 3611). This document also defines the necessary signaling of the new MA report block type in the Session Description Protocol (SDP). [STANDARDS-TRACK]
Document record
- Document ID
- RFC6332
- Published
- July 2011
- Authors
- A. Begen; E. Friedrich
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6285Unicast-Based Rapid Acquisition of Multicast RTP SessionsCurrent
June 2011
- RFC 7667RTP TopologiesCurrent
November 2015
- RFC 8114Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast NetworkCurrent
March 2017
- RFC 8638IPv4 Multicast over an IPv6 Multicast in Softwire Mesh NetworksCurrent
September 2019
- RFC 8777DNS Reverse IP Automatic Multicast Tunneling (AMT) DiscoveryCurrent
April 2020
- RFC 8815Deprecating Any-Source Multicast (ASM) for Interdomain MulticastCurrent
August 2020
- RFC 9706TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass AudiencesCurrent
January 2025
- RFC 6659Considerations for Deploying the Rapid Acquisition of Multicast RTP Sessions (RAMS) MethodCurrent
July 2012
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?