[Ntp] Antw: Re: Antw: Re: Antw: [EXT] NTPv5 Loop Detection without Stratum

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Wed, 31 August 2022 07:52 UTC

Return-Path: <Ulrich.Windl@rz.uni-regensburg.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 356B7C1522C3 for <ntp@ietfa.amsl.com>; Wed, 31 Aug 2022 00:52:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 m_Q4KN72QU0Z for <ntp@ietfa.amsl.com>; Wed, 31 Aug 2022 00:52:42 -0700 (PDT)
Received: from mx2.uni-regensburg.de (mx2.uni-regensburg.de [IPv6:2001:638:a05:137:165:0:3:bdf8]) (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 8C004C1522AD for <ntp@ietf.org>; Wed, 31 Aug 2022 00:52:42 -0700 (PDT)
Received: from mx2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 79BEF6000055 for <ntp@ietf.org>; Wed, 31 Aug 2022 09:52:40 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx2.uni-regensburg.de (Postfix) with ESMTP id 5F1D46000053 for <ntp@ietf.org>; Wed, 31 Aug 2022 09:52:40 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Wed, 31 Aug 2022 09:52:04 +0200
Message-Id: <630F1321020000A10004D377@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.4.1
Date: Wed, 31 Aug 2022 09:52:01 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: mlichvar@redhat.com, halmurray@sonic.net
Cc: "ntp@ietf.org" <ntp@ietf.org>, Heiko Gerstung <heiko.gerstung@meinberg.de>, mayer@pdmconsulting.net, david@venhoek.nl
References: <david@venhoek.nl> <CAPz_-SVPE-Fd1vFWnbu+GAPc=y2bkJMW4pyu98bBwDfcm+R2rg@mail.gmail.com> <20220830205143.DFDC328C1D8@107-137-68-211.lightspeed.sntcca.sbcglobal.net> <Yw8NBX6ATjRr0/A4@localhost> <C492F298020000C2AB59E961@gwsmtp.uni-regensburg.de> <F347640002000095FDA5B133@gwsmtp.uni-regensburg.de> <8F7E1DA8020000866A6A8CFC@gwsmtp.uni-regensburg.de>
In-Reply-To: <8F7E1DA8020000866A6A8CFC@gwsmtp.uni-regensburg.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/GhjMapHBYv6GmyZlBVIZ2GWGSRA>
Subject: [Ntp] Antw: Re: Antw: Re: Antw: [EXT] NTPv5 Loop Detection without Stratum
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: Wed, 31 Aug 2022 07:52:45 -0000

>>> Miroslav Lichvar <mlichvar@redhat.com> schrieb am 31.08.2022 um 09:25 in
Nachricht <Yw8NBX6ATjRr0/A4@localhost>:
> On Tue, Aug 30, 2022 at 01:51:43PM ‑0700, Hal Murray wrote:
>> That brings up an interesting point.
>> 
>> What does loop mean?
> 
> I think it's when a clock is synchronizing directly or indirectly
> (over one or more other clocks) to itself. As a test, you can inject a
> small offset to the server's clock and see if the impulse comes back
> later from one of its sources.

I think that is not sufficient: It would be a loop if the server's clock
(actually the error estimate) gets worse again, and then the process continues
(clock is getting more inaccurate over time). However it it's "smoothed out"
it's not a loop IMHO.

> 
> In the graph theory, it's a loop in a directed graph.

The problem is the "line" (correpsonding to time): In NTP it's a combination
of several sources (lines).

[...]

Regards,
Ulrich