Preparing your result...
Loading...
Press Esc to dismiss this message

Multicast Acquisition Report Block Type for RTP Control Protocol (RTCP) Extended Reports (XRs) (RFC6332) (01-Jul-2011)

Thumbnail
IP.com Prior Art Database Disclosure (Source: IPCOM)
Disclosure Number IPCOM000209191D dated 01-Jul-2011
Added to Prior Art Database on 30-Jul-2011
Disclosed by: ISOC
Country: United States
Copyright: Copyright (c) 2011 IETF Trust and the persons identified as the
Related People
A. Begen - AUTHOR [+1] [-1]
E. Friedrich - AUTHOR
Disclosure File: 32 pages / 35.3 KB / English (United States)

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 functionality to RTP entities, RTCP also enables a basic-level monitoring of RTP sessions via sender and receiver reports. More statistically detailed monitoring as well as application-specific monitoring are usually achieved through the RTCP Extended Reports (XRs) [RFC3611].

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 8% of the total text.

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

(Source: IPCOM)
First page image
(Source: IPCOM)