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

Warner Losh <imp@bsdimp.com> Mon, 02 December 2013 20:09 UTC

Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC5321ADF56 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 2 Dec 2013 12:09:27 -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 MfAqEdqXzQX7 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 2 Dec 2013 12:09:26 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 03B0F1ADF52 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 2 Dec 2013 12:09:26 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 000D286DAD7 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 2 Dec 2013 20:09:23 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id EB44086D422 for <ntpwg@lists.ntp.org>; Mon, 2 Dec 2013 20:09:17 +0000 (UTC)
Received: from mail-ie0-f175.google.com ([209.85.223.175]) by mail1.ntp.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <imp@bsdimp.com>) id 1VnZnv-000FYt-0O for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 20:09:17 +0000
Received: by mail-ie0-f175.google.com with SMTP id x13so21321603ief.20 for <ntpwg@lists.ntp.org>; Mon, 02 Dec 2013 12:09:09 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=nD9qyZRQWP+8a0aK7r3rOhfixl0Br4i8b0ZCbbROZ5g=; b=UjaE3uRzHC7InQy/AZlex8Bm6JSfmblmvCn/EWGIDoymmljHzhkmQ/hpJG5zBmO3iu vmADI3feIGC6EFGhFWRWMl2uDptVXSQo5MZ9YwNaFP6naWKFJaOdC1Vzq/KywTBi5m3X EkR3HFvWLFVaibL6nbKoy+tUocSLGqO0cAjt6o3Pl1FmSrPZpd7lVBycudV+USGLzfn2 lXYPjwa780PBymQ6rdCT6gm9LQeeiSDL9U9AavRVncLXrnVqvXkCgL0sstlH/QWi8yfV Wo+gS6+h3fzwkcpye+MH5JTZAjZCbot9znwFfGJxeqSlZ2YM1apm7O5obN3MhhBEBE+s b4sA==
X-Gm-Message-State: ALoCoQm+FTgTPRchdVDhnUjOibkg6EuJoRkjNLq7mzemFPSccpxTv5oWsn6u/F7DGUHagr1RnhdA
X-Received: by 10.50.30.66 with SMTP id q2mr19728670igh.17.1386014949269; Mon, 02 Dec 2013 12:09:09 -0800 (PST)
Received: from fusionlt2834a.int.fusionio.com ([209.117.142.2]) by mx.google.com with ESMTPSA id j16sm67621228igf.6.2013.12.02.12.09.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Dec 2013 12:09:08 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
From: Warner Losh <imp@bsdimp.com>
In-Reply-To: <E1VnZdi-0000fA-CY@stenn.ntp.org>
Date: Mon, 02 Dec 2013 13:09:06 -0700
Message-Id: <220ED02D-AE73-436F-A81F-BDF54611173B@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> <E1VnZdi-0000fA-CY@stenn.ntp.org>
To: Harlan Stenn <stenn@ntp.org>
X-Mailer: Apple Mail (2.1085)
X-SA-Exim-Connect-IP: 209.85.223.175
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: imp@bsdimp.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.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: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Dec 2, 2013, at 12:58 PM, Harlan Stenn wrote:

> 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/ .

Actually, in all those cases it is within a second of the 'real' time, hence specifying that it should be one second or the other seems appropriate. The timestamp APIs are for sub-second resolution, while the time_t in this protocol has only a second resolution... The main point is that it should be (a) specified to be what's going to most likely happen (or keep bounds on the error)  and (b) something sane that doesn't introduce errors > tolerance of the protocol. Having it be completely unspecified is a mistake, since -1 could be returned...

Warner

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg