Re: [Ntp] I-D Action: draft-ietf-ntp-using-nts-for-ntp-27.txt

[Hal Murray <[e-mail]>]

> >>> No, clients may switch between servers when they become unreachable
>>>> (e.g. due to rate limiting). I see this often with my mini-pool of NTS
>>>> servers.

>>> Oh really, I didn’t know. So chrony does that? (Nice!)
>> I think most NTP and SNTP clients do that.

> Right, SNTP most likely. But NTP? Oh well. 

In pool mode, yes.

With the current pool, there is no way to ask "Is this site still in the pool?"
(There isn't a clean way to turn off traffic when you remove a site from the 
pool.)

It makes sense when a site stops responding to go through the DNS step again 
and try a new server.

It would also make sense for sites that are up 24/7 to do something like once 
a day, scan the list of pool servers currently in use and kick out the worst 
one and try a new one.  The idea is to gradually pick servers that are better, 
probably nearer, but distance measured in network performance rather than 
kilometers.


-- 
These are my opinions.  I hate spam.