Re: [Ntp] Costs of running NTP servers
Miroslav Lichvar <mlichvar@redhat.com> Thu, 16 February 2023 09:55 UTC
Return-Path: <mlichvar@redhat.com>
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 6C49CC14CE2C for <ntp@ietfa.amsl.com>; Thu, 16 Feb 2023 01:55:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com
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 j5EFAfVtGLJ7 for <ntp@ietfa.amsl.com>; Thu, 16 Feb 2023 01:55:13 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 D04E1C14F748 for <ntp@ietf.org>; Thu, 16 Feb 2023 01:55:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1676541311; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=THOIEAgraHqnx5liIvdJemCIi5VNazrrF+t39NNjUBE=; b=bdeRzwLL2n5CaXHpSqEdnSJ/NgELl1LDm3dNWYD77b9qRNVmfKE7IVeTgXndIXXPsisIVg cdeT31hSldNOwz2F/IgA/zikeBPEiZrFWUMhln/oE18KxLPdVw6J0ZA8L0hSakknFwHacu Vw53bHLjQ9z1rEtYANFPH6bgBsxzUCc=
Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-128-Si7TNt_5O5uD3YSol-7Guw-1; Thu, 16 Feb 2023 04:55:08 -0500
X-MC-Unique: Si7TNt_5O5uD3YSol-7Guw-1
Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id B8802811E6E; Thu, 16 Feb 2023 09:55:07 +0000 (UTC)
Received: from localhost (unknown [10.43.135.229]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 271372026D4B; Thu, 16 Feb 2023 09:55:07 +0000 (UTC)
Date: Thu, 16 Feb 2023 10:55:05 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Hal Murray <halmurray@sonic.net>
Cc: ntp@ietf.org
Message-ID: <Y+39eYbVorHQfdp1@localhost>
References: <mlichvar@redhat.com> <Y+yvPytsVs6lTzyP@localhost> <20230215204606.B438728C211@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
MIME-Version: 1.0
In-Reply-To: <20230215204606.B438728C211@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
X-Scanned-By: MIMEDefang 3.1 on 10.11.54.4
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/o8zpz0T_StUxvLGf_myeNJ-0OWQ>
Subject: Re: [Ntp] Costs of running NTP servers
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 09:55:17 -0000
On Wed, Feb 15, 2023 at 12:46:06PM -0800, Hal Murray wrote: > What are the costs of running a high traffic NTP server? Or collection of > servers? Something on the scale of NIST or PTB? 1M/s of plain NTP is about 230 TB/month in one direction. If it was NTS-NTP with 1 cookie using AES-SIV-CMAC, it would be about 700 TB/month. For an individual at home or an ordinary company using cheap hardware and not caring much about availability and reliability (using a single server), the traffic cost would probably be the most expensive part of the operation. I'd not expect NIST to care much about traffic. I suspect the issue they have with NTS is not the computation cost, but the complexity of implementation. A plain NTP server is trivial. It can be implemented from scratch in an hour. NTS with its dependency on TLS is much more work. NIST runs their own NTP implementation and I guess they for some reason cannot or don't want to switch to an existing implementation. -- Miroslav Lichvar
- [Ntp] ntpv5 requirements Doug Arnold
- Re: [Ntp] ntpv5 requirements James
- Re: [Ntp] ntpv5 requirements Dieter Sibold
- Re: [Ntp] ntpv5 requirements Miroslav Lichvar
- Re: [Ntp] ntpv5 requirements Doug Arnold
- Re: [Ntp] ntpv5 requirements Harlan Stenn
- Re: [Ntp] ntpv5 requirements Hal Murray
- Re: [Ntp] ntpv5 requirements Miroslav Lichvar
- Re: [Ntp] ntpv5 requirements kristof.teichel
- Re: [Ntp] ntpv5 requirements Doug Arnold
- Re: [Ntp] ntpv5 requirements Miroslav Lichvar
- Re: [Ntp] ntpv5 requirements Harlan Stenn
- Re: [Ntp] ntpv5 requirements Dieter Sibold
- Re: [Ntp] ntpv5 requirements kristof.teichel
- Re: [Ntp] ntpv5 requirements kristof.teichel
- Re: [Ntp] ntpv5 requirements Miroslav Lichvar
- [Ntp] Costs of running NTP servers Hal Murray
- Re: [Ntp] ntpv5 requirements Dieter Sibold
- [Ntp] Antw: [EXT] Re: ntpv5 requirements Ulrich Windl
- Re: [Ntp] Costs of running NTP servers Miroslav Lichvar
- Re: [Ntp] ntpv5 requirements Harlan Stenn
- Re: [Ntp] ntpv5 requirements kristof.teichel