IETF Logo Mail Archive

Re: [Ntp] Finding leap-seconds.list

Hal Murray <hmurray@megapathdsl.net> Thu, 08 November 2018 20:36 UTC

Return-Path: <hmurray@megapathdsl.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 0A1D4130DD4 for <ntp@ietfa.amsl.com>; Thu, 8 Nov 2018 12:36:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.034
X-Spam-Level: *
X-Spam-Status: No, score=1.034 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_DYNAMIC_IPADDR=1.951, RDNS_DYNAMIC=0.982, URIBL_BLOCKED=0.001] autolearn=no 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 DsTrUjjosAwm for <ntp@ietfa.amsl.com>; Thu, 8 Nov 2018 12:36:36 -0800 (PST)
Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by ietfa.amsl.com (Postfix) with ESMTP id 58FA512F295 for <ntp@ietf.org>; Thu, 8 Nov 2018 12:36:35 -0800 (PST)
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id 5850740605C; Thu, 8 Nov 2018 12:36:30 -0800 (PST)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: Martin Burnicki <martin.burnicki@meinberg.de>
cc: Hal Murray <hmurray@megapathdsl.net>, ntp@ietf.org
From: Hal Murray <hmurray@megapathdsl.net>
In-Reply-To: Message from Martin Burnicki <martin.burnicki@meinberg.de> of "Thu, 08 Nov 2018 12:44:18 +0100." <3db197ad-4427-4f3f-12c3-dfdcf60959c0@meinberg.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 08 Nov 2018 12:36:30 -0800
Message-Id: <20181108203630.5850740605C@ip-64-139-1-69.sjc.megapath.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/UbFuV3uubYu3NHWSAK0pJmELMSM>
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 20:36:37 -0000

martin.burnicki@meinberg.de said:
> Agreed. But it would be the benefit of using the TZDIST protocol that this
> could work similar to a combination of DNS and the NTP pool:

> A "root" TZDIST server could be provided with an update, so secondaries or
> pool servers could grab the information and pass it on down the line to the
> final clients. 

Is there code available?  Server?  Client?

Should we ask IANA to run a server?


-- 
These are my opinions.  I hate spam.

v2.23.0 | Report a Bug | By Email