Hi, Am 20.02.2017 um 14:03 schrieb Andy Smith: > Hi Rob,
> 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 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. Maybe this and the load issues on the DNS servers could both be resolved by allowing ISPs to get their own vendor zone style ISP zone - like for example "dtag.de.pool.ntp.org" and the ability to prefer their own servers in this zone. As a customer I still would be able to distinguish between the ISPs NTP servers and the public pool. The ISPs servers should then of course need to be monitored like all the other servers and if the ISPs servers are unresponsive or returning unrealiable time, the public pool servers would rush into the ISP zone. And maybe there could be a nice feature for an ISP to maintain a list of known very good connected and "known to have problems" AS numbers to other networks, so the public servers in the ISP zone could be ordered based on this preference list to provide a low-latency time source for this ISPs customers. Greetings Max
signature.asc
Description: OpenPGP digital signature
_______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
