IETF Logo Mail Archive

Re: [Ntp] CLOCK_TAI (was NTPv5: big picture)

Philip Prindeville <philipp@redfish-solutions.com> Tue, 05 January 2021 20:12 UTC

Return-Path: <philipp@redfish-solutions.com>
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 9496A3A11AE; Tue, 5 Jan 2021 12:12:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, 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 hzdSWQg5YdGQ; Tue, 5 Jan 2021 12:12:54 -0800 (PST)
Received: from mail.redfish-solutions.com (mail.redfish-solutions.com [45.33.216.244]) (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 65A263A119D; Tue, 5 Jan 2021 12:12:54 -0800 (PST)
Received: from [192.168.3.4] ([192.168.3.4]) (authenticated bits=0) by mail.redfish-solutions.com (8.16.1/8.16.1) with ESMTPSA id 105KCr7G354543 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 5 Jan 2021 13:12:53 -0700
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
From: Philip Prindeville <philipp@redfish-solutions.com>
In-Reply-To: <f876a3ff-16ee-fc63-c27c-d5a3cb847a3d@meinberg.de>
Date: Tue, 05 Jan 2021 13:12:53 -0700
Cc: Hal Murray <hmurray@megapathdsl.net>, Miroslav Lichvar <mlichvar@redhat.com>, ntp@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E78BB38-5FA2-4974-AB25-85C5AD9E7DBE@redfish-solutions.com>
References: <20210105124544.5EF5C40605C@ip-64-139-1-69.sjc.megapath.net> <f876a3ff-16ee-fc63-c27c-d5a3cb847a3d@meinberg.de>
To: Martin Burnicki <martin.burnicki=40meinberg.de@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
X-Scanned-By: MIMEDefang 2.84 on 192.168.1.3
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/Qgy64KJNznxB1JGoxTUO7wyDeR4>
Subject: Re: [Ntp] CLOCK_TAI (was NTPv5: big picture)
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: Tue, 05 Jan 2021 20:12:56 -0000


> On Jan 5, 2021, at 9:09 AM, Martin Burnicki <martin.burnicki=40meinberg.de@dmarc.ietf.org> wrote:
> 
> For NTP, things are different. There is a huge base of NTPv4
> installations, and making NTPv5 basically compatible with v4 would IMO
> strongly increase the acceptance of NTPv5.


The logical corollary to this argument is that because there ARE a lot of servers, it’s not unreasonable to think that there will be a lot of both NTPv4 and NTPv5 servers co-existing in the future, and the user is free to peer with either.

Which eliminates the need for NTPv5 servers to also speak NTPv4.

v2.23.0 | Report a Bug | By Email