Re: [Ntp] What is SNTP?

Danny Mayer <mayer@pdmconsulting.net> Wed, 07 September 2022 15:55 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 B6914C159825 for <ntp@ietfa.amsl.com>; Wed, 7 Sep 2022 08:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.105
X-Spam-Level:
X-Spam-Status: No, score=-6.105 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, RDNS_NONE=0.793, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 ztnMZMWUOywY for <ntp@ietfa.amsl.com>; Wed, 7 Sep 2022 08:55:30 -0700 (PDT)
Received: from chessie.everett.org (unknown [IPv6:2001:470:1:205::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 C838EC15A72B for <ntp@ietf.org>; Wed, 7 Sep 2022 08:55:17 -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) server-digest SHA256) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id 4MN6KF3wqnzMQ2X; Wed, 7 Sep 2022 15:55:13 +0000 (UTC)
Message-ID: <62e0ab2d-be13-bebe-396c-f1593a0b3245@pdmconsulting.net>
Date: Wed, 07 Sep 2022 11:55:12 -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.0
Content-Language: en-US
To: Hal Murray <halmurray@sonic.net>, ntp@ietf.org
References: <20220907004522.A02BF28C1D8@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
From: Danny Mayer <mayer@pdmconsulting.net>
In-Reply-To: <20220907004522.A02BF28C1D8@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/Srf18_xsCu7X0DWrO-VjXzmSAsU>
Subject: Re: [Ntp] What is SNTP?
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, 07 Sep 2022 15:55:34 -0000

On 9/6/22 8:45 PM, Hal Murray wrote:
> I said:
>>> The S is for Simple.  I hope SNTP will work without extension fields.
> Kristof Teichel said:
>> Wouldn't that preclude use of NTS?
> Good point.
>
> There are 2 possible meanings for "simple" in SNTP.  One is that you don't have to implement most of what is described in RFC 5905.  The other is that the code really is simple when you look at it.  Does anybody have suggested terms?  Basic?  Minimal?
There is only one meaning for SNTP and that is what is described in 
RFC5905. No more and no less. If the section is not clear then it's time 
to write a clarification for it.
>
> My "without extension field" comment was for basic/minimal SNTP.  You should be able to get the time without using any extensions.
>
> An SNTP client without NTS is only a few hundred lines of code.  NTS will multiply that by (guess) a factor of 4.  It's no longer simple.  You have to get a TLS library and root certificates and keep them up to date.  You need to store cookies.  ...
>
> Yes, we should provide sample code for SNTP+NTS.   Feel free to remind me in a couple of months if I don't announce something.  (That will remove the "guess" above.)
I very much doubt that today you can get the IETF to accept a draft 
unless there is some sort authentication mechanism.
>
> What I really want to do is avoid crap like this story:
>    https://kb.meinbergglobal.com/kb/time_sync/timekeeping_on_windows/configuring_w32time_as_ntp_client
> Thanks Martin, for writing that up.
>
>
> The current status is that code gets shipped and we are expected to support it forever.  We don't even have specs.
>
> I think we need to do better than "go read RFC 5905".
>
> I think we need:
>    A list of the version 1 formats that are in use.
What do you mean by version 1 formats? NTPv4 would be a minimum format.
>       We can get requests at pool servers.
>       We also need to know what responses need to look like.
>    Good documentation for client side SNTP.
>       Maybe something like a BCP.
>       Maybe just a web page.
>    Sample code for SNTP and SNTP+NTS.
>    Setup servers that don't support v1 for testing.
>
V1 of what?

Danny