Providing Time over DHCP and ND for devices w/o reliable clock upon boot
draft-ogud-dhc-udp-time-option-01

Document Type Expired Internet-Draft (individual)
Author Ólafur Guðmundsson 
Last updated 2014-06-04 (latest revision 2013-12-01)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ogud-dhc-udp-time-option-01.txt

Abstract

Many small inexpensive computing devices like home routers, Rasberry Pi etc. do not have a battery to allow clock chip to keep track of time, thus the systems have no idea what the current time is upon boot. Number of modern services take Time Synchronization for granted, but operating systems do not allow the start of these services to be deferred until after accurate clock has been confirmed. NTP provides accurate fine grain clock synchronization but in order for NTP to succeed DNS needs to work. DNSSEC resolvers will fail if system clock is off by more than little bit. This draft proposes a mechanism to offer "reasonable" current time to devices upon boot via DHCP, DHCPv6 and ND.

Authors

Ólafur Guðmundsson (ogud@ogud.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)