Colin,
In the p2psip diagnostics draft, we also say that we use the "NTP format"
time.
Best Regards,
Song Haibin
Email: melodysong(_at_)huawei(_dot_)com
Skype: alexsonghw
_____
From: p2psip-bounces(_at_)ietf(_dot_)org
[mailto:p2psip-bounces(_at_)ietf(_dot_)org] On Behalf Of
Colin Perkins
Sent: Friday, November 14, 2008 3:34 AM
To: Roni Even
Cc: p2psip(_at_)ietf(_dot_)org; ietf(_at_)ietf(_dot_)org
Subject: Re: [P2PSIP] P2PSIP diagnostics: PING discussion
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(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf