Re: [Ntp] Leap second draft

Steve Allen <sla@ucolick.org> Sat, 30 March 2019 13:35 UTC

Return-Path: <sla@ucolick.org>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9F2B1201A7 for <ntp@ietfa.amsl.com>; Sat, 30 Mar 2019 06:35:58 -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, SPF_PASS=-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 36CPPJfiXz-S for <ntp@ietfa.amsl.com>; Sat, 30 Mar 2019 06:35:57 -0700 (PDT)
Received: from smtp.ucolick.org (zilan.ucolick.org [128.114.23.234]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5042B12000F for <ntp@ietf.org>; Sat, 30 Mar 2019 06:35:57 -0700 (PDT)
Received: from smtp.ucolick.org (localhost [127.0.0.1]) by smtp.ucolick.org (Postfix) with ESMTP id 403D529D0 for <ntp@ietf.org>; Sat, 30 Mar 2019 06:35:56 -0700 (PDT)
Received: from geneva.ucolick.org (geneva.ucolick.org [128.114.23.183]) by smtp.ucolick.org (Postfix) with ESMTP id 123EE298F for <ntp@ietf.org>; Sat, 30 Mar 2019 06:35:56 -0700 (PDT)
Received: from geneva.ucolick.org (localhost [127.0.0.1]) by geneva.ucolick.org (Postfix) with ESMTP id F33B0293 for <ntp@ietf.org>; Sat, 30 Mar 2019 06:35:55 -0700 (PDT)
Received: (from sla@localhost) by geneva.ucolick.org (8.14.7/8.14.7/Submit) id x2UDZt54020778 for ntp@ietf.org; Sat, 30 Mar 2019 06:35:55 -0700
Date: Sat, 30 Mar 2019 06:35:55 -0700
From: Steve Allen <sla@ucolick.org>
To: NTP WG <ntp@ietf.org>
Message-ID: <20190330133555.GA20717@ucolick.org>
References: <CAJm83bD5Ozkpg5TpkogOW6xeeNQL3ZziLO9URM7haqN8Wrp=Wg@mail.gmail.com> <CAJm83bCbVzO3NNCbjTy+O_16T7DBeA7O6018WWGu_-GyuN-8UA@mail.gmail.com> <20190330045928.GA31550@ucolick.org> <20190330054611.GA1539@ucolick.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20190330054611.GA1539@ucolick.org>
User-Agent: Mutt/1.9.2 (2017-12-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/2pSet-XfbZ_O8T3MbfVfVuZfIgs>
Subject: Re: [Ntp] Leap second draft
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 30 Mar 2019 13:35:59 -0000

This is the second message to Daniel Franke.

On Fri 2019-03-29T21:59:28-0700 Steve Allen hath writ:
> >           While neither TAI nor UTC is formally defined for any date
> >    earlier than the epoch, this nit is routinely ignored by allowing the
> >    day number to be negative and by assuming the fiction that prior to
> >    1958 Earth's rotation was always perfectly regular with respect to
> >    proper time.
>
> Which epoch?  POSIX epoch?
> Any date at which there is general agreement among all parties
> about when it happened is an epoch.  Please be specific and
> never use merely "the epoch".

To expand on my objection here, I find these sentences to be
unconnectable to any concrete concepts.

There is a common strategy in time scales which are trying to be a
precision time scale now, but which also wish to extend themselves
simply to an era before there was precision.

As such time scales are extended backwards in time there is some
past epoch at which the scale switches tracks and connects itself
to just plain Universal Time.  So such time scales are counting
SI seconds now, but going into the past they switch to counting
mean solar seconds.

They do not presume that the mean solar seconds were perfectly
regular, they just change from one kind of second to the other.

For radio broadcast time signals the change happened 1972-01-01
because that is what the CCIR said in Recommendation 460.

For Microsoft Windows the change happened 2018-06-01 because
that is what Microsoft said is the date that they begin to
distribute TAI offset from UTC so that Windows boxes can
count subsequent leap seconds.

--
Steve Allen                    <sla@ucolick.org>              WGS-84 (GPS)
UCO/Lick Observatory--ISB 260  Natural Sciences II, Room 165  Lat  +36.99855
1156 High Street               Voice: +1 831 459 3046         Lng -122.06015
Santa Cruz, CA 95064           https://www.ucolick.org/~sla/  Hgt +250 m