[AVT] FW: New Version Notification for draft-begen-avt-rapid-sync-rtcp-xr-03

["Ali C. Begen (abegen)" <abegen at cisco.com>]

Here is the update for the Multicast Acquisition RTCP XR format.
http://www.ietf.org/id/draft-begen-avt-rapid-sync-rtcp-xr-03.txt

The draft is now complete with no standing open issues. Instead of going for a direct IANA registration, we would like to have this work adopted by AVT and finalized along with the RAMS draft since they are closely related.

We presented this draft in Stockholm and will present a short update in two weeks. 

Chairs, ADs,

Can we add a milestone for this draft, preferably within the existing milestone for RAMS (e.g., develop an RTCP XR Multicast Acquisition Block for Proposed Standard)?

Thanks,
-acbegen

-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission at ietf.org] 
Sent: Thursday, October 22, 2009 1:52 PM
To: Ali C. Begen (abegen)
Cc: Eric Friedrich (efriedri)
Subject: New Version Notification for draft-begen-avt-rapid-sync-rtcp-xr-03 


A new version of I-D, draft-begen-avt-rapid-sync-rtcp-xr-03.txt has been successfuly submitted by Ali Begen and posted to the IETF repository.

Filename:	 draft-begen-avt-rapid-sync-rtcp-xr
Revision:	 03
Title:		 Multicast Acquisition Report Block Type for RTCP XR
Creation_date:	 2009-10-22
WG ID:		 Independent Submission
Number_of_pages: 21

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.  One approach to reduce this delay is to use an
auxiliary unicast RTP session with a retransmission server to receive
a burst stream that facilitates rapid acquisition of the multicast
stream.  An RTP receiver may use this approach (or any other
approach) to achieve rapid acquisition.  Yet, due to various factors,
performance of the rapid acquisition methods usually varies.
Furthermore, in some cases the RTP receiver may (or may have to) do a
simple multicast join.  For quality reporting, monitoring and
diagnostics 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 Multicast Acquisition (MA) Report Block,
within the framework of RTP Control Protocol (RTCP) Extended Reports
(XR).  This document also defines the necessary signaling of the new
MA report block type in the Session Description Protocol (SDP).
                                                                                  


The IETF Secretariat.