Re: [Ntp] Symmetric mode

David Venhoek <david@venhoek.nl> Sun, 02 October 2022 12:57 UTC

Return-Path: <david@venhoek.nl>
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 E9DFFC1522BB for <ntp@ietfa.amsl.com>; Sun, 2 Oct 2022 05:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-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_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=venhoek-nl.20210112.gappssmtp.com
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 7eeD4mCSi3tD for <ntp@ietfa.amsl.com>; Sun, 2 Oct 2022 05:57:19 -0700 (PDT)
Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 21C51C14CE24 for <ntp@ietf.org>; Sun, 2 Oct 2022 05:57:18 -0700 (PDT)
Received: by mail-ed1-x533.google.com with SMTP id e18so11362758edj.3 for <ntp@ietf.org>; Sun, 02 Oct 2022 05:57:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=venhoek-nl.20210112.gappssmtp.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date; bh=Bx0KGZdkrgGzqIbEhvig5Ie7NUeBKsngNpqcWgqLndE=; b=4JIqQAsVeCTtYPWvIodvdGsCDBFtd4KPrg8d4hgRG0pvXiDzIkY6xbLga+m11y7wkj CGMubVdsH9fpO0GNMMX6IMILVZba2GXV02MqeXvIbUQy/lQUI5wS2CqzPMd9e3rUmapA SkN7PoMig+0zyyO5M97houim8lqvi1NNa5WPBtaKUL/OjB6QMuTPHJxax/jt4tcqsVAS mZDuoega1rZNKkZ+hqCa/GHq6KP2wtCkqrTOpXkWmKX8rDa7bKeahuWamR4waerrGKBv f9NNC9wR7EPXhxfp4HwplTWKXgYqk4Hj4cDkYQQo5ll79urs+TwMUCqXI2BVUPjdwniT 6fig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date; bh=Bx0KGZdkrgGzqIbEhvig5Ie7NUeBKsngNpqcWgqLndE=; b=nuQwQ3R7nZIAaSgXHz0F2gk8ZHDr67oj4XokygZu0ipOU/T07t/NMK47dwkIENXpU3 X3kJNKP8qKbRrpjGS88YPq9SDVUtCXeIMfFErzipISa+1RK6S7NEUGhq4SvyqDjlfTON DJP7gvGjF8sjytUHW5xtoXye/cZ3so8zwd7RMAYrabl7btmu6lyamcOy+Z1YQugxuQte mAuEPA0WbTiJbn+n6/z00bU62/3WzOo9u7+x0Ivq7oyNpCv1OB9leDNXmiAkN2/MrV7g zJhmOo7q0HCdcs2pVP0KeaM+34oozIYGe9CQ6bfvAHbOf6IpwR1hn/LeHJ2SWKWSbt+V W1vA==
X-Gm-Message-State: ACrzQf032mO/Rp/QbGVmQUKwPaeDcYXPeKI+no+qMbpxlwqqvKIRal+O y04IC4EgLhKFIjjKttrSgiyrTszifWSMrB0zuE7rG9eXDU2RvQ==
X-Google-Smtp-Source: AMsMyM6EOSvjTrpopwHwy/rvEYnPKHckcireNo4EcqT7RFrKaZ8NpP5VTdlcYZCc2brh7b69h9aWCYu/iyvdNWeNVVk=
X-Received: by 2002:a05:6402:ea8:b0:456:d188:b347 with SMTP id h40-20020a0564020ea800b00456d188b347mr14927340eda.15.1664715436441; Sun, 02 Oct 2022 05:57:16 -0700 (PDT)
MIME-Version: 1.0
References: <doug.arnold@meinberg-usa.com> <AM7PR02MB5765D115CABA9E9B5A148711CF569@AM7PR02MB5765.eurprd02.prod.outlook.com> <20220930202957.8608D28C1D8@107-137-68-211.lightspeed.sntcca.sbcglobal.net> <AM7PR02MB57650B0AE5AF60B7A758EBF7CF589@AM7PR02MB5765.eurprd02.prod.outlook.com>
In-Reply-To: <AM7PR02MB57650B0AE5AF60B7A758EBF7CF589@AM7PR02MB5765.eurprd02.prod.outlook.com>
From: David Venhoek <david@venhoek.nl>
Date: Sun, 02 Oct 2022 14:57:11 +0200
Message-ID: <CAPz_-SV1i+vkru+HfVU4ErcY6+O2p6tWUTWeO+fQ4nJa8Ha8pQ@mail.gmail.com>
To: "ntp@ietf.org" <ntp@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/Fs17xE7fqSC84yqAZElXAh--Iok>
Subject: Re: [Ntp] Symmetric mode
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: Sun, 02 Oct 2022 12:57:23 -0000

In the interest of trying to at least get to some kind of conclusion,
I have tried my best to write up the main conclusions from all the
discussions:

Symmetric connection mode:
 - uses only 2 packets per polling interval to exchange time between 2
servers, compared to 4 when both are configured to use client mode
with the other.
 - can be easier to configure as only 1 of the two servers needs their
configuration altered (although this brings some security questions)
 - there may/are some differences in how timing data produced by these
connections is processed in the NTPd implementation

Broadcast connection mode:
 - uses only 1 packet per client per polling interval instead of 2 in
client-server mode, and 1 general broadcast packet
 - can be easier to configure as clients can just pick up the
broadcast packet without needing to know about the server in advance
(although this brings some security questions)


Primarily a question to Danny and/or Harlan, but is this a decent
description of the main differences between these modes and
Client/Server mode?

Kind regards,
David Venhoek

On Sun, Oct 2, 2022 at 11:09 AM Doug Arnold
<doug.arnold=40meinberg-usa.com@dmarc.ietf.org> wrote:
>
> It seems to me that the over-the-wire protocol should only be about sending timestamps back and forth. What the timestamps are used for belongs in the algorithms and clock control subsystems.
>
>
>
> From: Hal Murray <halmurray@sonic.net>
> Date: Friday, September 30, 2022 at 10:30 PM
> To: Doug Arnold <doug.arnold@meinberg-usa.com>
> Cc: Hal Murray <halmurray@sonic.net>, ntp@ietf.org <ntp@ietf.org>
> Subject: Re: [Ntp] Symmetric mode
>
>
> doug.arnold@meinberg-usa.com said:
> > Please enlighten me. I've been reading the discussion on symmetric ntp, a
> > nd I don=92t understand the purpose. An ntp server can ask other servers for
> > time using client server ntp, and use that information to examine its own
> > time and that of the peer it is looking at.  Why is a different over-the-wire
> > version of the protocol needed?
>
> That's what we are trying to figure out.
>
> Miroslav's draft for NTPv5 dropped symmetric mode.  Some people think it is
> interesting but they haven't managed to convince some others of us that it is
> important.
>
>
>
> --
> These are my opinions.  I hate spam.
>
>
> _______________________________________________
> ntp mailing list
> ntp@ietf.org
> https://www.ietf.org/mailman/listinfo/ntp