Search RFCs

RFC Editor

File formats:

Status:

PROPOSED STANDARD

Authors:

A. Begen
E. Friedrich

Stream:

IETF

Source:

avtext (rai)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC6332

Discuss this RFC: Send questions or comments to the mailing listavtext@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 6332

Abstract

In most RTP-based multicast applications, the RTP source sends inter-related data. Due to this interdependency, randomly joining RTPreceivers usually cannot start consuming the multicast data rightafter they join the session. Thus, they often experience a randomacquisition delay. An RTP receiver can use one or more differentapproaches to achieve rapid acquisition. Yet, due to variousfactors, performance of the rapid acquisition methods usually varies.Furthermore, in some cases, the RTP receiver can do a simplemulticast join (in other cases, it is compelled to do so). Forquality reporting, monitoring, and diagnostic purposes, it isimportant to collect detailed information from the RTP receiversabout their acquisition and presentation experiences. This documentaddresses this issue by defining a new report block type, called theMulticast Acquisition (MA) report block, within the framework of RTPControl Protocol (RTCP) Extended Reports (XRs) (RFC 3611). Thisdocument also defines the necessary signaling of the new MA reportblock type in the Session Description Protocol (SDP). [STANDARDS-TRACK]

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.