Re: Predictable Internet Time

Nico Williams <nico@cryptonector.com> Wed, 29 March 2017 15:54 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 6D9DD126D74 for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 08:54:19 -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 QiLfieYZBtTK for <ietf@ietfa.amsl.com>; Wed, 29 Mar 2017 08:54:18 -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 60C55126557 for <ietf@ietf.org>; Wed, 29 Mar 2017 08:54:18 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTP id F3BA21406B1F; Wed, 29 Mar 2017 08:54:17 -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=TSIArRKo0Xav/I 13ssPJu6czShk=; b=DW9eNwGLY07ZKS2WaUcCigCbNKnh4WdK5v8OWODI+1bnxn D9kdS8BfREjWJFBdgzhvCMnyYLkvM61J4cMn58Vhircob9EYd6Hkc54sFwDHDfKM +NMtyxcGOIw+HdY2GlxGgARNhK6Qc+eWjyriWw9MraTclJHsVa+iRqV2V13HE=
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 986921406B1A; Wed, 29 Mar 2017 08:54:17 -0700 (PDT)
Date: Wed, 29 Mar 2017 10:54:15 -0500
From: Nico Williams <nico@cryptonector.com>
To: Philip Homburg <pch-ietf-6@u-1.phicoh.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>, Phillip Hallam-Baker <phill@hallambaker.com>
Subject: Re: Predictable Internet Time
Message-ID: <20170329155414.GR7490@localhost>
References: <CAMm+Lwg+aD1DQ_=sr=3_7J2Eq+E16EScycyv7k=fdjrRvqdRVg@mail.gmail.com> <m1cOYZ6-0000FAC@stereo.hq.phicoh.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m1cOYZ6-0000FAC@stereo.hq.phicoh.net>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9u5Q3dYECdNJBHqJVTKMxHVTDQY>
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:54:19 -0000

On Wed, Jan 04, 2017 at 12:32:23AM +0100, Philip Homburg wrote:
> Unfortunately, there doesn't seem to be an IETF equivalent for operating
> systems, so it will be completely random whether anything will happen in
> this area or not.

There's no reason that the IETF could not a) define an abstract time API
that includes time "types" ({UTC, TAI, local, smeared, whatever} x
{various possible representations}), conversions between them, and
behaviors, then b) define bindings of this API for various programming
languages.  The Open Group, to give one example, could take our advice
on this matter -- or not; they'd not be obligated, natch.

The IETF has done this for other networking technologies (sockets
extensions for IPv6, GSS-API, ...).

Because our protocols must deal with time, this is very much in our
bailiwick.  It also fits in other SDOs, but as none have published such
a spec, we might lead.

Any RFC on smeared time surely would at least define a subset of this
abstract API for conversions to/from UTC.  We might as well go all the
way.

Nico
--