[Ntp] NTP speed of synchronization question

Toerless Eckert <tte@cs.fau.de> Wed, 14 August 2024 08:09 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 76F4DC14F726 for <ntp@ietfa.amsl.com>; Wed, 14 Aug 2024 01:09:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
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 NUwS6MmcC53N for <ntp@ietfa.amsl.com>; Wed, 14 Aug 2024 01:09:38 -0700 (PDT)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13145C14F5E8 for <ntp@ietf.org>; Wed, 14 Aug 2024 01:09:37 -0700 (PDT)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [131.188.34.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4WkLWf0Nqdznkp8 for <ntp@ietf.org>; Wed, 14 Aug 2024 10:09:34 +0200 (CEST)
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4WkLWd6Xmczkx1F; Wed, 14 Aug 2024 10:09:33 +0200 (CEST)
Date: Wed, 14 Aug 2024 10:09:33 +0200
From: Toerless Eckert <tte@cs.fau.de>
To: ntp@ietf.org
Message-ID: <ZrxmPeWAKqsIv86j@faui48e.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Message-ID-Hash: V53QU2TAUFJ6YT6WJ56H4AZ2TGH6ICH2
X-Message-ID-Hash: V53QU2TAUFJ6YT6WJ56H4AZ2TGH6ICH2
X-MailFrom: eckert@i4.informatik.uni-erlangen.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ntp.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Ntp] NTP speed of synchronization question
List-Id: Network Time Protocol <ntp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/gaDHI4dcCJ3PF3uZ6ggQo6HvH3k>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Owner: <mailto:ntp-owner@ietf.org>
List-Post: <mailto:ntp@ietf.org>
List-Subscribe: <mailto:ntp-join@ietf.org>
List-Unsubscribe: <mailto:ntp-leave@ietf.org>

Dear NTP WG

I have a few quick ops question against NTP which would take me a lot longer to investigate
on actual devices. This is for reviewing draft-ietf-bess-evpn-fast-df-recovery which wants
to utilize clock synchronization between routers.

Assuming typical high-end routers and their implementation of NTP:

1. Is there any reasonw why we should NOT be able to achieve synchronization of less than 5 msec ?

2. Assuming synchronization only across some WAN connection, how long would it typically
   take for a restarting router to synchronize against a peer to that level of accuracy or better ?

3. Would synchronization to a local peer be faster ? If so, how fast could it be ?

4. Am i correct to remember that the accuracy of synchronization should be accessible to
   user of NTP (such as the aforementioned drafts mechanism) through some diagnostics interface ?
   ( think to remmeber that to be the case from typical NTP implementation CLI).

Thanks so much!
    Toerless