Ask Bjørn Hansen wrote:
Anyway, please read the "For Vendors" document I wrote before
replying:
http://www.pool.ntp.org/vendors/
Another thing that occurs to me is whether there should be some mention
of the use of DHCP to distribute the names of NTP servers.
The DHCP RFC (RFC2132, at http://www.ietf.org/rfc/rfc2132.txt) specifies
option 42 as being a list of NTP servers.
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.
Martin
--
Martin Radford ([EMAIL PROTECTED])
Personal Computer Systems Team
Information Systems & Computing
University of Bristol Information Services
PGP keyID: 5D2D92E9
PGP fingerprint: 137E 0277 9D78 7447 71D0 BB3D C20D BB9A 5D2D 92E9
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
