IETF Logo Mail Archive

[Ntp] Frequency transfer in NTP

Miroslav Lichvar <mlichvar@redhat.com> Thu, 28 January 2021 14:32 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 4B33B3A1546 for <ntp@ietfa.amsl.com>; Thu, 28 Jan 2021 06:32:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.369
X-Spam-Level:
X-Spam-Status: No, score=-2.369 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pvP7c0wTMzht for <ntp@ietfa.amsl.com>; Thu, 28 Jan 2021 06:31:59 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AFC53A1545 for <ntp@ietf.org>; Thu, 28 Jan 2021 06:31:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1611844318; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=mIfT667K2OlgOkP5cb7aBfLSVCWOVuRVaQplwpnr59Y=; b=Qm9E/MlYag+7AQM8Dy6FjibWbwg/6HrZL2KCdz2UeoWbEe9LqtxeY7YWsML/dWis6cgUCH KmUcn8uowRizbGT78mV6kUhMzeMD4OeX2Qi7sAd/mwq4Zqv5KRmHf6/44I5y8mEjdHx7L7 b+z9Gc18STCOOaMJE9wIZARupAT7jdg=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-435-Yjae49pKOJSUoZZtrqosWQ-1; Thu, 28 Jan 2021 09:31:55 -0500
X-MC-Unique: Yjae49pKOJSUoZZtrqosWQ-1
Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id EECC4EC1BB for <ntp@ietf.org>; Thu, 28 Jan 2021 14:31:41 +0000 (UTC)
Received: from localhost (holly.tpb.lab.eng.brq.redhat.com [10.43.134.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 75C7F5D9EF for <ntp@ietf.org>; Thu, 28 Jan 2021 14:31:39 +0000 (UTC)
Date: Thu, 28 Jan 2021 15:31:37 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: ntp@ietf.org
Message-ID: <20210128143137.GA1205378@localhost>
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14
Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@redhat.com
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/a2rsddP3VvjdDI84R9_ops0RZzc>
Subject: [Ntp] Frequency transfer in NTP
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: Thu, 28 Jan 2021 14:32:01 -0000

One of the new features that was proposed for NTPv5 is an additional
receive timestamp to enable a frequency transfer to stabilize
synchronization. I have tested this idea with two different
implementations:

https://fedorapeople.org/~mlichvar/ntp-freq-transfer/

I think this would be a significant improvement of the protocol.

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email