IETF Logo Mail Archive

Re: [Ntp] Antwort: Re: Symmetric mode

Danny Mayer <mayer@pdmconsulting.net> Sat, 01 October 2022 19:38 UTC

Return-Path: <mayer@pdmconsulting.net>
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 20D48C14CE30 for <ntp@ietfa.amsl.com>; Sat, 1 Oct 2022 12:38:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level:
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=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 niutcTmM9B3J for <ntp@ietfa.amsl.com>; Sat, 1 Oct 2022 12:38:00 -0700 (PDT)
Received: from chessie.everett.org (chessie.everett.org [66.220.13.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 73CD0C14CE2D for <ntp@ietf.org>; Sat, 1 Oct 2022 12:38:00 -0700 (PDT)
Received: from [192.168.1.156] (pool-108-26-202-2.bstnma.fios.verizon.net [108.26.202.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4Mfy7D0Qr4zMPCs; Sat, 1 Oct 2022 19:37:59 +0000 (UTC)
Message-ID: <1e4a32a7-2911-673f-d1fe-1cf4199fe514@pdmconsulting.net>
Date: Sat, 01 Oct 2022 15:37:59 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.13.1
Content-Language: en-US
To: Hal Murray <halmurray@sonic.net>
Cc: ntp@ietf.org
References: <20221001063649.A59EB28C1D8@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
From: Danny Mayer <mayer@pdmconsulting.net>
In-Reply-To: <20221001063649.A59EB28C1D8@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/orbsLsTMKYyUlmuAwHdTCZ5kUEE>
Subject: Re: [Ntp] Antwort: 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: Sat, 01 Oct 2022 19:38:02 -0000

On 10/1/22 2:36 AM, Hal Murray wrote:
>> The initiator of the request is acting as the client for the packet and the
>> other one acts as the server. When the other peer initiates a packet it is
>> the client.
>> No, since each side know whether it's acting as a client or as a server for
>> each packet.
> That doesn't match my understanding.
>
> Suppose both sides say peer or the ephemeral association gets setup.  Both
> ends show a normal/happy slot in ntpq peers so both ends are clients.   There
> are only half as many packets as a pair of client/server associations.

That is not correct. Symmetric mode uses EXACTLY the same number of 
packets as client/server. I'm not sure why you keep saying otherwise.

>    Each
> packet is both client and server.  Each packet is a new client/request but
> also contains the server/response data for the previous packet from other guy.
>
No, these are normal request/response packets. They do NOT contain the 
server response from the previous packet from the other guy.

Danny

v2.23.0 | Report a Bug | By Email