Hi Rob, On Sun, Feb 19, 2017 at 06:49:38PM +0100, Rob Janssen wrote: > That way the customers of some ISP could be directed to the > timeservers provided by that ISP, and similar for other networks > that have good timeservers and a DNS resolver.
How would you distinguish ISPs with "good timeservers" from ones with unreliable timeservers, where I (as a customer of that ISP) will specifically want to avoid their servers and prefer the pool only? If I know enough to configure an NTP client then I am going to select pool servers and my ISP's servers, knowing that NTP's selection algorithm should rescue me if my ISP's servers go bad. I do not then want the pool to bias towards my ISP's servers. If an ISP was concerned about NTP traffic leaving their network then they could provide their own NTP servers. Assuming they end up performing better than the average pool server -- which they should as there's going to be a lot less latency to their own customers than between rest of Internet and own customers -- then more of the traffic should stay on-net. Cheers, Andy _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
