Re: [art] Predictable Internet Time

Nico Williams <nico@cryptonector.com> Wed, 29 March 2017 02:58 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1CB7128896 for <art@ietfa.amsl.com>; Tue, 28 Mar 2017 19:58:33 -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 afTwdymXscYH for <art@ietfa.amsl.com>; Tue, 28 Mar 2017 19:58:32 -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 8B5A6127F0E for <art@ietf.org>; Tue, 28 Mar 2017 19:58:32 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTP id 684AC1406B1A; Tue, 28 Mar 2017 19:58:31 -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=zK3RkTBaSK/Q+L 2CLEcUNqJ+Hdw=; b=mXkckAFzHOTDee+h31LP1Tj8Z59KK5LGZ974Z2Xh9ylPMO 59bXu4sGB1k/arNIAHzHEzb6CQh69LYC2uBAnvEGSkeunnaFqHulgXib/HSrQH0H 4smVUVmmymwsNsoPAeheVDO9O0uehT5/Tb1LWethIqI4BQqDd5cggSRa4PXWc=
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 9AEED1406B0A; Tue, 28 Mar 2017 19:58:15 -0700 (PDT)
Date: Tue, 28 Mar 2017 21:58:13 -0500
From: Nico Williams <nico@cryptonector.com>
To: Joe Touch <touch@isi.edu>
Cc: art@ietf.org
Message-ID: <20170329025808.GM7490@localhost>
References: <alpine.DEB.2.11.1701031348430.7102@grey.csi.cam.ac.uk> <f94415b6-d9f7-0a03-cf5b-ce39c109aa71@isi.edu> <f9429571-b9d5-75d4-9b46-b877a189a7bf@gmail.com> <20170328173916.GE7490@localhost> <e73d5c15-1ba3-8162-f7df-555e2e8588a6@isi.edu> <20170328224041.GJ7490@localhost> <9ddcde60-a915-a03d-dfc3-2c2c451c398c@isi.edu> <20170329000601.GK7490@localhost> <96ad09b7-7dc2-20e8-2aa4-793310d184f6@isi.edu> <20170329015811.GL7490@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20170329015811.GL7490@localhost>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/eZQnCkswRVCTyUcu4MFUXix2wIQ>
Subject: Re: [art] Predictable Internet Time
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Mar 2017 02:58:34 -0000

On Tue, Mar 28, 2017 at 08:58:12PM -0500, Nico Williams wrote:
> On Tue, Mar 28, 2017 at 05:15:58PM -0700, Joe Touch wrote:
> > >> time_t does not access a SI reference or frankly any other stable reference.
> > > The Open Group man pages I'm looking at don't reference SI, but so
> > > bloody what.  If it says "seconds", it means "seconds".
> > That's the trouble - seconds in SI are not seconds defined as 86400/day.
> > If the units don't match,  then a conversion needs to be included. If
> > the units aren't known, you can't convert accurately.
> 
> POSIX does NOT define seconds in terms of days!  It does the opposite:

Although I can see how to waterboard the spec to get either answer.  If
it were right about POSIX time being UTC (which it's not in practice),
then you'd be quite right about it defining seconds in terms of days...

Would that make POSIX a smeared time standard?  Sure seems that way!