IETF Logo Mail Archive

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

Martin Burnicki <martin.burnicki@meinberg.de> Tue, 09 August 2022 10:46 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 E8991C13CCE2 for <ntp@ietfa.amsl.com>; Tue, 9 Aug 2022 03:46:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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=meinberg.de
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 sn5XJXbsEQx1 for <ntp@ietfa.amsl.com>; Tue, 9 Aug 2022 03:46:11 -0700 (PDT)
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 25023C14F718 for <ntp@ietf.org>; Tue, 9 Aug 2022 03:46:10 -0700 (PDT)
Received: from seppmail.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 47F4671C0065; Tue, 9 Aug 2022 12:46:07 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=meinberg.de; s=d2021; t=1660041967; 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=c2SEDnS2IgZuaPMsJMWfH1ZLoZXKu53YdQFdD9aj/Wk=; b=WbaycEWprzAVr5Z8KA2C7EaMyIKodOmhHQRuye4hbWXVDvsHcMfojjsPuYmp4EGAlGqjLN YLi0dkK+U3cMJsHE59oWbxadwW076Mf5eDFs9vXIqZcgSIy8KUsVMmE+VeZE6t6+rnbnP2 KdJXfWu3X9514SNDW4BDjoVlKf4Di8gFntMu2DRTA+qD+KwTh8i92Wp3qQ+SprTLEh12yK VdeMMayPkhtZ0qGX8Nc22lWm6YnfH2teXvsyxUJzNCOOcGqqPGnisxnianjQ0sc0FZbllI tvalIjEseYsw4TfsWL7Z0TeDqQMbJ4Lu7ZmfKhmOPHPtO/aJHuAh9BdXvRQJPg==
Received: from srv-kerioconnect.py.meinberg.de (srv-kerioconnect.py.meinberg.de [172.16.3.65]) (using TLSv1.3 with cipher AEAD-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by seppmail.py.meinberg.de (Postfix) with ESMTPS; Tue, 9 Aug 2022 12:46:06 +0200 (CEST)
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)); Tue, 9 Aug 2022 12:46:05 +0200
Message-ID: <814ad60b-c655-8396-6457-b83fa20cbeda@meinberg.de>
Date: Tue, 09 Aug 2022 12:46:05 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0
Content-Language: en-US
To: Hal Murray <halmurray@sonic.net>
Cc: Miroslav Lichvar <mlichvar@redhat.com>, "ntp@ietf.org" <ntp@ietf.org>, Harlan Stenn <stenn@nwtime.org>
References: <20220809103929.01C4B28C1CA@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
From: Martin Burnicki <martin.burnicki@meinberg.de>
Organization: Meinberg Funkuhren GmbH & Co. KG, Bad Pyrmont, Germany
In-Reply-To: <20220809103929.01C4B28C1CA@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="------------BaQFoMkdFYj9Y1aQ6wNaJCgm"
X-SM-outgoing: yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/BvxzVfJFIEYPsIEotdxgCrD-cpY>
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, 09 Aug 2022 10:46:16 -0000

Hal Murray wrote:
> 
>> I haven't seen any v1 clients in ages.  For that matter, I don't think  I've
>> ever seen a v1 client request come in (OK, nobody has reported that  they
>> could not sync a v1 client with a v3 or a v4 server).
> 
> You haven't looked very hard.  Ballpark of 1% at pool servers.

Really v1 implementations that are decades old?

Or just the result of software developers that write their own NTP 
client, didn't look at the specs, and simply put v1 into the request 
packets that in fact have a v4 format?

> We (NTPsec) dropped support for V1 and got a bug report.
> 
> It's not just 20 year old modems.  I have credible reports that modern gear is
> doing it too.  I assume they are just carrying along old code - if it ain't
> broke, don't fix it.

That's what I mean, and I doubt that only 20 year old devices send v1 
requests.

> I think we need a serious discussion about SNTP and support lifetimes.  I'll
> start another thread when I get a chance.

I'm not even sure that you can call these faulty client implementations 
"SNTP".


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

v2.23.0 | Report a Bug | By Email