RE: [AVT] RTP/RTCP Timestamp and transmission time

"Alan Clark" <alan@telchemy.com> Mon, 22 September 2003 12:02 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11482 for <avt-archive@odin.ietf.org>; Mon, 22 Sep 2003 08:02:33 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A1POM-0007O3-B8 for avt-archive@odin.ietf.org; Mon, 22 Sep 2003 08:02:10 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8MC2AHE028351 for avt-archive@odin.ietf.org; Mon, 22 Sep 2003 08:02:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A1POE-0007Md-Da; Mon, 22 Sep 2003 08:02:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A1PNc-0007Lb-9M for avt@optimus.ietf.org; Mon, 22 Sep 2003 08:01:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11442 for <avt@ietf.org>; Mon, 22 Sep 2003 08:01:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A1PNW-0006BB-00 for avt@ietf.org; Mon, 22 Sep 2003 08:01:18 -0400
Received: from www.telchemy.com ([66.155.69.251] helo=telchemy.com) by ietf-mx with esmtp (Exim 4.12) id 1A1PNG-0006AG-00 for avt@ietf.org; Mon, 22 Sep 2003 08:01:02 -0400
Received: from alansnotebook [66.156.9.53] by telchemy.com with ESMTP (SMTPD32-7.14) id A3D794F0150; Mon, 22 Sep 2003 07:58:15 -0400
From: Alan Clark <alan@telchemy.com>
To: Colin Perkins <csp@csperkins.org>, Lorenzo Polidori <lorenzo@blt.it>
Cc: avt@ietf.org
Subject: RE: [AVT] RTP/RTCP Timestamp and transmission time
Date: Mon, 22 Sep 2003 08:04:12 -0400
Message-ID: <OKECKEHENBLEOHBIOCIBMEGMCAAA.alan@telchemy.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <52CCCA2C-EAF9-11D7-8ECA-000A957FC5F2@csperkins.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
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>
Content-Transfer-Encoding: 7bit

Colin

Does the RTCP PPDV/jitter calculation accomodate this situation where a
burst of RTP packets with the same TS are sent (or RTP frames are not
transmitted with uniform spacing)?

Alan Clark
Telchemy

-----Original Message-----
From: avt-admin@ietf.org [mailto:avt-admin@ietf.org]On Behalf Of Colin
Perkins
Sent: Friday, September 19, 2003 7:31 PM
To: Lorenzo Polidori
Cc: avt@ietf.org
Subject: Re: [AVT] RTP/RTCP Timestamp and transmission time



On Friday, Sep 19, 2003, at 08:36 Europe/London, Lorenzo Polidori wrote:

> At 12.56 18/09/2003 +0100, Colin Perkins wrote:
>
>> You need to schedule the transmission time of the RTP packets
>> according
>> to their RTP timestamp. Since the packets are timed, there is a
>> correlation with the wall-clock.
>
> Ok, now it's clear, thanks all. But I have an other question. I must
> schedule  the transmission time of the RTP packets and the packets
> containing the same MPEG2 picture have the same RTP TS, since the time
> reference of the slides belonging to the same picture does not change.
> Am I
> obliged to send a burst of RTP data packets every MPEG2 scheduled
> picture,
> containing all the relative slides?

You are not obliged to send them in a burst, however RTP provides no
way for the receiver to distinguish sender-induced delay from
network-induced delay.

--
Colin Perkins
http://csperkins.org/


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


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