Re: Predictable Internet Time

Nico Williams <nico@cryptonector.com> Wed, 29 March 2017 15:45 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 7DF0A126557 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 08:45:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.796
X-Spam-Level:
X-Spam-Status: No, score=-4.796 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.796] 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 DnvYqSAyKcFt for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 08:45:42 -0700 (PDT)
Received: from homiemail-a31.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 DF5FA1292C5 for <ietf@ietf.org>; Wed, 29 Mar 2017 08:45:42 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTP id 5738E1406B21; Wed, 29 Mar 2017 08:45:42 -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=d97V1mW3Mta629 qPVopkdbSCL3Y=; b=bUm9IfF/b9BvKVw9lZbhVxWqdO4W+Hxj3mEvBdVmR0a6pW rx5ubfmIBnPzCgsijbqyFa4Q9llOTOQzcoJdAPVjg1C5iJPWpWKpwYKzMPUIFWyw mGVShYIskCdYhifab6Hm4XPdEqBfWKzt6KMvK0BOFnQzVpXeCgstqwmApHqgw=
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-a31.g.dreamhost.com (Postfix) with ESMTPSA id 53A0F1406B20; Wed, 29 Mar 2017 08:45:40 -0700 (PDT)
Date: Wed, 29 Mar 2017 10:45:37 -0500
From: Nico Williams <nico@cryptonector.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Cc: Cyrus Daboo <cyrus@daboo.name>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Predictable Internet Time
Message-ID: <20170329154536.GQ7490@localhost>
References: <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <alpine.DEB.2.11.1701031348430.7102@grey.csi.cam.ac.uk> <0bbfcd7c-11a7-0e7f-56f7-eee959b7a947@gmail.com> <CAMm+Lwi0sQyRE_2dMCkwTk7xTiK2JbHhHSPYMkdG2FeBw_6CNA@mail.gmail.com> <7BDE58D23ADF3BC046F8942D@caldav.corp.apple.com> <b27515e2-a36a-7bf2-0ca4-1fae31a9dc21@gmail.com> <04DD5DFCB528DCD404C81F78@caldav.corp.apple.com> <A193D619-7B59-4EFB-A773-B6F6E4FD5884@fugue.com> <C93A4EFBD3E91F4F714DF948@caldav.corp.apple.com> <CAMm+LwgWSp7R=vZfWNXTsk4DjCDAWo4PVNnYsGPrewZp2Ng0hw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAMm+LwgWSp7R=vZfWNXTsk4DjCDAWo4PVNnYsGPrewZp2Ng0hw@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OpwSshaqvVWdyJaiduTQsVN5ck0>
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: Wed, 29 Mar 2017 15:45:47 -0000

On Tue, Jan 03, 2017 at 03:06:57PM -0500, Phillip Hallam-Baker wrote:
> +1

Indeed.

> Case in point, the time displayed on my Honda Oddy does not correct for
> daylight savings correctly because some pimple brain decided to vary the
> date of the switchover and there is no way to update the firmware without
> spending stupid amounts of money to do so.
> 
> This is the sort of thing I would like to be able to avoid in IoT. The
> problem being that to do so requires vendors to think about problems as
> something other than an excuse to sell a 'pro' version or updates.

Trouble is, this is one more protocol for IoTs to speak.  One more
source of those vulnerabilities that make IoTs IoSs.

> Not being able to predict with accuracy when a future time expressed in
> civil time will occur is a problem.

It's easy to predict that actual changes will be withing +/- 1 hour
though.  For events scheduled far into the future this is mostly a
non-issue.

I'm not interested in more complaining about politicians making our life
hell.  Fact is they get to and they do and they have and they will keep
doing it.  So we should arrange our affairs as to minimize the pain and
just move on.

Nico
--