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

Miroslav Lichvar <mlichvar@redhat.com> Mon, 30 November 2020 11:51 UTC

Return-Path: <mlichvar@redhat.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 0910B3A0980 for <ntp@ietfa.amsl.com>; Mon, 30 Nov 2020 03:51:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level:
X-Spam-Status: No, score=-2.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com
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 7BPM1DheWcUX for <ntp@ietfa.amsl.com>; Mon, 30 Nov 2020 03:51:48 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 264403A097D for <ntp@ietf.org>; Mon, 30 Nov 2020 03:51:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1606737107; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=i2lag1tcWkAEs/zkzTwJDVjJKePz0lhmDs7I4RxWW5M=; b=IdXGyaBOi6NsED9BwWAd/EhC9iAfjBkhuVN+12rJAD3eiKqqdwSleOPTma4tzEzJW51scn Y9/QJ9fJDWWJPmPN28aLaoPyhVxsGNHWMLMfnIC8jVH/DyQcDOT07jcUyihy21l3oU/8Yj /B2zNt1SzK56ltpAGugICcmyzlNHgLA=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-482-vZhu3aaUP3K35DlmBsVxgg-1; Mon, 30 Nov 2020 06:51:45 -0500
X-MC-Unique: vZhu3aaUP3K35DlmBsVxgg-1
Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id BB2DA107ACE6; Mon, 30 Nov 2020 11:51:43 +0000 (UTC)
Received: from localhost (holly.tpb.lab.eng.brq.redhat.com [10.43.134.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id E83A918996; Mon, 30 Nov 2020 11:51:42 +0000 (UTC)
Date: Mon, 30 Nov 2020 12:51:40 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Kurt Roeckx <kurt@roeckx.be>
Cc: g16 <g16g16g16@gmail.com>, ntp@ietf.org
Message-ID: <20201130115140.GI1826178@localhost>
References: <CAFZ=0SzC1cKbMf=9tNDdxYfde9UnD4CcLYZ2EGwvcKMEtp1i1w@mail.gmail.com> <20201129194332.GB971977@roeckx.be>
MIME-Version: 1.0
In-Reply-To: <20201129194332.GB971977@roeckx.be>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11
Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/2dqR71Z458NC9_JAyT2MHEPk6xQ>
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: Mon, 30 Nov 2020 11:51:50 -0000

On Sun, Nov 29, 2020 at 08:43:32PM +0100, Kurt Roeckx wrote:
> On Mon, Nov 30, 2020 at 12:49:09AM +0900, g16 wrote:
> > 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

My intention was to let the future NTPv6 specification describe how
older versions should be handled in the same way this draft allows an
NTPv5 server handle requests with versions 4 and older.

> does it have any text on what a client could do to talk to a
> server that supports older versions.

The client could try NTPv5 and see if it gets a valid response. This
would be similar to the proposed detection of the alternative port.

> 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.

I hope that won't be necessary.

-- 
Miroslav Lichvar