IETF Logo Mail Archive

Re: [art] Predictable Internet Time

Philip Homburg <pch-ietf-art@u-1.phicoh.com> Wed, 29 March 2017 15:13 UTC

Return-Path: <pch-bF054DD66@u-1.phicoh.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 BC6041296CB for <art@ietfa.amsl.com>; Wed, 29 Mar 2017 08:13:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
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 EgcE9bLsXz36 for <art@ietfa.amsl.com>; Wed, 29 Mar 2017 08:13:10 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo.hq.phicoh.net [130.37.15.35]) by ietfa.amsl.com (Postfix) with ESMTP id B65941296B5 for <art@ietf.org>; Wed, 29 Mar 2017 08:13:08 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (Smail #130) id m1ctFHX-0000HSC; Wed, 29 Mar 2017 17:13:07 +0200
Message-Id: <m1ctFHX-0000HSC@stereo.hq.phicoh.net>
To: art@ietf.org
Cc: Joe Touch <touch@isi.edu>
From: Philip Homburg <pch-ietf-art@u-1.phicoh.com>
Sender: pch-bF054DD66@u-1.phicoh.com
References: <e0a43370-751f-808c-3719-9716f9cd57d1@isi.edu> <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> <111c86bc-c2c5-5050-edc0-82e40d36c570@isi.edu> <m1ctEy7-0000G9C@stereo.hq.phicoh.net> <70bae467-8636-379c-7452-21cacf03215f@isi.edu>
In-reply-to: Your message of "Wed, 29 Mar 2017 07:57:30 -0700 ." <70bae467-8636-379c-7452-21cacf03215f@isi.edu>
Date: Wed, 29 Mar 2017 17:13:07 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/OuMc2cY8QrWa2GBoMXmARKiCvOQ>
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 15:13:12 -0000

>Right - I will update the doc accordingly. AFAICT, POSIX time implies
>(but never states) that it uses a local reference clock to emulate TAI.

Not TAI, UTC.

Every time_t value has a specific interpretation as a UTC timestamp. Obviously,
without correction a free running clock will go wrong with leap seconds. But
that doesn't change that it is some approximation of UTC and not TAI.

By and large, current Unix systems have no idea about TAI. There are no 
(commonly available) APIs that give you TAI.

v2.23.0 | Report a Bug | By Email