IETF Logo Mail Archive

[Ntp] Antw: Re: Antw: [EXT] Re: New Version Notification for draft‑gruessing‑ntp‑ntpv5‑requirements‑03.txt

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Thu, 21 October 2021 11:12 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 1ACF53A157D for <ntp@ietfa.amsl.com>; Thu, 21 Oct 2021 04:12:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 dwPI5i-7UGVh for <ntp@ietfa.amsl.com>; Thu, 21 Oct 2021 04:12:43 -0700 (PDT)
Received: from mx3.uni-regensburg.de (mx3.uni-regensburg.de [194.94.157.148]) (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 9F1183A157B for <ntp@ietf.org>; Thu, 21 Oct 2021 04:12:42 -0700 (PDT)
Received: from mx3.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 50B3D6000054 for <ntp@ietf.org>; Thu, 21 Oct 2021 13:12:38 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx3.uni-regensburg.de (Postfix) with ESMTP id 415FB600004A for <ntp@ietf.org>; Thu, 21 Oct 2021 13:12:35 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Thu, 21 Oct 2021 13:12:35 +0200
Message-Id: <61714B21020000A100044B83@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.1
Date: Thu, 21 Oct 2021 13:12:33 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: mlichvar@redhat.com, halmurray+ietf@sonic.net
Cc: "ntp@ietf.org" <ntp@ietf.org>
References: <D19C98F0020000AAAB822621@gwsmtp.uni-regensburg.de> <B6193D9D02000051AB59E961@gwsmtp.uni-regensburg.de> <84735FB40200007C44DF974D@gwsmtp.uni-regensburg.de> <236983740200003E824A10E1@gwsmtp.uni-regensburg.de> <CEFD0B92020000436A6A8CFC@gwsmtp.uni-regensburg.de> <616E7B69020000A10004491E@gwsmtp.uni-regensburg.de> <DB577C29020000EF6A6A8CFC@gwsmtp.uni-regensburg.de> <616E933D020000A100044957@gwsmtp.uni-regensburg.de> <72083C72020000E06A6A8CFC@gwsmtp.uni-regensburg.de> <D11527C602000032FDA5B133@gwsmtp.uni-regensburg.de> <9E2EA18B020000B86A6A8CFC@gwsmtp.uni-regensburg.de> <6EFADD85020000BDFDA5B133@gwsmtp.uni-regensburg.de>
In-Reply-To: <6EFADD85020000BDFDA5B133@gwsmtp.uni-regensburg.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/oiQIKYYJFLolEgNW2GMIsiH4pEQ>
Subject: [Ntp] Antw: Re: Antw: [EXT] Re: New Version Notification for draft‑gruessing‑ntp‑ntpv5‑requirements‑03.txt
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 21 Oct 2021 11:12:48 -0000

>>> Hal Murray <halmurray+ietf@sonic.net> schrieb am 21.10.2021 um 11:20 in
Nachricht
<20211021092000.13DDD28C157@107-137-68-211.lightspeed.sntcca.sbcglobal.net>:

...
> The root of the problem is smearing.  The current implementation hides it 
> from 
> the client software.
...

I wondered: Requiring that smearing servers lower (increase) their startum by one or two?
So when mixing sources, the non-smearing servers might win the selection.

An other question: Can a smearing server be confused when getting smeared time from another smearing server?
(something like: time is "t", but server smeared it to "t-0.5". The receiving server thinks it has to smear it to "t-0.5-1" eventually.)

Regards,
Ulrich

v2.23.0 | Report a Bug | By Email