>> I agree re. s/p - the meaning here isn’t immediately obvious from the
>> name, I have to look them up when I want to figure out which to use. I
>> note that both s2 and p2 point to ntp3 - is that intentional, or should
>> only s2 point to ntp3? Out of interest, what do s/p actually stand for?
>
> Looking at the AUP I always presumed that the differentiation between
> s2/3/4 and p1/2/3 was to allow future differentiation between 'classes' of
> client. This doesn't seem like a bad idea, even if (currently) they wind
> up going to the same place(s).

Looking at the AUP, I'd always through the p* and s* referred to primary and secondary.  Re NTP, primary is 'important gear' (- needed for billing\ security\ logs), secondary is a 'nice to have' (- doesn't strictly matter if NTP not functional).  There's also mention of server load in the AUP, so if the load being received got out of hand, then any requests to the 'secondary' hosts could be null routed, to ensure availability\access for 'primary' systems.



Paul Adshead