IETF Logo Mail Archive

Re: [Ntp] NTS-KE server load pulse

Miroslav Lichvar <mlichvar@redhat.com> Thu, 01 February 2024 08:18 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 69BBCC14CE25 for <ntp@ietfa.amsl.com>; Thu, 1 Feb 2024 00:18:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 KH9ZJhSQlCou for <ntp@ietfa.amsl.com>; Thu, 1 Feb 2024 00:18:07 -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_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 76CFEC14F68D for <ntp@ietf.org>; Thu, 1 Feb 2024 00:18:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1706775485; 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=D4yqrDzl8OmdwxGxeHC2K/qB8gh99di0kaIZYIBDRw0=; b=d1JQZ/ZAgnEvyR1eRv2HuJHXN6asaHxEnmG5V++ForndEPQgUDn06w+B4GXUsfVKZqabPG zWTeE3CqXnMFiB5YbGkpID1L+Q/aemVFOh01iGiskNC/ZOWNv4O9swwcwFWXL+6vIXpW8c 5jwKR6hMVHm3hrSLSovGe3NVLCO3QBo=
Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-198-Okag5p3QNkmqvtpUhHkW9w-1; Thu, 01 Feb 2024 03:18:04 -0500
X-MC-Unique: Okag5p3QNkmqvtpUhHkW9w-1
Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (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 mimecast-mx02.redhat.com (Postfix) with ESMTPS id 254EF1066140; Thu, 1 Feb 2024 08:18:04 +0000 (UTC)
Received: from localhost (unknown [10.43.135.229]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A5C8C2028CD2; Thu, 1 Feb 2024 08:18:03 +0000 (UTC)
Date: Thu, 01 Feb 2024 09:18:02 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Hal Murray <halmurray@sonic.net>
Cc: ntp@ietf.org
Message-ID: <ZbtTupIwkmQVRF4G@localhost>
References: <20240131210135.62B2528C065@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
MIME-Version: 1.0
In-Reply-To: <20240131210135.62B2528C065@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
X-Scanned-By: MIMEDefang 3.4.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/ReJZmdWm5VtUb3pAr4b3jhC7tKU>
Subject: Re: [Ntp] NTS-KE server load pulse
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, 01 Feb 2024 08:18:08 -0000

On Wed, Jan 31, 2024 at 01:01:35PM -0800, Hal Murray wrote:
> Are we going to run into troubles with the NTS-KE server getting overloaded 
> when the server comes back up and all the clients jump on it trying to get new 
> cookies?

The server will be overloaded, but I think it should recover
eventually as long as it can provide NTS-KE for some number of
its clients. The problem would be if the server stopped working
completely under load, e.g. if it accepted so many connections that
none of them can finish before timeout, or if new connections were
causing old connections to be dropped.

This shouldn't be too different from the case when the server doesn't
save its keys across restarts.

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email