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

Heiko Gerstung <heiko.gerstung@meinberg.de> Tue, 16 August 2022 11:18 UTC

Return-Path: <heiko.gerstung@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 2DB08C159524 for <ntp@ietfa.amsl.com>; Tue, 16 Aug 2022 04:18:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, RCVD_IN_DNSWL_BLOCKED=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_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 FxErMHoI1xG3 for <ntp@ietfa.amsl.com>; Tue, 16 Aug 2022 04:18:27 -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 836DEC15AE1D for <ntp@ietf.org>; Tue, 16 Aug 2022 04:18:27 -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 F010671C0132; Tue, 16 Aug 2022 13:18:24 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=meinberg.de; s=d2021; t=1660648705; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=/UX/qQhaawfhYCaWJB36lQ+ZRldjYGyc7I0WgUt7gek=; b=Pd9wI3vuiJihnLOO3LHF+jwW25yMNXPkJqHUccE4/FwvL83vWlH3ALWIT/g2fiVywHpRR5 j3mpeoJ8Fi9pKaQDWWXxa5n3Q+cFpGkJiijvwwB39HRSnSah+52OMDm1Z4NDKFYpSJfr42 PmFaf/q7sTVvSJsuYIFndx/pNeJhPC4Oe649b3tDYLfsYI0+jGZKCLccD5ffiNvDl8Kxte KypLskpnudt7kerZkNfeLt57BVtpBccvvMX5KcdzK9dfQUYdq+2tUdL2osDHjppbaFleoa 3oyO6ZEPKSJHPzTzCKE/oV8BWEzaK3yL4apvE8ZIhqqPPdHt8JtF5k9msYzhJQ==
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, 16 Aug 2022 13:18:24 +0200 (CEST)
X-Footer: bWVpbmJlcmcuZGU=
User-Agent: Microsoft-MacOutlook/16.63.22070801
Date: Tue, 16 Aug 2022 13:18:22 +0200
Message-ID: <5149BD55-E4A2-40B9-AFB1-9F69AAA319C8@meinberg.de>
Thread-Topic: [Ntp] Antw: [EXT] Re: Quick review of WGLC for status change for draft-ietf-ntp-update-registries
References: <PH0PR06MB7061FA7A5B338D262B3A2963C2999@PH0PR06MB7061.namprd06.prod.outlook.com> <PH0PR06MB706126984E4442EF32F8242AC2999@PH0PR06MB7061.namprd06.prod.outlook.com> <da155c84-2c70-2e3b-59eb-03e380806cf2@nwtime.org> <PH0PR06MB70611F2331D8255F7E2B6604C2999@PH0PR06MB7061.namprd06.prod.outlook.com> <0b4c7efa-3977-b588-0974-33b6a9437e52@nwtime.org> <YvDWC27qKnODlD52@localhost> <0b57b7db-772e-f5e6-e6a0-a433673f3d77@nwtime.org> <YvED7T5R0UsRWbv3@localhost> <b64c6a0a-ea2e-0a19-4bb9-38bfaa2e5032@nwtime.org> <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> <22DC6703-ADFA-45BA-B26D-3DB7E957D0F3@meinberg.de>
In-Reply-To: <22DC6703-ADFA-45BA-B26D-3DB7E957D0F3@meinberg.de>
Importance: Normal
X-Priority: 3
Thread-Index: AZ2x3tU+ZTYyMDA2ZGIxOTEwYjk0Mw==
From: Heiko Gerstung <heiko.gerstung@meinberg.de>
To: Heiko Gerstung <heiko.gerstung=40meinberg.de@dmarc.ietf.org>, Harlan Stenn <stenn@nwtime.org>, Ulrich Windl <ulrich.windl@rz.uni-regensburg.de>, "ntp@ietf.org" <ntp@ietf.org>
X-SM-outgoing: yes
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="----D9A51C970044A791C37B792F20ADC01F"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/EYo2pATyU-Ys1ffQ470Xa-ESLpY>
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 11:18:35 -0000

OK, I checked and found out that the ntpq tool in 4.2.8p13 is sending all queries with VN=2 - therefore ntpd is responding with the same version. 

As it seems, there is no standard describing/defining mode 6 or mode 7, so maybe we should treat both as "vendor/implementation specific"?

Regards,
  Heiko

Am 16.08.22, 13:10 schrieb "ntp im Auftrag von Heiko Gerstung" <ntp-bounces@ietf.org im Auftrag von heiko.gerstung=40meinberg.de@dmarc.ietf.org>:

    The RFC says 
    " VN Version Number (version): 3-bit integer representing the NTP
       version number, currently 4."

    It does not make any exceptions for different modes, so why should the meaning of the version number field be different for mode 6 packets? I did not find anything in RFC5905 about mode 6 packets. 

    Regards,
      Heiko

    --
    Heiko Gerstung | Managing Director
    T: +49 (0)5281 9309-404 | LinkedIn Profile <https://www.linkedin.com/in/heikogerstung/> | Twitter <https://twitter.com/hgerstung>
    heiko.gerstung@meinberg.de

    MEINBERG® The Synchronization Experts

    Meinberg Funkuhren GmbH & Co. KG
    Lange Wand 9 | 31812 Bad Pyrmont | Germany
    Web: http://www.meinberg.de | http://www.meinbergglobal.com | LinkedIn  <https://www.linkedin.com/company/meinberg-funkuhren-gmbh-&-co--kg>

    Amtsgericht Hannover 17HRA 100322
    Geschäftsführer/Management: Günter Meinberg, Werner Meinberg, Andre Hartmann, Heiko Gerstung

    Do not miss our Time Synchronization Blog:
    http://blog.meinbergglobal.com



    Am 16.08.22, 11:22 schrieb "ntp im Auftrag von Harlan Stenn" <ntp-bounces@ietf.org im Auftrag von stenn@nwtime.org>:

        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
        > <4f833218-231f-8c47-e529-b3ba00f6554e@nwtime.org>:
        > ...
        >> So if we're a V4 server and we get a v5 request, we will respond with a
        >> v4 packet that says v5.
        >>
        >> This is consistent with the design.
        >>
        >> No one has seen a v1 packet format in a very long time.  The v1 stuff
        >> folks are seeing now are v[234] packets claiming to be v1.
        >>
        >> The format of the base packet saw a slight change going from v2 to v3
        >> (sync dispersion was replaced by estimated drift rate), and there was
        >> (TTBOMK) no change to the base packet from v3 to v4.
        >>
        >> 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?

        -- 
        Harlan Stenn <stenn@nwtime.org>
        http://networktimefoundation.org - be a member!

        _______________________________________________
        ntp mailing list
        ntp@ietf.org
        https://www.ietf.org/mailman/listinfo/ntp

    _______________________________________________
    ntp mailing list
    ntp@ietf.org
    https://www.ietf.org/mailman/listinfo/ntp