[Ntp] Antw: [EXT] Re: NTPv5: big picture

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Mon, 04 January 2021 14:16 UTC

Return-Path: <Ulrich.Windl@rz.uni-regensburg.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 677F03A0D6D for <ntp@ietfa.amsl.com>; Mon, 4 Jan 2021 06:16:48 -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 UMmvkhwua3It for <ntp@ietfa.amsl.com>; Mon, 4 Jan 2021 06:16:46 -0800 (PST)
Received: from mx2.uni-regensburg.de (mx2.uni-regensburg.de [IPv6:2001:638:a05:137:165:0:3:bdf8]) (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 691CD3A0D6B for <ntp@ietf.org>; Mon, 4 Jan 2021 06:16:46 -0800 (PST)
Received: from mx2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 75D2A6000050 for <ntp@ietf.org>; Mon, 4 Jan 2021 15:16:43 +0100 (CET)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx2.uni-regensburg.de (Postfix) with ESMTP id EFB7F600004D for <ntp@ietf.org>; Mon, 4 Jan 2021 15:16:40 +0100 (CET)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Mon, 04 Jan 2021 15:16:40 +0100
Message-Id: <5FF32347020000A10003DF2E@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.0
Date: Mon, 04 Jan 2021 15:16:39 +0100
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: "ntp@ietf.org" <ntp@ietf.org>, Hal Murray <hmurray@megapathdsl.net>, doug.arnold@meinberg-usa.com
References: <20210101025440.ECE3340605C@ip-64-139-1-69.sjc.megapath.net> <0DF4D79B-29BA-4DB0-A3D6-EE3B6AE807DF@meinberg-usa.com>
In-Reply-To: <0DF4D79B-29BA-4DB0-A3D6-EE3B6AE807DF@meinberg-usa.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/bxQ9f91j5RaZUAX0Xo2JeUkc6Q4>
Subject: [Ntp] Antw: [EXT] Re: 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 14:16:48 -0000

>>> Doug Arnold <doug.arnold@meinberg-usa.com> schrieb am 01.01.2021 um 17:14
in
Nachricht <0DF4D79B-29BA-4DB0-A3D6-EE3B6AE807DF@meinberg-usa.com>:
> I would say that the unifying themes for ntpv5 are greater flexibility, and

> higher accuracy, compared to ntpv4.  

I'd like to add: Updated monitoring and management capabilities.
Should dynamic addition, reconfiguration and deletion of time sources be a
SHOULD for v5 at least?

> 
> Doug
> 
> 
> On 12/31/20, 9:54 PM, "ntp on behalf of Hal Murray" <ntp-bounces@ietf.org
on 
> behalf of hmurray@megapathdsl.net> wrote:
> 
> 
>     Do we have a unifying theme?  Can you describe why we are working on 
> NTPv5 in 
>     one sentence?
> 
>     I'd like to propose that we get rid of leap seconds in the basic 
> protocol.
> 
>     Unfortunately, we have a huge installed base that works in Unix time 
> and/or 
>     smeared time.  Can we push supporting that to extensions?  Maybe even a

>     separate document.
> 
>     --------
> 
>     Part of the motivation for this is to enable and encourage OSes to 
> convert to 
>     non-leaping time in the kernels.  Are there any subtle details in this 
> area 
>     that we should be aware of?  Who should we coordinate with?  ...
> 
>     ---------
> 
>     I think this would bring out another important area: How does a client 
>     discover if a server supports an option and/or discover servers that do

>     support it?
> 
>     I'd like the answer to be authenticated.  It seems ugly to go through 
> NTS-KE 
>     if the answer is no.  Maybe we should distribute the info via DNS where

> we can 
>     use DNSSEC.
> 
>     Again, that can be a separate document.
> 
> 
> 
> 
>     -- 
>     These are my opinions.  I hate spam.
> 
> 
> 
>     _______________________________________________
>     ntp mailing list
>     ntp@ietf.org 
>     https://www.ietf.org/mailman/listinfo/ntp 
> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp