I agree with Brad; if we only care about 1 second accuracy, we should
drop all of the sub-zones. However, if we are going to keep the country
zones, they need fixing.
The Mexican zones illustrate a real problem. At the moment, there are
only two pool servers in Mexico. If you lookup mx.pool.ntp.org or any of
[012].mx.pool.ntp.org, you get exactly the same two servers. Thus, a
client using [012].mx.pool.ntp.org will be unable to detect a single
false ticker. This is not a good situation.
I think the fundamental problem with the current country zones is that
they contain *servers* in a given country; they should contain servers
that are useful for *clients* in a given country.
So, I'd say the first thing we should do is create zones for all countries.
Then, how do we populate them? Let's consider Mexico again. Ideally
0.mx.pool.ntp.org should contain one of the Mexican servers,
1.mx.pool.ntp.org should contain the other, and 2.mx.pool.ntp.org should
contain a random North American server.
However, the ideal solution might be an awful lot more work for Ask. A
more reasonable approach might be to populate a country zone from
servers in that country if the country has more than N (N=10?) servers
and populate the country zone from the global zone otherwise.
Oh, and if we are going to keep the country zones, there really should
be an explicit fourth zone (i.e., 3.xx.pool.ntp.org) for each country.
Regards,
Alan
--
Dr Alan Watson
Centro de Radioastronomía y Astrofísica
Universidad Astronómico Nacional de México
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
