Multicast Acquisition Report Block Type for RTP Control Protocol (RTCP) Extended Reports (XRs)
RFC 6332

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 06

Internet Engineering Task Force (IETF)                          A. Begen
Request for Comments: 6332                                  E. Friedrich
Category: Standards Track                                          Cisco
ISSN: 2070-1721                                                July 2011

              Multicast Acquisition Report Block Type for
           RTP Control Protocol (RTCP) Extended Reports (XRs)

Abstract

   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).

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6332.

Begen & Friedrich            Standards Track                    [Page 1]
RFC 6332            MA Report Block Type for RTCP XR           July 2011

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Requirements Notation  . . . . . . . . . . . . . . . . . . . .  4
   3.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . . .  4
   4.  Multicast Acquisition (MA) Report Block  . . . . . . . . . . .  4
     4.1.  Base Report  . . . . . . . . . . . . . . . . . . . . . . .  5
       4.1.1.  Status Code Rules for New MA Methods . . . . . . . . .  6
       4.1.2.  Status Code Rules for the RAMS Method  . . . . . . . .  6
     4.2.  Extensions . . . . . . . . . . . . . . . . . . . . . . . .  6
       4.2.1.  Vendor-Neutral Extensions  . . . . . . . . . . . . . .  7
       4.2.2.  Private Extensions . . . . . . . . . . . . . . . . . . 10
   5.  Session Description Protocol Signaling . . . . . . . . . . . . 10
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 11
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
     7.1.  RTCP XR Block Type . . . . . . . . . . . . . . . . . . . . 11
     7.2.  RTCP XR SDP Parameter  . . . . . . . . . . . . . . . . . . 12
     7.3.  Multicast Acquisition Method Registry  . . . . . . . . . . 12
     7.4.  Multicast Acquisition Report Block TLV Space Registry  . . 12
     7.5.  Multicast Acquisition Status Code Space Registry . . . . . 13
   8.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . 14
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
     9.1.  Normative References . . . . . . . . . . . . . . . . . . . 15
     9.2.  Informative References . . . . . . . . . . . . . . . . . . 15

Begen & Friedrich            Standards Track                    [Page 2]
RFC 6332            MA Report Block Type for RTCP XR           July 2011

1.  Introduction

   The RTP Control Protocol (RTCP) is the out-of-band control protocol
   for applications that use the Real-time Transport Protocol (RTP) for
   media transport [RFC3550].  In addition to providing minimal control