[Ntp] How many clients does a busy PTP server support?

Hal Murray <halmurray+ietf@sonic.net> Tue, 01 June 2021 22:54 UTC

Return-Path: <halmurray+ietf@sonic.net>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 504CF3A2A8F for <ntp@ietfa.amsl.com>; Tue, 1 Jun 2021 15:54:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.035
X-Spam-Level: *
X-Spam-Status: No, score=1.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_DYNAMIC_IPADDR=1.951, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id jojqT61uJH8h for <ntp@ietfa.amsl.com>; Tue, 1 Jun 2021 15:54:11 -0700 (PDT)
Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net []) by ietfa.amsl.com (Postfix) with ESMTP id 3108F3A2A98 for <ntp@ietf.org>; Tue, 1 Jun 2021 15:54:11 -0700 (PDT)
Received: from shuksan (localhost []) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id EE16E40605C; Tue, 1 Jun 2021 15:54:09 -0700 (PDT)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: ntp@ietf.org
cc: Hal Murray <halmurray+ietf@sonic.net>
From: Hal Murray <halmurray+ietf@sonic.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Tue, 01 Jun 2021 15:54:09 -0700
Message-Id: <20210601225409.EE16E40605C@ip-64-139-1-69.sjc.megapath.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/H4xK5peanuNX399mLaCyH1-Fyys>
Subject: [Ntp] How many clients does a busy PTP server support?
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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: Tue, 01 Jun 2021 22:54:17 -0000

Most of NTS4NTP is dancing around the lack of per-client state on the server.

If PTP servers only support a "small" number of clients and PTP already has a 
mechanism using shared keys, it might be simpler to just use TLS/whatever to 
setup keys.

If it takes 100 bytes for a server to store a key, that's 10K clients per 
megabyte.  Raspberry Pi-s come with gigabytes so the numbers seem worth 
further investigation.

Does the PTP shared key stuff cover all the problems?  (or enough of them to 
be interesting)

These are my opinions.  I hate spam.