[Ntp] Re: NTPv4 client behavior to ntpv3 reply
rémy decrock <rmdck@rmdck.fr> Tue, 30 July 2024 08:00 UTC
Return-Path: <rmdck@rmdck.fr>
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 4E2F6C14F700 for <ntp@ietfa.amsl.com>; Tue, 30 Jul 2024 01:00:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.65
X-Spam-Level:
X-Spam-Status: No, score=-6.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.455, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rmdck.fr
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 nWARCDk7H7qs for <ntp@ietfa.amsl.com>; Tue, 30 Jul 2024 01:00:30 -0700 (PDT)
Received: from wilbur.contactoffice.com (wilbur.contactoffice.com [212.3.242.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3F23C14F6FA for <ntp@ietf.org>; Tue, 30 Jul 2024 01:00:30 -0700 (PDT)
Received: from ichabod.co-bxl (ichabod.co-bxl [10.2.0.36]) by wilbur.contactoffice.com (Postfix) with ESMTP id D041C80B1; Tue, 30 Jul 2024 10:00:27 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1722326427; s=20220130-ieei; d=rmdck.fr; i=rmdck@rmdck.fr; h=Date:From:To:Message-ID:In-Reply-To:References:Subject:MIME-Version:Content-Type; bh=jI/d5FKfvTF9mQCAHjigLCO5f2oyvEMlA2wsDRRljZM=; b=LN39AiKPb4q5vV640n84Y3PSVjqjjAsPNYNm5aiz0aDCZPLGgoCD5E2enktYfOWq 7VawrkRjkqt9i59Rwr3myZHlaWqmwYdwMIOVhVfuyRph006KBe9UqnW9/3ou+RkCt3E sdz84yLCxYjXKBtzUyMO6FiKI4jfhKmq2KhYtDerSUEgVNFVerpy8n5GihJB4CPDW9E f6MbHDgpVrYBJHX41lf4kydgjJ8qUM6IlM9VoQ7M4/NDFjv1LVuXztXGsJb8w10RdmY R+tRumZ2DcWQtvyldOg/0nz12Ai3Vzus2yadGsE52jYNBFbEuVrlzDhA3lB9/weRJgW gF3NNuD/ww==
Date: Tue, 30 Jul 2024 10:00:25 +0200
From: rémy decrock <rmdck@rmdck.fr>
To: Harlan Stenn <stenn=40ntp.org@dmarc.ietf.org>, ntp@ietf.org
Message-ID: <633834849.717533.1722326425298@ichabod.co-bxl>
In-Reply-To: <89926b1b-e909-4f4d-8d13-ecf43d6ddd59@ntp.org>
References: <499016286.658450.1722265918944@ichabod.co-bxl> <89926b1b-e909-4f4d-8d13-ecf43d6ddd59@ntp.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_717531_968615589.1722326425297"
X-Mailer: ContactOffice Mail
X-ContactOffice-Account: com:305125439
Message-ID-Hash: 6ES5G6MJ7BWGFS5PYFDBZAKO2N6PQWZ3
X-Message-ID-Hash: 6ES5G6MJ7BWGFS5PYFDBZAKO2N6PQWZ3
X-MailFrom: rmdck@rmdck.fr
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ntp.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Ntp] Re: NTPv4 client behavior to ntpv3 reply
List-Id: Network Time Protocol <ntp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/50QrcoE48K5lQPiDDuxFcgTClGI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Owner: <mailto:ntp-owner@ietf.org>
List-Post: <mailto:ntp@ietf.org>
List-Subscribe: <mailto:ntp-join@ietf.org>
List-Unsubscribe: <mailto:ntp-leave@ietf.org>
Thank you Harlan for the answer. The issue behind my question is that I have an equipment that uses a NTPv4 client and so perform ntpv4 requests to a server that only support NTPv3 "Windows..." The server replies to my equipment but with a NTPv3 answer and seems to be ignored. Before creating a bug request to the vendor, I want to be sure that this behavior is illegitimate or not. Le 30 juil. 2024 à 02:09, Harlan Stenn <stenn=40ntp.org@dmarc.ietf.org> a écrit :On 7/29/2024 8:11 AM, rémy decrock wrote: > Hello, > > I have a question about the NTP v4-v3 compatiblity. > According to the RFC https://datatracker.ietf.org/doc/rfc5905/, v3 and > v4 are compatible. > By compatible, I understand that if a client perform an NTPv3 request > to a NTPv4 server, this one is able to answer in an understandable way > to the client. > But what if a NTPv4 client receives an NTPv3 reply to his NTPv4 requests? "It depends." I say this because the reference implementation replies with the packet format it knows about, using the version field from the request. So you will not see the case you describe from the reference implementation. We took great pains to make sure clients and servers running different NTP versions would interoperate successfully. If the V3 server was written by somebody else, it will behave the way it will behave. The first/early release of NTPv4 happened before February 1998. The last release of NTPv3 was in November of 1998. There were no interoperability complaints around the switch from v3 to v4. NTPv3 has not been supported for over 25 years' time. I gotta wonder how many v3 servers are actually still running out there. > Thanks. > > _______________________________________________ > ntp mailing list -- ntp@ietf.org > To unsubscribe send an email to ntp-leave@ietf.org -- Harlan Stenn <stenn@ntp.org> The NTP Project is part of https://www.nwtime.org/ - be a member! _______________________________________________ ntp mailing list -- ntp@ietf.org To unsubscribe send an email to ntp-leave@ietf.org
- [Ntp] Re: NTPv4 client behavior to ntpv3 reply Harlan Stenn
- [Ntp] NTPv4 client behavior to ntpv3 reply rémy decrock
- [Ntp] Re: NTPv4 client behavior to ntpv3 reply rémy decrock
- [Ntp] Re: NTPv4 client behavior to ntpv3 reply Harlan Stenn
- [Ntp] Re: NTPv4 client behavior to ntpv3 reply Martin Burnicki