IETF Logo Mail Archive

Re: [Ntp] Antw: [EXT] Re: NTPv5 Loop Detection without Stratum ‑ Why do we want this?

Harlan Stenn <stenn@nwtime.org> Wed, 21 September 2022 06:47 UTC

Return-Path: <stenn@nwtime.org>
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 C0BD3C1522AC for <ntp@ietfa.amsl.com>; Tue, 20 Sep 2022 23:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.106
X-Spam-Level:
X-Spam-Status: No, score=-1.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 OJZ7KGPnvHrr for <ntp@ietfa.amsl.com>; Tue, 20 Sep 2022 23:47:00 -0700 (PDT)
Received: from chessie.everett.org (unknown [IPv6:2001:470:1:205::234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C042C1522A2 for <ntp@ietf.org>; Tue, 20 Sep 2022 23:46:58 -0700 (PDT)
Received: from [10.208.75.149] (071-084-168-128.res.spectrum.com [71.84.168.128]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4MXTGz1y65zMP96; Wed, 21 Sep 2022 06:37:15 +0000 (UTC)
Message-ID: <d3c50d33-d6aa-4c09-dd6a-e94de3e9dacc@nwtime.org>
Date: Tue, 20 Sep 2022 23:37:14 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2
Content-Language: en-US
To: ntp@ietf.org
References: <DA1F1664-8A84-4197-844A-CA7E8DAA36B8@meinberg.de> <OF43150191.DABAA331-ONC12588B5.00362DC0-C12588B5.003861AF@ptb.de> <YxckOm2+TD3tTPN4@localhost> <7d7f0656-2fd2-b781-4913-526a4be8cb62@pdmconsulting.net> <Yxg4Cba58hI/aPKw@localhost> <aba44bbc-2204-735e-daff-a29a59dac9da@pdmconsulting.net> <YxmKlSVTzOQah/nc@localhost> <10b1b402-9386-4fb3-4297-38d31bdc5c96@pdmconsulting.net> <Yx8I6sTGKTLKJr8c@localhost> <796c33e6-02dc-0665-c8a2-a143f9100bdd@pdmconsulting.net> <Yygb4pt5JdyIszWU@localhost> <23f26126-c39e-16ea-d862-c8ac706e37d5@pdmconsulting.net> <632AA6E7020000A10004DF22@gwsmtp.uni-regensburg.de>
From: Harlan Stenn <stenn@nwtime.org>
In-Reply-To: <632AA6E7020000A10004DF22@gwsmtp.uni-regensburg.de>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/FszmjivXQN6O1dCZN1lDE2cE45E>
Subject: Re: [Ntp] Antw: [EXT] Re: NTPv5 Loop Detection without Stratum ‑ Why do we want this?
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, 21 Sep 2022 06:47:04 -0000

On 9/20/2022 10:53 PM, Ulrich Windl wrote:
>>>> Danny Mayer <mayer@pdmconsulting.net> schrieb am 20.09.2022 um 15:37 in
> Nachricht <23f26126-c39e-16ea-d862-c8ac706e37d5@pdmconsulting.net>:
> 
> ...
>>> Can you please tell us in which file and on what line we can see that
>>> difference in handling of measurements made in client/server mode and
>>> symmetric mode?
>>
>> It's in there. If you don't want to read code you can read some of Dave
>> Mills's papers. Here's one document reference and I'm sure that you can
>> search for others. His book also talks about it.
>>
>> https://doc.ntp.org/reflib/onwire/
> 
> Having the RFCs, the source code of the reference implementation, and the Mills paper, does not make things easier.
> Ideally the RFCs would cover everything one needs to know.
> 
> ...

LOL!

Thanks for the laugh, Ulrich!

> Regards,
> Ulrich
> 
> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org
> https://www.ietf.org/mailman/listinfo/ntp
> 

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

v2.23.0 | Report a Bug | By Email