Re: [Ntp] Antw: Re: Antw: [EXT] NTPv5 Loop Detection without Stratum

Hal Murray <halmurray@sonic.net> Mon, 05 September 2022 21:52 UTC

Return-Path: <halmurray@sonic.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 A0DD0C14CF01 for <ntp@ietfa.amsl.com>; Mon, 5 Sep 2022 14:52:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 oxyN7ZgN_Hlr for <ntp@ietfa.amsl.com>; Mon, 5 Sep 2022 14:52:38 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF383C14CE3A for <ntp@ietf.org>; Mon, 5 Sep 2022 14:52:38 -0700 (PDT)
Received: from 107-137-68-211.lightspeed.sntcca.sbcglobal.net (107-137-68-211.lightspeed.sntcca.sbcglobal.net [107.137.68.211]) (authenticated bits=0) by d.mail.sonic.net (8.16.1/8.16.1) with ESMTPSA id 285Lqbkp023565 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Mon, 5 Sep 2022 14:52:37 -0700
Received: from hgm (localhost [IPv6:::1]) by 107-137-68-211.lightspeed.sntcca.sbcglobal.net (Postfix) with ESMTP id ED4D728C1D8; Mon, 5 Sep 2022 14:52:36 -0700 (PDT)
X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.7.1
To: Danny Mayer <mayer@pdmconsulting.net>
cc: Hal Murray <halmurray@sonic.net>, "ntp@ietf.org" <ntp@ietf.org>
From: Hal Murray <halmurray@sonic.net>
In-Reply-To: Message from Danny Mayer <mayer@pdmconsulting.net> of "Mon, 05 Sep 2022 15:56:55 -0400." <b52ceff2-28a4-ef4e-2d63-ce2a0f519adb@pdmconsulting.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 05 Sep 2022 14:52:36 -0700
Message-Id: <20220905215236.ED4D728C1D8@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
X-Sonic-CAuth: UmFuZG9tSVas+hdKUQ/+qOjk2xzfWJ4KaOZBE5PheH0DG3L1d9I+qTARTIOb9dibGqXbo0wqqHEYHIUuaj9ziKuzTp8oqBVpR5hAM4wwP0E=
X-Sonic-ID: C;iiA5DmUt7RGYNID9Pq3e0g== M;IopkDmUt7RGYNID9Pq3e0g==
X-Sonic-Spam-Details: -1.5/5.0 by cerberusd
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/1RVfVJVFrIfVst1c1a5QuRODZ50>
Subject: Re: [Ntp] Antw: Re: Antw: [EXT] NTPv5 Loop Detection without Stratum
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: Mon, 05 Sep 2022 21:52:39 -0000

mayer@pdmconsulting.net said:
> SNTP is defined in RFC5905 Section 14. You don't need anything more than
> that. 

There is also RFC 4330 and a lot of crappy code out there in firmware that 
will never get updated.

RFC 5905 is over 100 pages.  Section 14 is less than a page.  How many of 
those other pages would somebody have to read and understand in order to 
implement a SNTP client?

If you were a junior programmer assigned to implement a SNTP client, would you 
go throgh RFC 5905 or google around and find some code to copy and ship it 
when it worked?


I think we should have a separate document for SNTP clients.  So far, I 
haven't convinced (m)any other people.  There are two goals:

One is to have a clear and simple document so we can point people at it when 
their current code is sending ancient format packets.  Some of those ancient 
packets are not using a format described in any RFC and they worked just 
because of the undocumented details in the ntpd implementation.

Another is to make us think and document a packet format that we will support for a long time.

We should setup servers that don't support old format packets so SNTP implementors can test their code.



-- 
These are my opinions.  I hate spam.