Re: [P2PSIP] P2PSIP diagnostics: PING discussion
Colin Perkins <csp@csperkins.org> Thu, 13 November 2008 19:34 UTC
Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A382B3A698C; Thu, 13 Nov 2008 11:34:22 -0800 (PST)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 148B53A69BA; Thu, 13 Nov 2008 11:34:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.598
X-Spam-Level:
X-Spam-Status: No, score=-6.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 70JV6qnXplzD; Thu, 13 Nov 2008 11:34:20 -0800 (PST)
Received: from mr1.dcs.gla.ac.uk (mr1.dcs.gla.ac.uk [130.209.249.184]) by core3.amsl.com (Postfix) with ESMTP id ED81E3A698C; Thu, 13 Nov 2008 11:34:19 -0800 (PST)
Received: from [64.102.186.84] (port=57402 helo=[64.102.186.84]) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42) id 1L0hxK-0002Df-Qt; Thu, 13 Nov 2008 19:34:18 +0000
In-Reply-To: <491c390c.0506d00a.722c.ffffcbce@mx.google.com>
References: <2D06DE445C2ADE44890118C3F449B9631FA33659@NASANEXMB12.na.qualcomm.com> <491c390c.0506d00a.722c.ffffcbce@mx.google.com>
Mime-Version: 1.0 (Apple Message framework v753.1)
Message-Id: <FB41DAA8-6C39-4390-A2FF-DB4460763A06@csperkins.org>
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [P2PSIP] P2PSIP diagnostics: PING discussion
Date: Thu, 13 Nov 2008 14:34:15 -0500
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.753.1)
Cc: "'Das, Saumitra'" <saumitra@qualcomm.com>, p2psip@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1363900820=="
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
On 13 Nov 2008, at 09:24, Roni Even wrote: > I am not sure what you mean NTP refresh, if the test was using the > system clock than you would expect in XP that it will be updated > every tick which is 10 or 15 msec which can account for the error. > NTP is used in RTP (RFC 3550) for synchronization and the RTP time > is using the system clock which may add skew but it is not because > of NTP. > One minor clarification: RTP uses an NTP format timestamp, but it doesn't require the use of NTP. -- Colin Perkins http://csperkins.org/
_______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Re: [P2PSIP] P2PSIP diagnostics: PING discussion Das, Saumitra
- RE: [P2PSIP] P2PSIP diagnostics: PING discussion Roni Even
- RE: [P2PSIP] P2PSIP diagnostics: PING discussion Song Haibin
- RE: [P2PSIP] P2PSIP diagnostics: PING discussion Das, Saumitra
- Re: [P2PSIP] P2PSIP diagnostics: PING discussion Colin Perkins
- Re: [P2PSIP] P2PSIP diagnostics: PING discussion Bruce Lowekamp
- RE: [P2PSIP] P2PSIP diagnostics: PING discussion Song Haibin
- Re: [P2PSIP] P2PSIP diagnostics: PING discussion Bruce Lowekamp