I think 4(c) might be confusing, or contradictory, for those using a "well-behaved" NTP client (e.g. ntpd):
4. End-User agrees that he or she will not: (c) Set the time more often than is necessary for the purposes of the device; if the device can keep reasonably accurate time for several days, End-User will not set the time every hour. Additionally, if the device only uses whole seconds, End-User will not optimize the device for millisecond accuracy. While 4(a) seems to imply the default settings for an NTP daemon are good, 4(c) suggests otherwise: I know my machines can keep reasonably accurate time for several days, but by default, maxpoll is well more than once per hour (1024 seconds?). Then again, "set the time" implies that an NTP daemon is NOT being used. But that could be made explicit (as it is for 4(a) and 4(b)). Something that might be worth adding: time service is only available via NTP (insert specific version or RFC reference if desired) on the standard UDP port. Attempts to connect to other ports or services (HTTP, legacy port 13 or 37 time, whatever) will result in unpredictable and undesirable behavior. I also agree with Rob's input about integrators/distributors gone wild. And, in general, I approve of these TOS :-) -rt On Fri, Aug 30, 2013 at 4:08 AM, Ask Bjørn Hansen <[email protected]> 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 -- Ryan Tucker <[email protected]> _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
