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

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

Return-Path: <imp@bsdimp.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 42CE41AD73F for <dhcwg@ietfa.amsl.com>; Mon, 2 Dec 2013 10:13:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 87Ltki_yO_eP for <dhcwg@ietfa.amsl.com>; Mon, 2 Dec 2013 10:13:02 -0800 (PST)
Received: from mail-ie0-f181.google.com (mail-ie0-f181.google.com [209.85.223.181]) by ietfa.amsl.com (Postfix) with ESMTP id 8AA171AD8F3 for <dhcwg@ietf.org>; Mon, 2 Dec 2013 10:13:02 -0800 (PST)
Received: by mail-ie0-f181.google.com with SMTP id e14so20811581iej.26 for <dhcwg@ietf.org>; Mon, 02 Dec 2013 10:13:00 -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=cfYwbFBhUBk+5kYSFEOqd73pn2n2nOvfZ+S7Tc8+O7A=; b=czj7pICTqG2zyhWPDZsOjdw4TIqGi/zWmBdYsZykWcXupMFThFkv+H8bbDGwxdEQxm 43TdtbyaPvbRyikMgbx2vDbY1L2Na1sI3gXQSUt1J1rarFZWAiJyG5EGHRt8OPrnW/SI fejhuzPqwpzuQ3wQ3ohWSllDpfRmSGID8elRlli/JHCo9WxZHT+7+yf3hXqnbtF5w+1A Y0CK6uF5unvv6KfI+MuU4g3YHp1Xwh68mDjk9ydHvdPSZxVTzOh454JIZke9d/4sIwKu BybfMAriUyzCrNuIm1hNiYcxsLlGJZBACK36Vh9yQzwQonOknnlK+EEGTvr9lKHhUDdg AafQ==
X-Gm-Message-State: ALoCoQmFODEIy4iYDSPvtd5DyilmVYgFtJPWtaQFvJqYJ97AlgeCfD1Vbhjhqnci/Ip+gVRpvbav
X-Received: by 10.42.42.132 with SMTP id t4mr1929976ice.90.1386007980059; Mon, 02 Dec 2013 10:13:00 -0800 (PST)
Received: from fusionlt2834a.int.fusionio.com ([209.117.142.2]) by mx.google.com with ESMTPSA id x5sm67786946iga.6.2013.12.02.10.12.59 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Dec 2013 10:12:59 -0800 (PST)
Sender: Warner Losh <wlosh@bsdimp.com>
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Warner Losh <imp@bsdimp.com>
In-Reply-To: <4AA650D3-2AD2-4C83-8450-DC3926AC9416@nominum.com>
Date: Mon, 2 Dec 2013 11:12:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7C1A1F32-EED7-4990-A550-DB66BAB6AAD4@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> <4AA650D3-2AD2-4C83-8450-DC3926AC9416@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1085)
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, "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 18:13:04 -0000

On Dec 2, 2013, at 10:12 AM, Ted Lemon wrote:

> On Dec 2, 2013, at 10:32 AM, Warner Losh <imp@bsdimp.com> wrote:
>> 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.
> 
> I think the expectation is that the time will be updated with a more accurate mechanism later, and an error of 1s is not worth worrying about for typical devices, so this is almost certainly overkill.

This isn't to prevent an error of a second, but to bound the error to a second by adopting the main work arounds that are in practice today which do that.

Warner