Re: Predictable Internet Time

Nico Williams <nico@cryptonector.com> Tue, 18 April 2017 22:20 UTC

Return-Path: <nico@cryptonector.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 A54C31314B0 for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 15:20:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.8
X-Spam-Level:
X-Spam-Status: No, score=-4.8 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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.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 rLl8vZKibh5l for <ietf@ietfa.amsl.com>; Tue, 18 Apr 2017 15:20:09 -0700 (PDT)
Received: from homiemail-a109.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C9961314B2 for <ietf@ietf.org>; Tue, 18 Apr 2017 15:20:09 -0700 (PDT)
Received: from homiemail-a109.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a109.g.dreamhost.com (Postfix) with ESMTP id 16F2D20047604; Tue, 18 Apr 2017 15:20:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=s6oZFVLaxO4tlb dhzvOvhYQWynA=; b=jgC0vcfjGO4GdnUzbf7XklH1h+zEXQ7LIzUmp7wqPWWwtm Je5L7BOQjatY2PPAZwflJbZlOEBaT4S0j6RPkOJy60zrzvWSzf9/f9lNd9w6LF0O pzXT5sgGxlmj7YQmrzJB2jaqukeu68sHU5FxquQPLiOspOQH1Dm1cYXW4pk5o=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a109.g.dreamhost.com (Postfix) with ESMTPSA id A24E020047603; Tue, 18 Apr 2017 15:20:08 -0700 (PDT)
Date: Tue, 18 Apr 2017 17:20:06 -0500
From: Nico Williams <nico@cryptonector.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>, IETF Discussion Mailing List <ietf@ietf.org>, Patrik =?iso-8859-1?B?RuRsdHN0cvZt?= <paf@frobbit.se>
Subject: Re: Predictable Internet Time
Message-ID: <20170418222004.GB2856@localhost>
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> <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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAMm+LwjQ_kaSBzcJhem5CbPLvMCAJRFnRpqJgu8SFTTQpt4bzQ@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2R5ab1461YSw0U9LJiXIdT25ySo>
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: Tue, 18 Apr 2017 22:20:11 -0000

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