IETF Logo Mail Archive

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

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Fri, 22 October 2021 08:02 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 B2A8D3A08D3 for <ntp@ietfa.amsl.com>; Fri, 22 Oct 2021 01:02:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 i7bVKJx4eugK for <ntp@ietfa.amsl.com>; Fri, 22 Oct 2021 01:02:46 -0700 (PDT)
Received: from mx4.uni-regensburg.de (mx4.uni-regensburg.de [IPv6:2001:638:a05:137:165:0:4:4e7a]) (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 696283A08C7 for <ntp@ietf.org>; Fri, 22 Oct 2021 01:02:46 -0700 (PDT)
Received: from mx4.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 87D106000052 for <ntp@ietf.org>; Fri, 22 Oct 2021 10:02:42 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx4.uni-regensburg.de (Postfix) with ESMTP id 745926000051 for <ntp@ietf.org>; Fri, 22 Oct 2021 10:02:42 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Fri, 22 Oct 2021 10:02:42 +0200
Message-Id: <61727020020000A100044BE7@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.1
Date: Fri, 22 Oct 2021 10:02:40 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: doug.arnold=40meinberg-usa.com@dmarc.ietf.org, 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> <61714B21020000A100044B83@gwsmtp.uni-regensburg.de> <AM7PR02MB576513760641C35EB5B43673CFBF9@AM7PR02MB5765.eurprd02.prod.outlook.com>
In-Reply-To: <AM7PR02MB576513760641C35EB5B43673CFBF9@AM7PR02MB5765.eurprd02.prod.outlook.com>
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/IsBnKKWG7GUUN3_x3VKGBBbgl2g>
Subject: [Ntp] Antw: Re: 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: Fri, 22 Oct 2021 08:02:52 -0000

>>> Doug Arnold <doug.arnold=40meinberg-usa.com@dmarc.ietf.org> schrieb am
21.10.2021 um 15:36 in Nachricht
<AM7PR02MB576513760641C35EB5B43673CFBF9@AM7PR02MB5765.eurprd02.prod.outlook.com>

> One thing to keep in mind is that the use case for leap smearing is that it 
> happens in a private network, where all Stratum 1 servers are configured the 
> same.  I still consider it dangerous, though.

We could demand that a smearing server may only respond to authenticated packets (maybe even specific keys), so clients expecting leap smear would have to provide some cryptographic key to the server.
A clients querying the server by mistake wuld not get a response then.

Regards,
Ulrich

v2.23.0 | Report a Bug | By Email