Simon Arlott a écrit : > On 11/08/06 23:26, Guillaume Filion wrote: >> Rob Janssen a écrit : >>> This includes not only the database of pool members, but also the >>> uptodate reachability information, the recent history of replies sent >>> to users, the source network of the query, etc. >> I'm not sure about "the recent history of replies sent to users" though. >> >> My prototype would respond to 0.pool.ntp.org with the closest server, >> 1.pool.ntp.org the 2nd closest, up to 5.pool.ntp.org. > > But the replies are the same for each source network, so you'd be directing > an entire ISP to the closest server even if there are 5 or more pool servers > run by customers of that ISP.
You have a good point. I'm not sure of the best way of solving that, using a small history list might be a good way of solving it, or maybe hashing the IP address like OpenBSD's pf is doing for load balancing. (http://www.openbsd.org/faq/pf/pools.html) Given that DNS servers are caching the data that we're returning to them, the behavior would be pretty hard to predict without empirical data -- at least for me. Anyway, I think that should be taken care of in optimization. You know the saying: Make it work first, Optimize later. Best, GFK's -- Guillaume Filion, ing. jr Logidac Tech., Beaumont, Québec, Canada - http://logidac.com/ PGP Key and more: http://guillaume.filion.org/
signature.asc
Description: OpenPGP digital signature
_______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
