i think a TOS for the pool that end users have to see and accept would be
fundamentally detrimental to the pool's mission, and would do it a
disservice. as it is now, the pool is "just there". its main userbase are
people who don't know what NTP is, or what the pool is, and their clock is
"just" kept synched by ntp software in their distro, etc. it should remain
this way.
IMO, the pool's main target for this TOS kind of rules is not those end
users. rather, it's developers of software (PC, embedded, and so on) which
uses the pool by default. these developers absolutely need to make sure they
use the pool correctly.
i think it makes a lot of sense to sue the developer or perhaps distributor
of an abusive client, and also no sense to sue its end users.
power users, who configure their own setup to use the pool, manually, could
be seen as another group who need to see the TOS, but i think they make up
such a small minority of the pool's traffic that it's not worth considering
them.
instead of a TOS that every user has to agree on, it should perhaps be a TOS
to be agreed on by software developers who want to use the pool by default,
and a mere recommendation for everyone else.
also, the pool already has a mechanism in place to deal with problematic
software: the "distro pool" DNS names, which can be blocked as needed. as
long as software uses those.
On 2013-08-30 10:08, Ask Bjørn Hansen wrote:
Hi everyone,
The website now has a terms of service document for how to use the NTP Pool --
http://www.ntppool.org/tos.html
The main points are about not configuring syncing in a dumb way (top of the
hour, too frequent, etc) and that the service is provided as-is -- don't use it
for anything where correct time is business- or life-critical.
Ask
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
_______________________________________________
pool mailing list
[email protected]
http://lists.ntp.org/listinfo/pool
