IETF Logo Mail Archive

Re: [Ntp] Antw: [EXT] Re: CLOCK_TAI (was NTPv5: big picture)

Martin Burnicki <martin.burnicki@meinberg.de> Thu, 07 January 2021 15:53 UTC

Return-Path: <martin.burnicki@meinberg.de>
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 285F93A11FA for <ntp@ietfa.amsl.com>; Thu, 7 Jan 2021 07:53:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.361
X-Spam-Level:
X-Spam-Status: No, score=-2.361 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, NICE_REPLY_A=-0.262, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=meinberg.de
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 NXPFY6lFf4Kn for <ntp@ietfa.amsl.com>; Thu, 7 Jan 2021 07:53:27 -0800 (PST)
Received: from server1a.meinberg.de (server1a.meinberg.de [176.9.44.212]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64F053A0F3A for <ntp@ietf.org>; Thu, 7 Jan 2021 07:53:27 -0800 (PST)
Received: from srv-kerioconnect.py.meinberg.de (unknown [193.158.22.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by server1a.meinberg.de (Postfix) with ESMTPSA id EBC1071C0F51; Thu, 7 Jan 2021 16:53:24 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=meinberg.de; s=dkim; t=1610034805; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ija6twnf0+oe4RZL5TW2kyO4sVLnEKgZhGSMkcCd+nQ=; b=VLwxE/IUXw83sOdzI3s0TINW49eLukpg2cGbeL9l5V/xNWP6KUrg1WomzoBYvZTlBOSW4l 0939ZgRo5HCNvZQ0VnWNBLaLPLSR0jZH4c41Jle/yG2lT7WPZjuOsJyRrYdtqS4AzpMb5b wFMvxokfGWOiuki7HJhpob12YNtRv8SojjUN92ynZ25dVW44f8pkOiWf/k3C8l7C6mWXKt 2uP1LtTnclghq52HO6oa1IwSDVsFvrNbImCZchAy6ze4xikKLTPQos+IJsGRbMfUdQDcVJ nUSWwMlbHtRtQe71lavM2L6Gk/u2qy9nDSgJly3p1HfGej6VvZSHFkwuKBvm4A==
X-Footer: bWVpbmJlcmcuZGU=
Received: from localhost ([127.0.0.1]) by srv-kerioconnect.py.meinberg.de with ESMTPSA (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)); Thu, 7 Jan 2021 16:53:24 +0100
To: Hal Murray <hmurray@megapathdsl.net>, ntp@ietf.org
References: <20210107091330.11BF0406060@ip-64-139-1-69.sjc.megapath.net>
From: Martin Burnicki <martin.burnicki@meinberg.de>
Organization: Meinberg Funkuhren GmbH & Co. KG, Bad Pyrmont, Germany
Message-ID: <522782c2-4811-e7ba-4fcc-126adbbdaff4@meinberg.de>
Date: Thu, 07 Jan 2021 16:53:23 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <20210107091330.11BF0406060@ip-64-139-1-69.sjc.megapath.net>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/qUMg2t9AqO3jGV6V8NEM0g04XJg>
Subject: Re: [Ntp] Antw: [EXT] Re: CLOCK_TAI (was NTPv5: big picture)
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, 07 Jan 2021 15:53:30 -0000

Hal Murray wrote:
> 
> Ulrich.Windl@rz.uni-regensburg.de said:
>> My initial feeling is that a NTPv5 server should respond to v3 and v4
>> requests. If networks really have v2 clients or older, they'd need some
>> "gateway" to translate the time. 
> 
> Requests arriving at a pool server:
>     136711  0.221% NTPv1
>      10626  0.017% NTPv2
>   16845809 27.269% NTPv3
>   44782460 72.492% NTPv4
>          3  0.000% NTPv6 - length 48
>          1  0.000% NTPv6 - length 68

The v3 spec is from 1992 and was current when I first heard about NTP at
that time. In fact I've never seen a piece of software according to the
real specs for v1 or v2.

I think the at least the v1 and maybe the v2 packets just originate from
dump implementations that send and expect the standard v3/v4 packet but
put a wrong version code into the request.

Over the years I've seen several reports about such clients.

I don't know which request exactly have been counted, but v2 requests
can also be mode 6 packets sent by clients when trying to find out
details about the server.

I wonder if the v6 packets are real clients, or just someone who is
trying to find out if and what a server responds when it receives such a
request.


Martin
-- 
Martin Burnicki

Senior Software Engineer

MEINBERG Funkuhren GmbH & Co. KG
Email: martin.burnicki@meinberg.de
Phone: +49 5281 9309-414
Linkedin: https://www.linkedin.com/in/martinburnicki/

Lange Wand 9, 31812 Bad Pyrmont, Germany
Amtsgericht Hannover 17HRA 100322
Geschäftsführer/Managing Directors: Günter Meinberg, Werner Meinberg,
Andre Hartmann, Heiko Gerstung
Websites: https://www.meinberg.de  https://www.meinbergglobal.com
Training: https://www.meinberg.academy

v2.23.0 | Report a Bug | By Email