> That's all well and good, but how do know that Vendor XYZ is going to > "behave". I think if a vendor wants to deploy a large amount of NTP > devices they should have their own XYZ.pool.ntp.org dns entry. That > gives the vendor, and us more control of how and where those packets go.
IMHO: The vendors we have to worry and complain about are the ones that misbehave both technically (i.e. boneheaded client software) AND administratively (by not requesting a subdomain). After that we should worry about the ones that met the administrative rules but are using boneheaded software. The vendors that use well behaved software but didn't register a subdomain? We won't ever notice them as a problem. We could run a statistical report and find them that way, but the same statistical report would also reveal that they have very conscientious usage patterns. The gotcha is, all people who use boneheaded NTP clients by definition don't realize how boneheaded their NTP client is. Outside of ntpd, the standards are ridiculously and sadly low. We could just expect the worst out of every vendor but really lots of them do make intelligent and conscientious choices. Tim. _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
