RE: [AVT] TimeStamp in the RFC2833 packet.
"Oren Peleg" <OrenP@audiocodes.com> Sun, 15 June 2003 12:56 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA29940 for <avt-archive@odin.ietf.org>; Sun, 15 Jun 2003 08:56:18 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h5FCto130107 for avt-archive@odin.ietf.org; Sun, 15 Jun 2003 08:55:50 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5F8x2a17247; Sun, 15 Jun 2003 04:59:02 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h5F8w6m17218 for <avt@optimus.ietf.org>; Sun, 15 Jun 2003 04:58:06 -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 EAA26543 for <avt@ietf.org>; Sun, 15 Jun 2003 04:58:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19RTIm-0002bm-00 for avt@ietf.org; Sun, 15 Jun 2003 04:55:52 -0400
Received: from bzq-179-22-133.cust.bezeqint.net ([212.179.22.133] helo=lodmsg01.corp.audiocodes.com) by ietf-mx with esmtp (Exim 4.12) id 19RTIl-0002bX-00 for avt@ietf.org; Sun, 15 Jun 2003 04:55:51 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0
content-class: urn:content-classes:message
Subject: RE: [AVT] TimeStamp in the RFC2833 packet.
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C3331C.335C4814"
Date: Sun, 15 Jun 2003 11:57:51 +0300
Message-ID: <BF10CC312C7A9C4FA2988BE360BAE44D338C49@lodmsg01.corp.audiocodes.com>
Thread-Topic: [AVT] TimeStamp in the RFC2833 packet.
Thread-Index: AcMxn3r0TMHQGfmmS3Gf91Z3GPTTZwBe0LfA
From: Oren Peleg <OrenP@audiocodes.com>
To: Awais Ali <aali@i2telecom.com>
Cc: avt@ietf.org, schulzrinne@cs.columbia.edu
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>
Thanks. It seems like a good idea. Probably should be added to the RTP-new draft. Regards, Oren P. -----Original Message----- From: Awais Ali [mailto:aali@i2telecom.com] Sent: Thursday, June 12, 2003 10:22 PM To: Oren Peleg; schulzrinne@cs.columbia.edu Cc: avt@ietf.org Subject: Re: [AVT] TimeStamp in the RFC2833 packet. The solution I am following right now is the one from http://www.cs.columbia.edu/~hgs/rtp/ which says under "How is Jitter Computed" "If several packets, say, within a video frame, bear the same timestamp, it is advisable to only use the first packet in a frame to compute the jitter. (This issue may be addressed in a future version of the specification.) ..." I hope the future version of spec. mentioned here is coming soon, because this aspect of timestamp issue is quite confusing in the current one. Regards Ali Awais ----- Original Message ----- From: Oren <mailto:OrenP@audiocodes.com> Peleg To: schulzrinne@cs.columbia.edu Cc: avt@ietf.org Sent: Wednesday, June 11, 2003 9:46 AM Subject: [AVT] TimeStamp in the RFC2833 packet. How does the RFC2833 TimeStamp values come along with the RTCP report Jitter Calculation explained at the RFC1889? Thanks, Oren Peleg Work phone No. : 03 - 5394167 Home phone No. : 03 - 5335913 Cell phone No. : 055 - 669613 Email : Oren.Peleg@audiocodes.com
- [AVT] TimeStamp in the RFC2833 packet. Oren Peleg
- Re: [AVT] TimeStamp in the RFC2833 packet. Awais Ali
- RE: [AVT] TimeStamp in the RFC2833 packet. Oren Peleg
- Re: [AVT] TimeStamp in the RFC2833 packet. Colin Perkins
- RE: [AVT] TimeStamp in the RFC2833 packet. Oren Peleg