On 4/24/06, Simon Arlott <[EMAIL PROTECTED]> wrote: > You could always allow ISPs to override an "isp.pool.ntp.org" hostname...
Wouldn't that still require end-user configuration? Incorrect end-user configuration is the reason NIST's servers and other popular stratum-1s get crushed with 5 Mbps or more of NTP traffic. End users can't be expected to reliably figure out that "Qwest is my ISP, so I should use qwest.pool.ntp.org", and then figure out what buttons to press or which configuration file to edit to make that change correctly. Building intelligence into the DNS infrastructure of pool.ntp.org would seem to be the best long-term solution my mind. I personally believe intelligent DNS would enable the pool to efficiently handle the most traffic, provide the best time, and lessen the impact of mis-configurations by vendors and end users. Of course, as discussed here previously, building an intelligent DNS system that would handle the pool is not a trivial undertaking. Both geography and netowrk topology need to be taken into account, and getting accurate geographic data is not free at the moment. Regards, -- RPM _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
