Re: [Ntp] Symmetric mode

Danny Mayer <mayer@pdmconsulting.net> Wed, 28 September 2022 23:34 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 D6D26C15AE22 for <ntp@ietfa.amsl.com>; Wed, 28 Sep 2022 16:34:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=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 Y6_AVGJnuY1f for <ntp@ietfa.amsl.com>; Wed, 28 Sep 2022 16:34:16 -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 85EB7C1522D0 for <ntp@ietf.org>; Wed, 28 Sep 2022 16:33:50 -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 4MdCVg5RSwzMPCK; Wed, 28 Sep 2022 23:33:47 +0000 (UTC)
Message-ID: <e15fb43b-9c28-7a13-b395-468e8c62b71a@pdmconsulting.net>
Date: Wed, 28 Sep 2022 19:33:46 -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" <ntp@ietf.org>
References: <20220925070937.7FE1028C1D8@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
From: Danny Mayer <mayer@pdmconsulting.net>
In-Reply-To: <20220925070937.7FE1028C1D8@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/4EB99U7Cwe7RDxE8OYy-Lsc2HfA>
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: Wed, 28 Sep 2022 23:34:21 -0000

On 9/25/22 3:09 AM, Hal Murray wrote:
>>> It uses twice as many packets.
>> No, it doesn't. Run it and check the packet traffic. Yes each side sends  a
>> packet to the other the same as if both were referencing the other as
>> servers
> We had a pronoun binding mixed up.
>
> A setup with a pair of client/server connections will use twice as much
> traffic as a single symmetric connection.

I realized over the weekend that people have misunderstood how symmetric 
mode works and think that there is just one packet exchange between 
peers. That is incorrect. That's not how it works.

Symmetric mode works almost identically to client/server modes on the 
wire. The only difference is that client/server use modes 3 and 4 while 
symmetric peer use mode 1 or 2 depending on whether these are active or 
passive modes. You should see no difference on the wire between 
client/server and symmetric modes except for the mode value.

>
>>> It works with NTS.
>> NTS dropped it in the interested of getting NTS out.
> Same issue.  NTS works today if you use client/server mode.
>
It would be trivial to add to symmetric mode, see above.

Danny