IETF Logo Mail Archive

Re: [Ntp] Antw: [EXT] Re: Quick review of WGLC for status change for draft-ietf-ntp-update-registries

Miroslav Lichvar <mlichvar@redhat.com> Tue, 16 August 2022 10:57 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 04FB7C15AE15 for <ntp@ietfa.amsl.com>; Tue, 16 Aug 2022 03:57:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.678
X-Spam-Level:
X-Spam-Status: No, score=-2.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.571, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ECy2jLWaDfr2 for <ntp@ietfa.amsl.com>; Tue, 16 Aug 2022 03:57:28 -0700 (PDT)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (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 7D2D7C1522AD for <ntp@ietf.org>; Tue, 16 Aug 2022 03:57:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1660647447; 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=1tWKWBRGNuv59NFyKMDP70lVcmbyrOWr38aRALN38AM=; b=bB/RLT5vmH1GSdrM1MXjSKhZNXRHniPr7szTBjbaJut2nDjUaWqXEkMh6VhtNSPzjYk/p7 G5mg70bjlgqZ+tMRNgzXofuexZaP3MTmSYYhVycpatFtHS/pDq5bYeXecf+e+Egyh5bcN7 9hE+yUJIulVGRjDOEbVwhKBz05fDGE0=
Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-610-brhnmMFuNret6wmRAvphPw-1; Tue, 16 Aug 2022 06:57:18 -0400
X-MC-Unique: brhnmMFuNret6wmRAvphPw-1
Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 25B121C068D4; Tue, 16 Aug 2022 10:57:18 +0000 (UTC)
Received: from localhost (unknown [10.43.135.229]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 59614492C3B; Tue, 16 Aug 2022 10:57:16 +0000 (UTC)
Date: Tue, 16 Aug 2022 12:57:15 +0200
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Harlan Stenn <stenn@nwtime.org>
Cc: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>, "ntp@ietf.org" <ntp@ietf.org>, Heiko Gerstung <heiko.gerstung@meinberg.de>
Message-ID: <Yvt4C97N+I51c54v@localhost>
References: <656D355F-E06A-4005-B9D6-90885FA8509D@akamai.com> <1a4bae28-f0f3-e675-899a-bad597b4ee29@nwtime.org> <F74A7B5B-3D77-42AF-BD7E-1A874CCD2D66@akamai.com> <67545c9a-3291-bbe6-c876-4c762c80c710@nwtime.org> <FF22AEFE-ED61-405E-AB40-B7901D0CD588@meinberg.de> <f79cecd6-92b0-595b-e449-6b6f8944ae66@nwtime.org> <133C5633-E4D5-42AF-8215-E3FDE28C5BF9@meinberg.de> <4f833218-231f-8c47-e529-b3ba00f6554e@nwtime.org> <62FB5EDB020000A10004C5CD@gwsmtp.uni-regensburg.de> <a89aeba9-5e88-2214-634f-7a9a7106eec3@nwtime.org>
MIME-Version: 1.0
In-Reply-To: <a89aeba9-5e88-2214-634f-7a9a7106eec3@nwtime.org>
X-Scanned-By: MIMEDefang 2.85 on 10.11.54.10
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/1lsIFoK9vW6pj9v_ZrXTF9WOlFE>
Subject: Re: [Ntp] Antw: [EXT] Re: Quick review of WGLC for status change for draft-ietf-ntp-update-registries
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Network Time Protocol <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: Tue, 16 Aug 2022 10:57:32 -0000

On Tue, Aug 16, 2022 at 02:21:54AM -0700, Harlan Stenn wrote:
> On 8/16/2022 2:09 AM, Ulrich Windl wrote:
> > > > > Harlan Stenn <stenn@nwtime.org> schrieb am 15.08.2022 um 23:53 in Nachricht
> > > The change from v2 to v3 caused no problems that I can recall, and even
> > > so, I'm unaware of ANY surviving v2 servers out there.
> > 
> > Well, ntpq 4.2.8p15 is using version==2 when doing mode 6 queries, so there are V2 packets!
> 
> What exactly does the version field mean in a mode 6 packet?

I'd expect most people to assume that the version field indicates the
protocol version, same as for the timing modes.

Here is how the version field in the "Control message format" is
described in the previous NTP versions and the current NTPv4 draft:

RFC1119 (NTPv2):
  Version Number (VN): This is a three-bit integer indicating the NTP
  version number, currently two (2).

RFC1305 (NTPv3):
  Version Number (VN): This is a three-bit integer indicating the NTP
  version number, currently three (3).

draft-ietf-ntp-mode-6-cmds-11 (NTPv4):
  Version Number (VN): This is a three-bit integer indicating a
  minimum NTP version number.  NTP servers do not respond to control
  messages with an unrecognized version number.  Requests may
  intentionally use a lower version number to enable interoperability
  with earlier versions of NTP.  Responses carry the same version as
  the corresponding request.

I like how it explicitly says that servers are not supposed to respond
to unsupported versions.

Are there any client implementations using the NTPv4 control mode?

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email