Re: [Ntp] Finding leap-seconds.list

" tglassey@earthlink.net " <tglassey@earthlink.net> Thu, 08 November 2018 06:43 UTC

Return-Path: <tglassey@earthlink.net>
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 E0D46130DE2 for <ntp@ietfa.amsl.com>; Wed, 7 Nov 2018 22:43:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.719
X-Spam-Level:
X-Spam-Status: No, score=-1.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=earthlink.net; domainkeys=pass (2048-bit key) header.from=tglassey@earthlink.net header.d=earthlink.net
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 dI7cT9lqDS6g for <ntp@ietfa.amsl.com>; Wed, 7 Nov 2018 22:43:46 -0800 (PST)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3E7E130DC8 for <ntp@ietf.org>; Wed, 7 Nov 2018 22:43:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=earthlink.net; s=dk12062016; t=1541659425; bh=fKDMvCo0R6g9UBenHrsun7nsygBnNd4bwN7m cB9tb2g=; h=Received:To:From:Cc:Subject:Date:MIME-Version: Content-Type:Message-ID:X-ELNK-Trace:X-Originating-IP; b=KR1mpszd3 nk+mlPPh0dNfMpIPCYGow6D/HG153klnD4H2jkX4K7jRNiiBr9271S3i63bo41u7t8l XB27dtk/dTJrXLEM4baMXjZew/oi6D2Tlzmgh3eydbxeLAhKnIGKEIaEK2ulGqhoNiR aDNA62AUvKokHWwmCFEWKEfxdH/ARZaH7QlRHgo+Oyr0wtC3YRg58rluXjpmj+KbBuZ t2QwHuETdh3RNxlZEg/HUBWRNCW+tI8tWuCE7fiywaXMwrLMeG73AFRCA/Hn32PzIXM Rk9jdOgNkB7JjJEfLuOLOzEs/bChxyy3ie6eJd+JznH6DDDWMNOmcCR6xSG//lUwQ==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk12062016; d=earthlink.net; b=nUsFFYLxmiTTWkwi3RShdN522wEEdTI5QRP7cbJfdtshGnL7TfONtOyRMf6M3yMh/u9gIdpFRUB3LENqT8sKTSyAEH2kV4RNz2yBt6elUnfElIlWRlltFjM7TR0nYJFOTwHtw2D66iYZl24kUDUgL1w84XdMuTEeM2p43ldKsEHkFHqLzr2GiMRxrpbAK5zJ/7qIQw93s7z3yn1oiKp2NNAk5AxSdWVkrshiK6Mv8MreW9qEHAwY7cW4Rov88mOFuG9cHME1PtcMEsnYSzi7bkPD2v3ul/qeVLnPAkxcSiIASI5kCF6o+PLSm9NvgOLqYjQr8zbK3ifcSJdx50XjLw==; h=Received:To:From:Cc:Subject:Date:MIME-Version:Content-Type:Message-ID:X-ELNK-Trace:X-Originating-IP;
Received: from [107.92.62.66] (helo=[10.6.178.135]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpa (Exim 4) (envelope-from <tglassey@earthlink.net>) id 1gKe2T-0007Ql-Nd; Thu, 08 Nov 2018 01:43:40 -0500
To: Steve Allen <sla@ucolick.org>
From: "tglassey@earthlink.net" <tglassey@earthlink.net>
Cc: Warner Losh <imp@bsdimp.com>, hidinginthebbc@gmail.com, ntp@ietf.org, eggert@cs.ucla.edu, dsibold.ietf@gmail.com, Martin Burnicki <martin.burnicki@meinberg.de>, denis.reilly@orolia.com
Date: Thu, 08 Nov 2018 09:43:33 +0300
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_0_1541659413716"
Message-ID: <E1gKe2T-0007Ql-Nd@elasmtp-galgo.atl.sa.earthlink.net>
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7941fdda3c3c332aa138d777ed03405d54350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 107.92.62.66
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/AwIdUo-CftAZaaPLDlsrysisZz0>
Subject: Re: [Ntp] Finding leap-seconds.list
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: Thu, 08 Nov 2018 06:43:49 -0000

The IETF has no legal authority to post any TZ data either. It by the way is controlled by three treaties including an international commerce one, an AML one, and another from the ATF realm. 

But the key thing here is in the US the public timebase and all operations about it are tied to 15USC272 and its predecessor, 271.

This isn't really arguable. What is arguable is whether NIST is going to do its job or not it claim that under 15USC260 it's the DOT/RITA who is responsible for this. Since NIST cannot operate any of the joint timekeeping agreements without this IMHO they are stuck with making the data available from a legal standpoint. 

Again this is something the gov. is responsible for IMHO and it should be a formal project of NIST ITS or the Calibration Services desk. 

By the way the legal damage from spoofing this table US huge. So it is what it is.

//tsg

Sent from my HTC, so please excuse any typos this keyboard sucks!

----- Reply message -----
From: "Steve Allen" <sla@ucolick.org>
To: "tglassey@earthlink.net" <tglassey@earthlink.net>
Cc: "Warner Losh" <imp@bsdimp.com>, <hidinginthebbc@gmail.com>, <ntp@ietf.org>, <eggert@cs.ucla.edu>, <dsibold.ietf@gmail.com>, "Martin Burnicki" <martin.burnicki@meinberg.de>, <denis.reilly@orolia.com>
Subject: [Ntp] Finding leap-seconds.list
Date: Thu, Nov 8, 2018 08:28

On Thu 2018-11-08T07:04:26+0300 tglassey@earthlink.net hath writ:
> IETF nor any other non government agency ascribed with time keeping
> should be cross posting the LSL.  It is created and is a requirement
> of NIST (and other Government) related time services.

IETF is not the authority for the recent time change in Morocco.
IETF is not the authority for the recent time change in Metlakatla.
Nor for any of the other data in IANA tzdb is IETF the authority.

All of that data is painstakingly gathered by volunteers from a wide
variety of uncooperative sources in order that it is possible to
convert between internal system times and localized civil times.

The leap seconds data are not different in any respect from all of the
other data in the IANA tz database.  Those data are also needed to
convert between internal system times and localized civil times.

If the IETF is going to claim no authority for the leap second
data then please justify the chain of authority for all of the
rest of the IANA tzdb, or else delete all of that as well.

--
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           http://www.ucolick.org/~sla/   Hgt +250 m