IETF Logo Mail Archive

Re: Predictable Internet Time

Nico Williams <nico@cryptonector.com> Wed, 19 April 2017 16:14 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 38E34129AF2 for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 09:14:55 -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 fAhp1GAvL3YL for <ietf@ietfa.amsl.com>; Wed, 19 Apr 2017 09:14:54 -0700 (PDT)
Received: from homiemail-a88.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 08D71129AD4 for <ietf@ietf.org>; Wed, 19 Apr 2017 09:14:54 -0700 (PDT)
Received: from homiemail-a88.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a88.g.dreamhost.com (Postfix) with ESMTP id 61691A003A1E; Wed, 19 Apr 2017 09:14:53 -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:content-transfer-encoding; s= cryptonector.com; bh=Sm4XnZuO5MefcXRmFjXTTojmaX8=; b=BXJ0H6/djY/ skd3isoRqMJU0QQ7glvZ45lga6dg5np3vOw6/pf8+NtHUirdH01B8J50NcKtMQ4W MUquQu5I5jauYYWlZinrANUADt2ysEM8D4Hn/IxbFxSOebNESgdYaIbrhvgQnCyO ew3ZgXQpcZXsxPTBS1QbamQgVG9JHSpg=
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-a88.g.dreamhost.com (Postfix) with ESMTPSA id A1C83A003A1D; Wed, 19 Apr 2017 09:14:52 -0700 (PDT)
Date: Wed, 19 Apr 2017 11:14:49 -0500
From: Nico Williams <nico@cryptonector.com>
To: Patrik Fältström <paf@frobbit.se>
Cc: Toerless Eckert <tte@cs.fau.de>, Phillip Hallam-Baker <phill@hallambaker.com>, IETF Discussion Mailing List <ietf@ietf.org>, Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: Predictable Internet Time
Message-ID: <20170419161448.GC2856@localhost>
References: <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> <E030FF20-4EA4-4475-9304-B6F7ADA0B8C2@frobbit.se>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
In-Reply-To: <E030FF20-4EA4-4475-9304-B6F7ADA0B8C2@frobbit.se>
User-Agent: Mutt/1.5.24 (2015-08-30)
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/W9F8EtowzLs66wxbZ_fIknw25gc>
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, 19 Apr 2017 16:14:55 -0000

On Wed, Apr 19, 2017 at 07:18:29AM +0200, Patrik Fältström wrote:
> I want as potential fixes which I think are doable:
> 
> - an updated POSIX definition where the variable which holds the
> number of seconds since the epoch when converting back and forth to
> date actually will hold the number of seconds since the epoch.

So we should... brigade the Open Group?

> - a slot in the NTP protocol not used today include the number of leap
> seconds so people get to know that.
> 
> FWIW I am a person that is against smear. I think a clock must be able
> to give the correct time and that timestamps should be correct. Either
> in seconds (and fractions of seconds) since the epoch or in correct
> date and time UTC. Both are increasing all the time. And because of
> that smear should not have to happen.

+1

> That said, I am not against a BCP explaining the issues due to for
> example the broken POSIX specification (which makes it hard to "do the
> right thing" in software).

Sure.

Nico
--

v2.23.0 | Report a Bug | By Email