Re: [Ntp] Timescales
Martin Burnicki <martin.burnicki@meinberg.de> Wed, 09 December 2020 22:40 UTC
Return-Path: <martin.burnicki@meinberg.de>
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 88DED3A1786 for <ntp@ietfa.amsl.com>; Wed, 9 Dec 2020 14:40:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level:
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_HELO_NONE=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=meinberg.de
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 IIGZ-pUCZuIH for <ntp@ietfa.amsl.com>; Wed, 9 Dec 2020 14:40:26 -0800 (PST)
Received: from server1a.meinberg.de (server1a.meinberg.de [176.9.44.212]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7384E3A1785 for <ntp@ietf.org>; Wed, 9 Dec 2020 14:40:25 -0800 (PST)
Received: from srv-kerioconnect.py.meinberg.de (unknown [193.158.22.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by server1a.meinberg.de (Postfix) with ESMTPSA id 802A271C07B2 for <ntp@ietf.org>; Wed, 9 Dec 2020 23:40:22 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=meinberg.de; s=dkim; t=1607553622; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=QtB8amKhgq2zVLzCaLhl9JsjLInhUZzZbKooHHLewSQ=; b=U681zmKN3o1zXoZt6t36i0YRpBGJdeVd9EY+rZ3lxZFTug4AKyvSE9HXXutEuhALMB6LLM 95D1Z0zdH5TOaZWYu93F6BQki8oH1Xx2fUidq7xGx07Z1vxE0gmL9mD1gPL1yxovvalTbV Qf7psvQNKcJIjYXdbZhvuZyTUnvA2lGHOdfXrV5CqwWTYCnk6FDR+u/4dUeHodcQwh3/nZ MXh6EKvYgQjS0fiCDosBfRlgHClj3RuG7UOR0ISW8aIsHNc+XXVLVVM8bmNWzPfLcThUdl c7kPHRMpbn3psZ34bOcILBkcxs63KK4A+D9smqEaO8YkcYUKpF6yZeI+iVerTg==
X-Footer: bWVpbmJlcmcuZGU=
Received: from localhost ([127.0.0.1]) by srv-kerioconnect.py.meinberg.de with ESMTPSA (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) for ntp@ietf.org; Wed, 9 Dec 2020 23:40:21 +0100
To: ntp@ietf.org
References: <20201209101830.7CB0240605C@ip-64-139-1-69.sjc.megapath.net> <058712d2-d031-65a6-d816-0b28c56cf87b@rubidium.se> <20201209162923.GO2553@ucolick.org>
From: Martin Burnicki <martin.burnicki@meinberg.de>
Organization: Meinberg Funkuhren GmbH & Co. KG, Bad Pyrmont, Germany
Message-ID: <d78358cd-c6a2-0a95-eee3-05df5496d315@meinberg.de>
Date: Wed, 09 Dec 2020 23:40:20 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0
MIME-Version: 1.0
In-Reply-To: <20201209162923.GO2553@ucolick.org>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/qgpEXfQ8WgpKQ60Z9Q-KCzfjvYg>
Subject: Re: [Ntp] Timescales
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: Wed, 09 Dec 2020 22:40:29 -0000
Steve Allen wrote: > The extended discussion in the NTPWG now is strikingly similar to the > arguments in the late 1960s which resulted in leap seconds. > A 1969 report analyzing the options pointed out that leap seconds > would cause problems in precise timing systems used for navigation. > Backward compatibility concerns forced the international agreement to > have leap seconds. Before the first leap second the technical members > of the committees proceeded to change their operational systems to use > purely atomic time with no leaps, and that choice was repeated for > GPS, Galileo, BeiDou, etc. because it was the only robust way. True, and I agree, but if you need civil time, corrections and offsets also have to be provided by these systems. Of course, the operators of the GNSS systems provide this information via the satellite signals, but if you operate your own NTP stratum-1 server (or your own PTP grandmaster) you have to find a reliable source for this kind of information. If this is a leap second file, you have to make sure the file is always kept up to date. Martin -- Martin Burnicki Senior Software Engineer MEINBERG Funkuhren GmbH & Co. KG Email: martin.burnicki@meinberg.de Phone: +49 5281 9309-414 Linkedin: https://www.linkedin.com/in/martinburnicki/ Lange Wand 9, 31812 Bad Pyrmont, Germany Amtsgericht Hannover 17HRA 100322 Geschäftsführer/Managing Directors: Günter Meinberg, Werner Meinberg, Andre Hartmann, Heiko Gerstung Websites: https://www.meinberg.de https://www.meinbergglobal.com Training: https://www.meinberg.academy
- Re: [Ntp] Timescales Miroslav Lichvar
- [Ntp] Timescales Hal Murray
- [Ntp] Antwort: Timescales kristof.teichel
- Re: [Ntp] Timescales Magnus Danielson
- [Ntp] Antw: [EXT] Timescales Ulrich Windl
- [Ntp] Antw: [EXT] Re: Timescales Ulrich Windl
- Re: [Ntp] Antw: [EXT] Re: Timescales Magnus Danielson
- Re: [Ntp] Antw: [EXT] Re: Timescales Miroslav Lichvar
- Re: [Ntp] Timescales FUSTE Emmanuel
- Re: [Ntp] Antw: [EXT] Re: Timescales FUSTE Emmanuel
- Re: [Ntp] Antw: [EXT] Re: Timescales Miroslav Lichvar
- Re: [Ntp] Timescales Magnus Danielson
- Re: [Ntp] Antw: [EXT] Re: Timescales Magnus Danielson
- Re: [Ntp] Antw: [EXT] Re: Timescales Magnus Danielson
- Re: [Ntp] Antw: [EXT] Re: Timescales Miroslav Lichvar
- Re: [Ntp] Timescales Steve Allen
- Re: [Ntp] Antw: [EXT] Re: Timescales Hal Murray
- Re: [Ntp] Antw: [EXT] Re: Timescales Warner Losh
- Re: [Ntp] Antw: [EXT] Re: Timescales Warner Losh
- Re: [Ntp] Timescales Martin Burnicki
- Re: [Ntp] Antw: [EXT] Re: Timescales Magnus Danielson
- Re: [Ntp] Antw: [EXT] Re: Timescales Magnus Danielson
- Re: [Ntp] Antw: [EXT] Re: Timescales Martin Burnicki
- Re: [Ntp] Antw: [EXT] Re: Timescales Martin Burnicki
- Re: [Ntp] Antw: [EXT] Re: Timescales Martin Burnicki
- Re: [Ntp] Antwort: Timescales Martin Burnicki
- Re: [Ntp] Antw: [EXT] Re: Timescales Martin Burnicki
- Re: [Ntp] Antw: [EXT] Re: Timescales Hal Murray
- Re: [Ntp] Antw: [EXT] Re: Timescales Magnus Danielson
- Re: [Ntp] Antw: [EXT] Re: Timescales Magnus Danielson
- Re: [Ntp] Timescales Philip Prindeville
- Re: [Ntp] Timescales Magnus Danielson
- Re: [Ntp] Timescales Steve Allen
- [Ntp] Antw: Re: Antw: [EXT] Re: Timescales Ulrich Windl
- Re: [Ntp] Antw: [EXT] Re: Timescales Ulrich Windl
- Re: [Ntp] Antw: Re: Antw: [EXT] Re: Timescales Warner Losh
- Re: [Ntp] Antw: [EXT] Re: Timescales Steve Allen
- Re: [Ntp] Antw: [EXT] Re: Timescales Martin Burnicki
- Re: [Ntp] Antw: [EXT] Re: Timescales Magnus Danielson
- Re: [Ntp] Antw: Re: Antw: [EXT] Re: Timescales Magnus Danielson
- Re: [Ntp] Antw: [EXT] Re: Timescales Magnus Danielson
- [Ntp] Antw: Re: Antw: [EXT] Re: Timescales Ulrich Windl
- [Ntp] Antw: Re: Antw: Re: Antw: [EXT] Re: Timesca… Ulrich Windl
- Re: [Ntp] Antw: Re: Antw: [EXT] Re: Timescales Magnus Danielson