IETF Logo Mail Archive

[Ntp] Antw: [EXT] Re: ntpv5 requirements

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Thu, 16 February 2023 07:43 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 13E86C151700 for <ntp@ietfa.amsl.com>; Wed, 15 Feb 2023 23:43:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 RtcEWdfcq-Kv for <ntp@ietfa.amsl.com>; Wed, 15 Feb 2023 23:43:52 -0800 (PST)
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 23771C14F693 for <ntp@ietf.org>; Wed, 15 Feb 2023 23:43:49 -0800 (PST)
Received: from mx3.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 372DB6000052 for <ntp@ietf.org>; Thu, 16 Feb 2023 08:43:46 +0100 (CET)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx3.uni-regensburg.de (Postfix) with ESMTP id 17E20600004F for <ntp@ietf.org>; Thu, 16 Feb 2023 08:43:44 +0100 (CET)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Thu, 16 Feb 2023 08:43:45 +0100
Message-Id: <63EDDEAD020000A100052481@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.4.2
Date: Thu, 16 Feb 2023 08:43:41 +0100
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: Dieter Sibold <dsibold.ietf@gmail.com>, mlichvar@redhat.com
Cc: "ntp@ietf.org" <ntp@ietf.org>
References: <DB8PR02MB5772E45732B25646F7CAE211CFD99@DB8PR02MB5772.eurprd02.prod.outlook.com> <Y+pgBgc/5dJ9wtAP@localhost> <2bbcdc7b-a47c-8421-0278-0ac364faaeea@nwtime.org> <OF7B624B98.C1ECCBBE-ONC1258956.00440F55-C1258956.00448C93@ptb.de> <8bfc7ac6-7696-1ac8-c2a3-62aa0084e07f@nwtime.org> <B5BBCED7-23AB-435E-A512-1661A8E108BE@gmail.com> <Y+yvPytsVs6lTzyP@localhost> <617F4490-EDD3-4C54-94BF-68241B011111@gmail.com>
In-Reply-To: <617F4490-EDD3-4C54-94BF-68241B011111@gmail.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/pjiz9qUMF7nueIsiPUc3qHPQw0o>
Subject: [Ntp] Antw: [EXT] Re: ntpv5 requirements
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: Thu, 16 Feb 2023 07:43:56 -0000

>>> Dieter Sibold <dsibold.ietf@gmail.com> schrieb am 15.02.2023 um 20:02 in
Nachricht <617F4490-EDD3-4C54-94BF-68241B011111@gmail.com>:

[...]
>> 
> https://www.netnod.se/nts/nts-in-a-fpga-christer-weinigel-netnod-meeting-2022 
>> 
>> It's an interesting project, but those FPGAs are quite expensive. It
>> seems to me you can get much better performance/cost with common
>> x86-64 CPUs.
> 
> I agree. And for the majority of server the x86-64 CPUs will more than be 
> sufficient. But for extrem cases like the NIST it might be solution. This 
> might be more expensive than standard hardware but I suppose the majority of 
> metrology institutes could justify higher costs because in many cases they 
> are legally entrusted to disseminate time.

FPGAs, if used creatively, can provide quite nice features. For example:
Brocade Fibre Channel switches handle the FC protocol (and routing, AFAIK) completely in FPGAs. So you can reboot/upgrade the switch's operating system without interrupting the traffic. I think they call it a "HA reboot". Such concepts might be interesting for the PTB and NIST, but not for the average user IMHO.

Kind regards,
Ulrich Windl

v2.23.0 | Report a Bug | By Email