[AVT] Why RTCP is needed for synch after long time in aggregated A/V RTSP session?

"Jaehwan Kim" <jaehwan@vidiator.com> Mon, 02 April 2007 10:11 UTC

Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HYJVJ-0001pu-Q8; Mon, 02 Apr 2007 06:11:13 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HYJVI-0001pm-Ax for avt@ietf.org; Mon, 02 Apr 2007 06:11:12 -0400
Received: from [211.189.53.2] (helo=kor1corpmail01.mediator.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HYJVG-0004MJ-Ej for avt@ietf.org; Mon, 02 Apr 2007 06:11:12 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: [AVT] Why RTCP is needed for synch after long time in aggregated A/V RTSP session?
Date: Mon, 02 Apr 2007 19:10:57 +0900
Message-ID: <FE6A9D3F2979884280CE0F5F5185517B48023E@kor1corpmail01.mediator.com>
In-Reply-To: <4610AB4C.1080807@ericsson.com>
References: <E1HXGtE-0000EZ-R7@megatron.ietf.org> <006301c772dd$b6ab7fa0$0fa2ee0a@viola> <FE6A9D3F2979884280CE0F5F5185517B1921FB@kor1corpmail01.mediator.com> <f06240802c2357566a067@[66.80.62.44]><FE6A9D3F2979884280CE0F5F5185517B480200@kor1corpmail01.mediator.com> <4610AB4C.1080807@ericsson.com>
From: Jaehwan Kim <jaehwan@vidiator.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Ross Finlayson <finlayson@live555.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: annasagaram.vamsi@aftek.com, avt@ietf.org, "Y. Matsui" <matsui.yoshinori@jp.panasonic.com>
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Dear Magnus,
Yes, we need. And thanks to this group, people could learn many things
about RTP timestamp as described in the Appendix B of rfc2326bis. Now I
found most major players have been changed to follow it; it was not in
the past.

As for the subject, I would appreciate if we add more text about "why"
in future; I found one sentence from rfc2326bis-04 but failed to find
why.
(page92)

I felt that Ross knows some empirical knowledge. So, I asked him.
Ross, do you mind if you share your experience with us? 

>From my 2 cents, if the given RTSP session is VOD, although the given
session is enough long, the additional work, checking RTCP would not be
necessary to our client codes.

I think Ross mentioned the live RTSP session, in which we need to take
into account more. I would like to learn :->

And inline:

Magnus wrote:
>Okay, we will log a request to clarify that RTP-Info only provides for 
>initial sync and that RTCP is needed for maintaining sync in the case
of 
>clock drift. But there is much more on timestamp handling in 
>http://tools.ietf.org/html/draft-ietf-mmusic-rfc2326bis-14
>than what is in RFC 2326.
>I could also recommend looking at the How To write RTP payload formats 
>that has some discussion on the RTCP synch mechanism or Colin Perkins 
>book on RTP.
>http://tools.ietf.org/html/draft-ietf-avt-rtp-howto-01
Very nice references. Of course, Colin's is bible.

>There is also need to have RTCP for synch in cases such as multiple 
>sources (SSRCs) and live sessions. In addition RTCP is needed for its 
>transport monitoring purpose. The sender can't do any type of
adaptation 
>or avoid causing long term congestion unless RTCP is used.
Sometimes, non-functional requirement like simplicity and modifiability
is more important than additional features. IMHO, thereby allowing an
applications using just RTP without RTCP would be meaningful. At least,
it looks like optional in rfc2326.

Cheers,
Jaehwan


_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt