IETF Logo Mail Archive

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

Philip Prindeville <philipp@redfish-solutions.com> Mon, 04 January 2021 20:33 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 10F2C3A1057 for <ntp@ietfa.amsl.com>; Mon, 4 Jan 2021 12:33:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[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 9v_8PAAYNs2G for <ntp@ietfa.amsl.com>; Mon, 4 Jan 2021 12:33:53 -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 0BF9B3A1056 for <ntp@ietf.org>; Mon, 4 Jan 2021 12:33:52 -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 104KXjGV348329 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 4 Jan 2021 13:33:45 -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: <cbfd20ae-7cc1-4ef8-0db4-540a11f64378@rubidium.se>
Date: Mon, 04 Jan 2021 13:33:45 -0700
Cc: Warner Losh <imp@bsdimp.com>, NTP WG <ntp@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <24EEF821-8ED9-46CF-8790-1DF63B102D76@redfish-solutions.com>
References: <20210102081603.1F63C40605C@ip-64-139-1-69.sjc.megapath.net> <cecaf661-92af-8b35-4c53-2f025c928144@rubidium.se> <CANCZdfrURzZp5EoU8A-Q9K1tZN0DvLJ10a3ekQtvfrLJExuriA@mail.gmail.com> <cbfd20ae-7cc1-4ef8-0db4-540a11f64378@rubidium.se>
To: Magnus Danielson <magnus@rubidium.se>
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/K7vxdhpZoXYZRBSJuvFJX5JV_SI>
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: Mon, 04 Jan 2021 20:33:54 -0000


> On Jan 4, 2021, at 1:21 PM, Magnus Danielson <magnus@rubidium.se> wrote:
> 
> Warner,
> 
> On 2021-01-04 19:29, Warner Losh wrote:
>> 
>> 
>> On Mon, Jan 4, 2021 at 9:34 AM Magnus Danielson <magnus@rubidium.se> wrote:
>> > It's not in NetBSD or FreeBSD.
>> Unfortunately not. However, that could probably be changed if enough
>> interest exists.
>> 
>> There were a number of issues with it in Linux.
> What issues are these that you refer to?
>> If there's a clearer definition of what it should be and how things should be updated as leap second knowledge evolves, I'd be happy to get it into FreeBSD...
> I think that part of the discussion is really not part of NTP WG discussion, but I am sure things can be figured out.
> 

Again, disagree.  I remember the days of the IETF where (1) a document describing a protocol was required, and (2) a successful “bake-off” demonstrating 3 unrelated interoperating implementations was equally required…

FreeBSD is as good a platform as any to demonstrate one of those implementations.

-Philip



> Cheers,
> Magnus
>

v2.23.0 | Report a Bug | By Email