[dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt

[Olafur Gudmundsson <[e-mail]>]

Hi, 

I wrote up this short document in order to address a problem seen in certain devices
that do not have good time at startup. The document  proposes a DHCv4 option and
DHCPv6 option to supply current time to a device. (there is also a proposed ND option
for the same thing). 

I looked into using option 152 from Bulk Query but that is only 32 bit long, and 
it seems cleaner to just get a 64bit time_t option into DHC

Comments please 

	Olafur


Begin forwarded message:

> From: [e-mail]
> Subject: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
> Date: December 1, 2013 3:42:27 PM EST
> To: Olafur Gudmundsson <[e-mail]>
> 
> 
> A new version of I-D, draft-ogud-dhc-udp-time-option-01.txt
> has been successfully submitted by Olafur Gudmundsson and posted to the
> IETF repository.
> 
> Filename:	 draft-ogud-dhc-udp-time-option
> Revision:	 01
> Title:		 Providing Time over DHCP and ND for devices w/o reliable clock upon boot
> Creation date:	 2013-12-01
> Group:		 Individual Submission
> Number of pages: 7
> URL:             http://www.ietf.org/internet-drafts/draft-ogud-dhc-udp-time-option-01.txt
> Status:          http://datatracker.ietf.org/doc/draft-ogud-dhc-udp-time-option
> Htmlized:        http://tools.ietf.org/html/draft-ogud-dhc-udp-time-option-01
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-ogud-dhc-udp-time-option-01
> 
> 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.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
>