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

Harlan Stenn <stenn@ntp.org> Mon, 02 December 2013 20:01 UTC

Return-Path: <stenn@stenn.ntp.org>
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 06ABB1ADEB4 for <dhcwg@ietfa.amsl.com>; Mon, 2 Dec 2013 12:01:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 iHoAVBxwqaoO for <dhcwg@ietfa.amsl.com>; Mon, 2 Dec 2013 12:01:44 -0800 (PST)
Received: from stenn.ntp.org (stenn.ntp.org [149.20.68.30]) by ietfa.amsl.com (Postfix) with ESMTP id 7917C1ADF4B for <dhcwg@ietf.org>; Mon, 2 Dec 2013 12:01:34 -0800 (PST)
Received: from localhost.ntp.org ([::1] helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1VnZdi-0000fA-CY; Mon, 02 Dec 2013 19:58:42 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Warner Losh <imp@bsdimp.com>
In-reply-to: <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org> <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com>
Comments: In-reply-to Warner Losh <imp@bsdimp.com> message dated "Mon, 02 Dec 2013 08:32:02 -0700."
X-Mailer: MH-E 7.4.2; nmh 1.5; XEmacs 21.4 (patch 22)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Content-Type: text/plain; charset=US-ASCII
Date: Mon, 02 Dec 2013 19:58:42 +0000
Message-Id: <E1VnZdi-0000fA-CY@stenn.ntp.org>
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [dhcwg] [ntpwg] 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: Mon, 02 Dec 2013 20:01:46 -0000

Warner Losh writes:
>>> The reason for time_t is the dhcp-client can feed that directly into
>>> following call: settimeofday(const struct timeval *tp, const struct
>>> timezone *tzp)
> 
> During a leap second, the value of time_t is not well defined because
> by definition leap seconds don't happen in time_t/POSIX time scale
> (don't happen -- well don't consume space in the time_t timescale is
> more pedantically correct). Obscure point likely worth noting...  But
> using a NTP time stamp doesn't save you, since during a leap second
> its value is well defined, but the same as another second (ntp
> distinguishes in bits set in other parts of the header). Assuming the
> tolerance for this application is >> 1s, this won't matter, but might
> be worth specifying that during a leap second, the value returned
> shall be either the value of the prior second or the value of the next
> second to make it conform to most current usage.

It's actually fuzzier than that, and this situation (which is handled
differently with ntpd under unix, ntpd under windows, and on systems
that "smear" the leap second over a longer period) is one of the cases
handled by the General Timestamp API project at Network Time Foundation,
described at http://nwtime.org/projects/timestamp-api/ .

H