On 7/17/06, Karel Sandler <[EMAIL PROTECTED]> wrote:
From: "Ryan Malayter" <[EMAIL PROTECTED]>
This ~2 ms systemic offset is invisible by the pool because its clients use
your 1500/256 in the opposite direction. Nevertheless, I think that it's a
pity that upstream servers can't be fudged in NTPv4.
Not every client connection is the same, so we can't count on the
asymmetry canceling itself out.
My cable connection in the US is 6000/256, which results in a 15%
larger systemic offset than 1500/256. I also use us.pool.ntp.org from
my laptop with a mobile wireless card, which is something like 1000/96
(an offset > 6 ms, not that anything better is needed on my laptop).
I suppose I'm just bothered - in an intellectual, obsessive-compulsive
way - by all the DSL-based pool servers out there advertising
stratum-2 but serving up time with multi-millisecond phase errors.
Especially when those errors are easy to calculate and correct.
As mentioned before, it doesn't matter much for the accuracy of pool
clients, which have phase errors on the order of tens of milliseconds
in many cases. But perhaps we should suggest those on slower DSL
connections fudge the stratum of their servers down to "announce" this
systemic error in some way, so that nobody tries to use one of the
DSL-based pool servers for a more sensitive application by "accident".
--
RPM
=========================
All problems can be solved by diplomacy, but violence and treachery
are equally effective, and more fun.
-Anonymous
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
