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

Olafur Gudmundsson <ogud@ogud.com> Sun, 01 December 2013 20:53 UTC

Return-Path: <ogud@ogud.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C22391AE134 for <dhcwg@ietfa.amsl.com>; Sun, 1 Dec 2013 12:53:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FzuK9m1R25Nr for <dhcwg@ietfa.amsl.com>; Sun, 1 Dec 2013 12:53:10 -0800 (PST)
Received: from smtp82.ord1c.emailsrvr.com (smtp82.ord1c.emailsrvr.com [108.166.43.82]) by ietfa.amsl.com (Postfix) with ESMTP id 5F4361AE10E for <dhcwg@ietf.org>; Sun, 1 Dec 2013 12:53:10 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 4E179500B1 for <dhcwg@ietf.org>; Sun, 1 Dec 2013 15:53:08 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id 1895D50099 for <dhcwg@ietf.org>; Sun, 1 Dec 2013 15:53:08 -0500 (EST)
From: Olafur Gudmundsson <ogud@ogud.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9D48D309-64DE-49CB-9E7C-220A0996C352"
Date: Sun, 1 Dec 2013 15:53:07 -0500
References: <20131201204227.7978.2067.idtracker@ietfa.amsl.com>
To: dhcwg@ietf.org
Message-Id: <83842BD2-0261-472F-9CA1-AFBFB47EAD91@ogud.com>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Subject: [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 01 Dec 2013 20:53:13 -0000

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: internet-drafts@ietf.org
> 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 <ogud@ogud.com>
> 
> 
> 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
>