Re: Predictable Internet Time

Joe Touch <touch@isi.edu> Fri, 21 April 2017 16:11 UTC

Return-Path: <touch@isi.edu>
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 DB7DE129481 for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 09:11:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
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 Jj9ftNgLeC7r for <ietf@ietfa.amsl.com>; Fri, 21 Apr 2017 09:11:22 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 782B512960D for <ietf@ietf.org>; Fri, 21 Apr 2017 09:11:22 -0700 (PDT)
Received: from [128.9.184.96] ([128.9.184.96]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id v3LGA4Ho017648 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 21 Apr 2017 09:10:05 -0700 (PDT)
Subject: Re: Predictable Internet Time
To: Toerless Eckert <tte@cs.fau.de>, Nico Williams <nico@cryptonector.com>
Cc: Patrik F?ltstr?m <paf@frobbit.se>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>, Paul Eggert <eggert@cs.ucla.edu>
References: <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> <7bc1a350-549c-c649-81c6-bcd19cff36d7@cisco.com> <B2E6846E-F25B-4792-8E13-B5D898B67223@frobbit.se> <9f719b6a-f3c0-ef98-1636-86e84106e366@cisco.com> <16db07fe-acc5-d178-b56c-755c3cf70680@cs.ucla.edu> <CAMm+LwjQ_kaSBzcJhem5CbPLvMCAJRFnRpqJgu8SFTTQpt4bzQ@mail.gmail.com> <20170418222004.GB2856@localhost> <20170418232126.GD5937@faui40p.informatik.uni-erlangen.de>
From: Joe Touch <touch@isi.edu>
Message-ID: <1bd9112d-091b-7889-633a-69e2137b8ca0@isi.edu>
Date: Fri, 21 Apr 2017 09:10:02 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <20170418232126.GD5937@faui40p.informatik.uni-erlangen.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/18sAG48Vt2NrUw7qO2BXFdzjwls>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 21 Apr 2017 16:11:24 -0000

Hi, all,

Again, this discussion is continuing over in ART at the advice of the IESG.

I'll post followups there.

Joe


On 4/18/2017 4:21 PM, Toerless Eckert wrote:
> Nice!
>
> Why not start to tackle the problem pragmatically before asking for standards
> when its clearly a political issue.
>
> a) RFC describing the problems developers and system deployments can face
>   because of leap seconds.
> b) And best current practices to get around those issues. Eg: Expect clock
>   smear on Jan 1 == reduced accuracy of ~1. Unless OS or other trusted
>   info source gives explicit indication: NO leap, no smear.
> c) And finally a description of the worst open issues when b) is applied.
>    Anything worse than labels on products "reduced functionality on Jan 1
>    after a leap second" ?
>
> Cheers
>     Toerless
>
> On Tue, Apr 18, 2017 at 05:20:06PM -0500, Nico Williams wrote:
>> On Tue, Jan 03, 2017 at 05:34:11PM -0500, Phillip Hallam-Baker wrote:
>>> As I said, I want 30-100 years lead time so I can bake the schedule into
>>> devices and remove a trust dependency.
>> 30 years' lead time for leap seconds?  Can't be done.
>>
>> Leap seconds depend on events such as earthquakes.
>>
>> You can estimate their frequency, but you can't estimate when they'll be
>> inserted.
>>
>> Nico
>> --