Martin Radford wrote:
[ ... ]
Where a device is getting its IP address by DHCP (as is probably common
with the type of devices we're considering here), then if that DHCP
response includes a list of NTP servers, the device should use those in
preference to a built-in default.
In addition, it would be nice if devices that have built-in DHCP
*servers* (e.g. home "broadband routers") could also have built-in NTP
servers and distribute their own IP address to their clients as an NTP
server via DHCP. This should result in "good enough" time being
distributed right down the tree at relatively little load on public NTP
servers (including the pool servers).
This is probably outside the scope of this specific document, though,
but possibly could be made into a separate "good practice" document.
These are +1 by me.
I think we should put together as many good thoughts like these as we can,
update RFC-4330 with them, and keep pointing Linksys, D-Link, Cisco, and certain
Linux distros at the spec until their products do not abuse public NTP server
resources by default.
--
-Chuck
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
