IETF Logo Mail Archive

[Ntp] NTS-KE server load pulse

Hal Murray <halmurray@sonic.net> Wed, 31 January 2024 21:01 UTC

Return-Path: <halmurray@sonic.net>
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 DA467C14F602 for <ntp@ietfa.amsl.com>; Wed, 31 Jan 2024 13:01:40 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sonic.net
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 pOqBML2iORJm for <ntp@ietfa.amsl.com>; Wed, 31 Jan 2024 13:01:37 -0800 (PST)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19B69C14E515 for <ntp@ietf.org>; Wed, 31 Jan 2024 13:01:36 -0800 (PST)
Received: from 107-137-68-211.lightspeed.sntcca.sbcglobal.net (104-182-38-69.lightspeed.sntcca.sbcglobal.net [104.182.38.69]) (authenticated bits=0) by d.mail.sonic.net (8.16.1/8.16.1) with ESMTPSA id 40VL1Ztu016810 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 31 Jan 2024 13:01:35 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sonic.net; s=net23; t=1706734896; bh=icnA9Si+QNaPRBKAktUppkxfTu6zkGnh2/4FehbZaCY=; h=To:From:Subject:Mime-Version:Date:Message-Id:From:Subject; b=scTXC0LY2Qy9nYe7GPbfxCqryjcd1T36mLAQjSPUZY8VrvjIXv0lt5J9wh1AFV4gO NmLUzbVphdtdIZrraPWzF59paQYtJoL0OSCNXyGBuEY1AyLHfFoGY5FFqv9Fnup7gH Ec5jp7r9G7icQkI+fWAVhpiRebL3WAyaKM319YyisLO/utcqM/hO9EOYQJs97Yb14h 1hWbg+yb/DqYnI8QSo7kM70IUHH+7jyykGlHICpiP402Tw71t7jkr4AkQoQv7LV9GW gEc4CiXaZTEWRrcVAXeONKQyhZetVJoAwGatxylgBaQnP47KvJFn/pW8+/n0yXsqm6 QG8/cXUUrcVTg==
Received: from hgm (localhost [IPv6:::1]) by 107-137-68-211.lightspeed.sntcca.sbcglobal.net (Postfix) with ESMTP id 62B2528C065; Wed, 31 Jan 2024 13:01:35 -0800 (PST)
X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.8
To: ntp@ietf.org
cc: Hal Murray <halmurray@sonic.net>
From: Hal Murray <halmurray@sonic.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 31 Jan 2024 13:01:35 -0800
Message-Id: <20240131210135.62B2528C065@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
X-Sonic-CAuth: UmFuZG9tSVbsZBrgdxQ0g7Bdyzigz1eEXQxBmZGoY0YsjdG2BcsOG0bCQUYRut+2QV0rs1XBGHTeiKfWunWf7da0a3LnMAEFxmhC7BFxsjA=
X-Sonic-ID: C;GpA463vA7hGAVpsCP63e0g== M;YAhN63vA7hGAVpsCP63e0g==
X-Sonic-Spam-Details: -1.5/5.0 by cerberusd
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/mh5RIttvZw6DkF8pZnVGOA8zWBk>
Subject: [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: Wed, 31 Jan 2024 21:01:40 -0000

I'm assuming that a NTP server and its NTS-KE server are running on the same 
box and that the client doesn't reuse cookies.

Consider what happens if that box is down for X minutes.  If X is greater than 
8 times a client's polling interval, the client will run out of cookies and go 
through NTS-KE again.

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?


-- 
These are my opinions.  I hate spam.

v2.23.0 | Report a Bug | By Email