Re: Predictable Internet Time

Phillip Hallam-Baker <phill@hallambaker.com> Tue, 03 January 2017 18:39 UTC

Return-Path: <hallam@gmail.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 B38BF129AB9 for <ietf@ietfa.amsl.com>; Tue, 3 Jan 2017 10:39:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 5ssbIyO_5jQn for <ietf@ietfa.amsl.com>; Tue, 3 Jan 2017 10:39:40 -0800 (PST)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (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 05D94129AAC for <ietf@ietf.org>; Tue, 3 Jan 2017 10:39:40 -0800 (PST)
Received: by mail-wm0-x229.google.com with SMTP id c85so206105843wmi.1 for <ietf@ietf.org>; Tue, 03 Jan 2017 10:39:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=AVZ2W58XIJ6rFx7qLIB/anBp7kW+fxDGl5AD3xnAfJM=; b=GFBeH9UgnsED2kgCpIy3iNC4xrJfbUp3ecXmbdpXB2J5QNgcVW/OUQqwrabmd4z12R sLLOan5dYsag5iwp/4Zqg3+DuTPunjt6AixaREgxbg08UcvLPTPiPOYc+mqO4aFaIt8a z9laujH5alZv+1fz11ws/e/Yu+cOL5Px5cpUUkAOY3dgyfN4Y4t4a1aq1QII6sp4sqgm gMsPnwjiepkZs/Umk/0okLIKK2i+51hjCvAquuRzOQjvtvQw4txvuzrkkx+MfSv0A7x8 mw/mON84Jy8mvuwqKLCQXgMKXwglKveOqejP3n8/6+qDHYXtx7iHbPpWy9SbchD9qA/M hGAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=AVZ2W58XIJ6rFx7qLIB/anBp7kW+fxDGl5AD3xnAfJM=; b=pZZ290INKce7wS/5+WJ1p0gGbvh1HyAvZKW+T+hOm+cqJCZmpho1Jx4f2YnqvyTIU/ BNmS0pC8ZVUxLxRI/lw24K/MbkOxMlrGVytls0XYrzG58m3AQW05+XVi2ILbu8D3pOjx rEVGQSCh/CrkF/yv4GrB6YaDDbHsdFl2wSMFSYBy53gcgl9cZdMiuElTFgjAkL6gugiS +1B9bSYkusfSeix3r1pUn5xuH5WrRP0FjO2Kuc40bGxeJIZM47ASLAhnqYbK+KEDUgtO 8xAFukT0m8JA0rKFPdW6cuUivC7OpciHNQ822Mfr7/SWKz+5QQBZxzMXmnWrYMNTIh/B gS9A==
X-Gm-Message-State: AIkVDXI9Od/BkRQQ9ZQUBYocfBgu/I+VqBPMaPLlLNlLdUUv60wCzxRtZv7hUdVGPQiPV7awAtnWR8e0/tR7pA==
X-Received: by 10.28.4.195 with SMTP id 186mr52319251wme.13.1483468778498; Tue, 03 Jan 2017 10:39:38 -0800 (PST)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.194.83.101 with HTTP; Tue, 3 Jan 2017 10:39:37 -0800 (PST)
In-Reply-To: <b487d605-6a6d-c5d2-4837-c7847f1c9083@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> <b487d605-6a6d-c5d2-4837-c7847f1c9083@isi.edu>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 3 Jan 2017 13:39:37 -0500
X-Google-Sender-Auth: TmGEXqWwGuBhjk0e0ExQHuuWZ-c
Message-ID: <CAMm+Lwg+aD1DQ_=sr=3_7J2Eq+E16EScycyv7k=fdjrRvqdRVg@mail.gmail.com>
Subject: Re: Predictable Internet Time
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=001a1141f02893f2fa054534fd9e
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-OiHy3wGV-Py6p5RDUX2F6fGhoc>
Cc: IETF Discussion Mailing List <ietf@ietf.org>, =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
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 18:39:42 -0000

On Tue, Jan 3, 2017 at 1:23 PM, Joe Touch <touch@isi.edu>; wrote:

> +1
>
> You can deny the ITU all you want, but we are not in control of the time
> standards used by financial, governmental, etc. systems.
>

​Neither is the ITU. The governments, financial services etc are.

An ITU standard that predictably causes confusion and chaos every year is
ripe for replacement.​



> Note that everything below also assumes a consistent view of time
> itself; conversion from "seconds since epoch measured locally" always
> needs to be translated to UTC at sea level on Earth anyway.
>
> Time within the machine should be measured relative to its own temporal
> frame, but whenever we communicate with another machine we need to
> strive to be as close to UTC as possible - warts and all. Anything else
> - including and especially smearing - compromises *correct* behavior.


​So you are for sticking with IPv4 as well?

Nothing can ever change because the ITU is in charge...​

​People are only in charge as long as other people let them. ​





>
> Joe
>
>
> On 1/2/2017 10:29 PM, 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
> >
> > - we should fix the code that do not accept 61 seconds in a minute
>
>