IETF Logo Mail Archive

[Ntp] Antw: [EXT] Re: Symmetric mode

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Tue, 18 October 2022 08:53 UTC

Return-Path: <Ulrich.Windl@rz.uni-regensburg.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 B2D1CC14CF0D for <ntp@ietfa.amsl.com>; Tue, 18 Oct 2022 01:53:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham 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 gUd4p1oHbzDs for <ntp@ietfa.amsl.com>; Tue, 18 Oct 2022 01:53:04 -0700 (PDT)
Received: from mx1.uni-regensburg.de (mx1.uni-regensburg.de [194.94.157.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28570C14CE2E for <ntp@ietf.org>; Tue, 18 Oct 2022 01:53:02 -0700 (PDT)
Received: from mx1.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 278556000051 for <ntp@ietf.org>; Tue, 18 Oct 2022 10:52:57 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx1.uni-regensburg.de (Postfix) with ESMTP id 0DF07600004D for <ntp@ietf.org>; Tue, 18 Oct 2022 10:52:55 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Tue, 18 Oct 2022 10:52:56 +0200
Message-Id: <634E6965020000A10004EA7C@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.4.1
Date: Tue, 18 Oct 2022 10:52:53 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: doug.arnold=40meinberg-usa.com@dmarc.ietf.org, stenn@nwtime.org, mlichvar@redhat.com, halmurray@sonic.net
Cc: "ntp@ietf.org" <ntp@ietf.org>
References: <mlichvar@redhat.com> <YzWunE8uQwTh8suS@localhost> <20220930015229.B235628C1D8@107-137-68-211.lightspeed.sntcca.sbcglobal.net> <AM7PR02MB5765D115CABA9E9B5A148711CF569@AM7PR02MB5765.eurprd02.prod.outlook.com> <415b7a7f-b9f6-8128-a9ae-467a93401945@nwtime.org> <387E5469020000CF5AEBDC6A@gwsmtp.uni-regensburg.de> <CED1DAD40200002E6A6A8CFC@gwsmtp.uni-regensburg.de> <72A957130200000B5AEBDC6A@gwsmtp.uni-regensburg.de> <60E0A8800200001A6A6A8CFC@gwsmtp.uni-regensburg.de> <64395FC0020000E55AEBDC6A@gwsmtp.uni-regensburg.de> <E2CB9EB502000031FDA5B133@gwsmtp.uni-regensburg.de> <114E6FEE020000C76A6A8CFC@gwsmtp.uni-regensburg.de> <7E0316BF020000985AEBDC6A@gwsmtp.uni-regensburg.de> <F6AB60DC020000A0FDA5B133@gwsmtp.uni-regensburg.de> <140797510200002A5AEBDC6A@gwsmtp.uni-regensburg.de> <C6BB969C020000F1FDA5B133@gwsmtp.uni-regensburg.de> <2120B0EA020000F65AEBDC6A@gwsmtp.uni-regensburg.de> <9E8B18D80200008AFDA5B133@gwsmtp.uni-regensburg.de> <E36AD98A020000BB5AEBDC6A@gwsmtp.uni-regensburg.de> <66CB14C40200001CFDA5B133@gwsmtp.uni-regensburg.de> <A1B6465A020000166A6A8CFC@gwsmtp.uni-regensburg.de> <FF0B828002000028FDA5B133@gwsmtp.uni-regensburg.de> <5A91856802000004BE098E0D@gwsmtp.uni-regensburg.de> <7EA7E6DB020000F0822C0D04@gwsmtp.uni-regensburg.de>
In-Reply-To: <7EA7E6DB020000F0822C0D04@gwsmtp.uni-regensburg.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/ZgxNU9ePBwRD-FOLoRGMgKdi-58>
Subject: [Ntp] Antw: [EXT] Re: 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: Tue, 18 Oct 2022 08:53:07 -0000

>>> Harlan Stenn <stenn@nwtime.org> schrieb am 01.10.2022 um 01:18 in Nachricht
<415b7a7f-b9f6-8128-a9ae-467a93401945@nwtime.org>:
> Client-server modes (3 and 4) are for a client to ask for the time from 
> a server.
> 
> Peer modes (1/active and 2/passive) are for exchanging time between peers.
> 
> One might choose to have a set of machines that offer time to the a lot 
> of client machines.  The machines that comprise the set of "time 
> servers" would peer with each other.
> 
> The clients would use the "time server" machines as their time servers.
> 
> There is "mechanism", and there is "policy".  Mechanism should be robust 
> enough to support policy goals.
> 
> "peer" (active or passive) and "client/server" are mechanism choices.
> 
> Local policy choices include "do we want to use peer mode on any machines?"

That is how I understood it, BUT what are the actual benefits of using peering?

Regards,
Ulrich

[...]

v2.23.0 | Report a Bug | By Email