RE: [AVT] RTP/RTCP Timestamp and transmission time
"Allison, Art" <AAllison@nab.org> Thu, 18 September 2003 12:55 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 IAA09767 for <avt-archive@odin.ietf.org>; Thu, 18 Sep 2003 08:55:05 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19zyJ0-0003QT-E3 for avt-archive@odin.ietf.org; Thu, 18 Sep 2003 08:54:42 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8ICsgc6013126 for avt-archive@odin.ietf.org; Thu, 18 Sep 2003 08:54:42 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19zyIM-0003Id-4x; Thu, 18 Sep 2003 08:54:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19zyHZ-0003Hc-Uz for avt@optimus.ietf.org; Thu, 18 Sep 2003 08:53:13 -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 IAA09685 for <avt@ietf.org>; Thu, 18 Sep 2003 08:53:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19zyHY-0005Oq-00 for avt@ietf.org; Thu, 18 Sep 2003 08:53:12 -0400
Received: from foxtrot.nab.org ([209.116.240.194]) by ietf-mx with esmtp (Exim 4.12) id 19zyHY-0005On-00 for avt@ietf.org; Thu, 18 Sep 2003 08:53:12 -0400
Received: from mail.nab.org by [209.116.240.194] via smtpd (for ietf-mx.ietf.org [132.151.6.1]) with ESMTP; Thu, 18 Sep 2003 08:53:12 -0400
Received: (private information removed)
Message-ID: <5A659834E1607E4EBD72FCE2FE5C9CF102FEB9C4@mail.NAB.ORG>
From: "Allison, Art" <AAllison@nab.org>
Cc: avt@ietf.org
Subject: RE: [AVT] RTP/RTCP Timestamp and transmission time
Date: Thu, 18 Sep 2003 08:53:10 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain; charset="iso-8859-1"
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>
Be aware that real MPEG-2 streams often contain time line discontinuities,
which are signaled via the discontinuity_indicator in the MPEG transport
packets' adaptation field.
Art
::{)
Art Allison
Director Advanced Engineering
NAB
1771 N St NW
Washington DC 20036
202 429 5418
-----Original Message-----
From: Colin Perkins [mailto:csp@csperkins.org]
Sent: Thursday, September 18, 2003 7:57 AM
To: Lorenzo Polidori
Cc: avt@ietf.org
Subject: Re: [AVT] RTP/RTCP Timestamp and transmission time
On Thursday, Sep 18, 2003, at 11:31 Europe/London, Lorenzo Polidori
wrote:
> Colin Perkins wrote:
>
>> The RTP timestamp is NOT calculated from the NTP timestamp, but
>> represents a sampling of the media clock.
>
> Ok, thank you. But can you explain the exact meaning of the following
> fragment of RFC 3550, section 6.4.1:
> "Note that in most cases this timestamp [RTP timestamp of an SR-RTCP
> packet]
> will not be equal to the RTP timestamp in any adjacent data packet.
> Rather,
> it MUST be calculated from the corresponding NTP timestamp using the
> relationship between the RTP timestamp counter and real time as
> maintained
> by periodically checking the wallclock time at a sampling instant".
This is for the particular case of estimating the RTP timestamp value
to include in an RTCP SR packet, if it is not possible to sample the
RTP clock at arbitrary instants.
A system that cannot sample the RTP clock at arbitrary times, and which
has no NTP-format clock, will have to set the RTP timestamp in an RTCP
SR to zero. Systems that have no local clock are very rare though, so
this should almost never be a concern.
> Now, I have an MPEG2 Elementary Stream (ES), stored on disk, to be
> transmitted over RTP. From Elementary Stream I can get and convert
> MPEG time
> code & temporal reference to a 90 kHz RTP timestamp, as in RFC 2250.
> So, I
> put this RTP timestamp in RTP data packet header: this timestamp is
> computed
> from the MPEG2 time code stored on disk, so it isn't correlated to the
> system wallclock current time.
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.
> If I get RTP timestamp of SR-RTCP packet
> sampling the wallclock current time, what's the correlation between RTP
> timestamp on RTP data packet and RTP timestamp on RTCP packet?
The RTP timestamps in data packets and in RTCP SR packets are samples of
the same conceptual clock, at the instant that packet is generated. The
wall-clock time is always correlated with the RTP timestamp, although it
is a separate clock (since the RTP timestamps are derived from the media
timing).
--
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
- Re: [AVT] RTP/RTCP Timestamp and transmission time Colin Perkins
- Re: [AVT] RTP/RTCP Timestamp and transmission time Magnus Westerlund
- Re: [AVT] RTP/RTCP Timestamp and transmission time Colin Perkins
- RE: [AVT] RTP/RTCP Timestamp and transmission time Allison, Art
- Re: [AVT] RTP/RTCP Timestamp and transmission time Colin Perkins
- RE: [AVT] RTP/RTCP Timestamp and transmission time Alan Clark
- Re: [AVT] RTP/RTCP Timestamp and transmission time Colin Perkins