Re: Predictable Internet Time

Eliot Lear <lear@cisco.com> Tue, 03 January 2017 06:43 UTC

Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D153129432 for <ietf@ietfa.amsl.com>; Mon, 2 Jan 2017 22:43:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.622
X-Spam-Level:
X-Spam-Status: No, score=-17.622 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 SVjVpHTQIkrm for <ietf@ietfa.amsl.com>; Mon, 2 Jan 2017 22:43:29 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC6F6129434 for <ietf@ietf.org>; Mon, 2 Jan 2017 22:43:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3552; q=dns/txt; s=iport; t=1483425809; x=1484635409; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=a1G+zNVy+noqkxW+ArpmTMuCK6zkK/ssixKEsDGb9nY=; b=cnFgJC3K9VYQfJynx5zxkcqlvXZJO7A1z79ErL8IDZXB/24AReDrDODL klKXPCJlm/8IRl34vSJ432TIv2BzYGZTLgX/+/qgzMEIbm30BVGLB/mFM Upstr2PGROHjG0wU5VTrXdVMuPOMVnFVsYXNZCpPnqal/Hut7JRVxYmz0 A=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CTAgCUR2tY/xbLJq1eDgsBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYM3AQEBAQGBAY9Sk1OXI4YiAoIhEQECAQEBAQEBAWIohGkBBSN?= =?us-ascii?q?WEAsYFRUCAlcGAQwIAQGIbK8FgiWKOgEBAQEBAQEBAQEBAQEBAQEBAREPiEeCX?= =?us-ascii?q?4UFgkWCXQWafYNkgX2LXYokhjGSPTUigQcWDYQRHIEjPD2JGwEBAQ?=
X-IronPort-AV: E=Sophos;i="5.33,451,1477958400"; d="asc'?scan'208";a="648450483"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jan 2017 06:43:07 +0000
Received: from [10.61.173.204] ([10.61.173.204]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v036h65m020236; Tue, 3 Jan 2017 06:43:06 GMT
Subject: Re: Predictable Internet Time
To: =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>, Joe Touch <touch@isi.edu>
References: <CAMm+LwgfQJ8aG5wB=d3fRbbeje3J9o7Z4_DCuP8DL88ouDeKzw@mail.gmail.com> <504e2cea0d1668c31486b05fec0a967a4446aefe@webmail.weijax.net> <CAMm+Lwi_jU6gjdtdM6a2n_9_89tUvWBNXxnMtSjTEA++h1D4Ew@mail.gmail.com> <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <B990A5A4-D62B-4E10-9FF7-7BA4377C0958@frobbit.se>
From: Eliot Lear <lear@cisco.com>
Message-ID: <7bc1a350-549c-c649-81c6-bcd19cff36d7@cisco.com>
Date: Tue, 3 Jan 2017 07:43:05 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.6.0
MIME-Version: 1.0
In-Reply-To: <B990A5A4-D62B-4E10-9FF7-7BA4377C0958@frobbit.se>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="jgL0qW7DlXlmrs0ncgFppogh54nwrnWN3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PJ-Y-F7OidJIOJXHeCZmyIHcrRA>
Cc: Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jan 2017 06:43:30 -0000

Good morning, Patrik,


On 1/3/17 7:29 AM, Patrik Fältström wrote:
> I think personally, as long as we do have leap seconds:
>
> - we should have the leap second information available somewhere in clear machine readable format. Some suggestions exists, including encoding it in A-records in DNS ;-)
>
> - we should look at having the time since epoch really be the number of SI-seconds since the epoch
>
> - we should have translation between number of seconds and UTC take leap seconds into account

The TZDB at IANA contains the file "leapseconds" which is machine
readable, and provides a history of all leapseconds.  This provides you
the 1st and 3rd of your requirements.
> - we should fix the code that do not accept 61 seconds in a minute
>
> Now, we can also say we should stop having leap seconds, but I feel that is a _different_ matter and different discussion. I am myself not clear over what is the correct thing regarding leap seconds.
>
> What I am sure of is that I think most of the problems we have is because of bad programming (including in old UNIX days the priorities although correct at the time have continued to let the time_t definition continue to be wrong).

I'm of two minds as well.  On the one hand, the current system makes it
quite easy to do the wrong thing, and that's not good.  There are
utility functions such as pytz's normalize() and localize() functions
that people just don't know about, for instance.  On the other hand,
it's not just leap seconds.  It's timezones in general, it's DST
transitions, etc.  Getting rid of leap seconds only marginally improves
things, and gets really philosophical really quickly...

Eliot