Re: [Ntp] Antw: [EXT] Re: Public NTP servers already responds to NTPv5

Hal Murray <hmurray@megapathdsl.net> Thu, 03 December 2020 08:16 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 8698A3A0AD4 for <ntp@ietfa.amsl.com>; Thu, 3 Dec 2020 00:16:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.037
X-Spam-Level: *
X-Spam-Status: No, score=1.037 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_DYNAMIC_IPADDR=1.951, PDS_RDNS_DYNAMIC_FP=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 fbwqWuPgpFaO for <ntp@ietfa.amsl.com>; Thu, 3 Dec 2020 00:16:47 -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 C48853A0AD3 for <ntp@ietf.org>; Thu, 3 Dec 2020 00:16:46 -0800 (PST)
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id E1DAF40605C; Thu, 3 Dec 2020 00:16:42 -0800 (PST)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
cc: "ntp@ietf.org" <ntp@ietf.org>, stenn@nwtime.org, hmurray@megapathdsl.net
From: Hal Murray <hmurray@megapathdsl.net>
In-Reply-To: Message from "Ulrich Windl" <Ulrich.Windl@rz.uni-regensburg.de> of "Thu, 03 Dec 2020 08:53:08 +0100." <5FC89964020000A10003D3DF@gwsmtp.uni-regensburg.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Thu, 03 Dec 2020 00:16:42 -0800
Message-Id: <20201203081642.E1DAF40605C@ip-64-139-1-69.sjc.megapath.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/c44WItLGgDr4METZVHSN-Sal8jE>
Subject: Re: [Ntp] Antw: [EXT] Re: Public NTP servers already responds to NTPv5
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, 03 Dec 2020 08:16:49 -0000

Ulrich.Windl@rz.uni-regensburg.de said:
> I had a similar idea: Instead of specifying "version=n" for a client, an
> implementation might allow "versions=5,4" or "verlist=5,4" or
> "version_list=5,4" to specify that it would like to use NTPv5, but if that
> fails (more than one packet, please!) try NTPv4; if that fails, trat the
> server as unreachable. Of course the list could also include NTPv3... 

That doesn't effect the on-the-wire protocol.

It's a good idea and should probably be mentioned in any NTPv5 documentation 
if only to make sure that people think about it since much of the current code 
doesn't work that way and our thinking might get stuck in a rut.  But it 
should be off in a notes-to-implementers footnote rather than the main 
protocol description.

Have we identified any protocol features where somebody might want to do that?

-- 
These are my opinions.  I hate spam.