Re: [art] Predictable Internet Time

Joe Touch <touch@isi.edu> Wed, 29 March 2017 15:46 UTC

Return-Path: <touch@isi.edu>
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 14A3F129422 for <art@ietfa.amsl.com>; Wed, 29 Mar 2017 08:46:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level:
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] 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 Kx6V3-Qp8q7O for <art@ietfa.amsl.com>; Wed, 29 Mar 2017 08:46:25 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 4BDC112942F for <art@ietf.org>; Wed, 29 Mar 2017 08:46:18 -0700 (PDT)
Received: from [192.168.1.189] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v2TFjnIV026245 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 29 Mar 2017 08:45:50 -0700 (PDT)
To: Tony Finch <dot@dotat.at>
References: <m1csrkh-0000GYC@stereo.hq.phicoh.net> <1cb57d13-4145-eb74-7d6a-954fe3a1059c@isi.edu> <alpine.DEB.2.11.1703282033370.2180@grey.csi.cam.ac.uk>
Cc: Philip Homburg <pch-ietf-art@u-1.phicoh.com>, art@ietf.org
From: Joe Touch <touch@isi.edu>
Message-ID: <2c04440a-11e4-4c7f-1e63-7151794ec90d@isi.edu>
Date: Wed, 29 Mar 2017 08:45:48 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <alpine.DEB.2.11.1703282033370.2180@grey.csi.cam.ac.uk>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/T1Y-7jDF9JBAnrEwUNe8ximbv8s>
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:46:28 -0000


On 3/28/2017 1:12 PM, Tony Finch wrote:
> Joe Touch <touch@isi.edu> wrote:
>
>> Section 3 states that in the definition of a solar day. Section 4.2
>> explains that UT0 is one of many different "means", and that UT0 is the
>> most common in current use.
> No, UT1 is the most common form of mean solar time. (UT0 is basically
> mean solar time at a particular observatory; UT1 is corrected for polar
> motion so it is globally consistent.)
Yes - mistyped (the doc is correct on that - it says UT1 is the
particular mean that is in common use).

>
>> GPS isn't one of the clocks averaged into TAI (AFAICT); it's a separate
>> source that's sync'd to TAI to ensure the 25 ns max delta.
> Well, GPS is an ensemble clock (each sat has its own clock) which is
> steered with reference to UTC(USNO). UTC(USNO) feeds into the BIPM paper
> clocks.
>
> The USNO says that GPS's maximum deviation from UTC(USNO) is 1us though
> in practice it is within a few hundred nanoseconds. The NAV message has
> additional information that allows GPS receivers to get the UTC(USNO) time
> to within 40ns.
>
> http://www.usno.navy.mil/USNO/time/gps/usno-gps-time-transfer

The GPS spec guarantees that its max deviation is 25 ns AFAICT (see the
cited ref in the doc).

>
>>> - It is not clear to me why NTP would differ 100ms from TAI.
>> It's in the spec.
> Where in which spec?

It's in the definition of NTP strata. Stratum 0 is the a reference clock
itself; stratum 1 is connected to the clock directly, stratum 2 is
connected to stratum 1 over the net. I'll dig up a specific citation for
that...

>
>> Uptime is just a printout of the delta of the POSIX time when a computer
>> started and the current POSIX time.
> CLOCK_MONOTONIC cannot be reset, so it is more reliable than that.
It is guaranteed monotonic only while the system is running. I don't
know what "reliable" means, but it isn't guaranteed to be preserved
across a boot.

http://pubs.opengroup.org/onlinepubs/9699919799/functions/clock_getres.html

Joe