Re: [Ntp] NTS4UPTP Rev 03 - Formal request for WG adoption

Miroslav Lichvar <> Wed, 02 June 2021 07:38 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id A55253A392D for <>; Wed, 2 Jun 2021 00:38:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.796
X-Spam-Status: No, score=-2.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.698, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PqxoGFShooZh for <>; Wed, 2 Jun 2021 00:38:53 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 370F23A392E for <>; Wed, 2 Jun 2021 00:38:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=mimecast20190719; t=1622619532; 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=iqvVj0213IsbjoIKfi3orv5hUgWLk9g9P6vg805E74o=; b=FXuvNdpVA0f1teN5hivMz4Q9q1NniGyVKXOJ2wpe2C85xDyu3idZUXUBTsukyveBucht3v YRSOpVyAKttY47O0EbMF3sI6kgACa2Iz0AzlmVirqoRgBoBzuTX+1vLtxWhgUcrjbxYAAs PPOMA5rwYqGzFyC4RYghngk8xWdKerU=
Received: from ( []) (Using TLS) by with ESMTP id us-mta-267-A966Fh7RNICmrC90tMeHcQ-1; Wed, 02 Jun 2021 03:38:47 -0400
X-MC-Unique: A966Fh7RNICmrC90tMeHcQ-1
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D1995106BB37; Wed, 2 Jun 2021 07:38:44 +0000 (UTC)
Received: from localhost ( []) by (Postfix) with ESMTPS id B59BE5D769; Wed, 2 Jun 2021 07:38:42 +0000 (UTC)
Date: Wed, 2 Jun 2021 09:38:41 +0200
From: Miroslav Lichvar <>
To: Danny Mayer <>
Cc: Daniel Franke <>, Heiko Gerstung <>, NTP WG <>
Message-ID: <YLc1gS3vdTlP2mOv@localhost>
References: <YLYheZYTSflAdlrF@localhost> <> <YLY3f2/5k1Hjebf7@localhost> <> <YLZVS4jwGOnMIk6g@localhost> <> <> <> <> <>
MIME-Version: 1.0
In-Reply-To: <>
X-Scanned-By: MIMEDefang 2.79 on
Authentication-Results:; auth=pass smtp.auth=CUSA124A263
X-Mimecast-Spam-Score: 0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Archived-At: <>
Subject: Re: [Ntp] NTS4UPTP Rev 03 - Formal request for WG adoption
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 02 Jun 2021 07:38:57 -0000

On Tue, Jun 01, 2021 at 02:48:59PM -0400, Danny Mayer wrote:
> That ignores the fact that you are bombarding the servers with requests at a
> very high rate. There's a very good reason why we implemented KOD packets.
> You wouldn't want to put any of those responses through a filter.

We are not talking about public servers here. These are protected
networks designed for highly accurate synchronization, where each link
has hardware timestamping on its ends and the jitter is on the order
of nanoseconds. With a 1000x smaller jitter you need a 1000x shorter
polling interval to fully take advantage of it, assuming everything
else is the same.

The server doesn't care if it has 100 million clients polling once per
1000 seconds, or 1000 clients polling 100 times per second. The load
is the same.

Of course, there is always a possibility that someone misconfigures
the client and floods a public server. There are safety mechanisms
that can be implemented to make that less likely. For example, chrony
doesn't switch to a sub-second polling interval unless the measured
peer delay is smaller than 10 milliseconds.

Miroslav Lichvar