IETF Logo Mail Archive

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

Kurt Roeckx <kurt@roeckx.be> Sun, 29 November 2020 19:43 UTC

Return-Path: <kurt@roeckx.be>
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 182F73A0DE2 for <ntp@ietfa.amsl.com>; Sun, 29 Nov 2020 11:43:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 TNRftZrhfP5p for <ntp@ietfa.amsl.com>; Sun, 29 Nov 2020 11:43:36 -0800 (PST)
Received: from excelsior.roeckx.be (excelsior.roeckx.be [195.234.45.115]) (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 401973A0DDC for <ntp@ietf.org>; Sun, 29 Nov 2020 11:43:35 -0800 (PST)
Received: from intrepid.roeckx.be (localhost [127.0.0.1]) by excelsior.roeckx.be (Postfix) with ESMTP id 75247A8A025F; Sun, 29 Nov 2020 19:43:33 +0000 (UTC)
Received: by intrepid.roeckx.be (Postfix, from userid 1000) id 4A1051FE0DAB; Sun, 29 Nov 2020 20:43:33 +0100 (CET)
Date: Sun, 29 Nov 2020 20:43:32 +0100
From: Kurt Roeckx <kurt@roeckx.be>
To: g16 <g16g16g16@gmail.com>
Cc: ntp@ietf.org, mlichvar@redhat.com
Message-ID: <20201129194332.GB971977@roeckx.be>
References: <CAFZ=0SzC1cKbMf=9tNDdxYfde9UnD4CcLYZ2EGwvcKMEtp1i1w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CAFZ=0SzC1cKbMf=9tNDdxYfde9UnD4CcLYZ2EGwvcKMEtp1i1w@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/hQtoykpm784QjxE0H8kxJiHnzfM>
Subject: Re: [Ntp] 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: Sun, 29 Nov 2020 19:43:38 -0000

On Mon, Nov 30, 2020 at 12:49:09AM +0900, g16 wrote:
> Hi, NTP WG and Miroslav !
> 
> I'm yuki.
> 
> I am interested in NTPv5 and ossification.
> 
> So I surveyed how the currently public NTP servers respond to NTPv5 packets.

The draft document probably doesn't make things better. It says to
just drop the packet in case the version is higher than 5, nor
does it have any text on what a client could do to talk to a
server that supports older versions. So in case a version 6 is ever
introduced, first the stratum 1 servers have to upgrade, then the
stratum 2 servers, and so on.

Either the the v5 packet should be in such a format that a v4
server can interprete the packet and reply in v4, or a v4 server
should tell the client which version it does support.

Reading the draft document, it at least looks like we try to be
compatible to the v4 format.


Kurt

v2.23.0 | Report a Bug | By Email