[Ntp] Antw: [EXT] Re: Quick review of WGLC for status change for draft‑ietf‑ntp‑update‑registries

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Mon, 08 August 2022 10:48 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 AD4FDC157B47 for <ntp@ietfa.amsl.com>; Mon, 8 Aug 2022 03:48:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.906
X-Spam-Level:
X-Spam-Status: No, score=-6.906 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-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 jrEAaq8_h7ar for <ntp@ietfa.amsl.com>; Mon, 8 Aug 2022 03:48:00 -0700 (PDT)
Received: from mx3.uni-regensburg.de (mx3.uni-regensburg.de [IPv6:2001:638:a05:137:165:0:4:4e79]) (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 C2028C14CF05 for <ntp@ietf.org>; Mon, 8 Aug 2022 03:47:58 -0700 (PDT)
Received: from mx3.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 7B7AC6000062 for <ntp@ietf.org>; Mon, 8 Aug 2022 12:47:51 +0200 (CEST)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx3.uni-regensburg.de (Postfix) with ESMTP id CD1FC6000047 for <ntp@ietf.org>; Mon, 8 Aug 2022 12:47:49 +0200 (CEST)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Mon, 08 Aug 2022 12:47:50 +0200
Message-Id: <62F0E9D3020000A10004C2EC@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.4.0
Date: Mon, 08 Aug 2022 12:47:47 +0200
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: "ntp@ietf.org" <ntp@ietf.org>, odonoghue@isoc.org, stenn@nwtime.org
References: <PH0PR06MB7061FA7A5B338D262B3A2963C2999@PH0PR06MB7061.namprd06.prod.outlook.com> <6a187a2f-9883-2fb5-1f51-1593591ddebb@nwtime.org> <PH0PR06MB706126984E4442EF32F8242AC2999@PH0PR06MB7061.namprd06.prod.outlook.com> <da155c84-2c70-2e3b-59eb-03e380806cf2@nwtime.org> <PH0PR06MB70611F2331D8255F7E2B6604C2999@PH0PR06MB7061.namprd06.prod.outlook.com> <0b4c7efa-3977-b588-0974-33b6a9437e52@nwtime.org>
In-Reply-To: <0b4c7efa-3977-b588-0974-33b6a9437e52@nwtime.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/DfPHiNHbmTec3_6wnj4aBOL9c-E>
Subject: [Ntp] Antw: [EXT] Re: Quick review of WGLC for status change for draft‑ietf‑ntp‑update‑registries
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, 08 Aug 2022 10:48:03 -0000

>>> Harlan Stenn <stenn@nwtime.org> schrieb am 08.08.2022 um 11:00 in
Nachricht
<0b4c7efa-3977-b588-0974-33b6a9437e52@nwtime.org>:
> For whatever it's worth...
> 
> I am opposed to the advancement/adoption of this document.
> 
> The NTP Project is opposed to the advancement/adoption of this document.
> 
> If this document is advanced, the NTP Project and I can only hope and 
> strongly recommend that IANA (or whomever) will take significant/primary 
> input from the NTP Project on the selection of the experts that will 
> oversee the maintenance of the various registries described in this 
> document.
> 
> The problems I (and the NTP Project) have with this document include, 
> but are not limited to:
> 
> ‑ it uses far too many words to say far too little.  In other places it 
> uses far too few words to say even less, except where it says nothing 
> about various significant aspects of the registries.

Harlan,

wouldn't you agree that this is also the category "it uses far too many words
to say far too little"?
What are you talking about specifically?

> 
> ‑ Table 1 is incomplete.  It does not include the value used by RFC 
> 7821, and it frequently refers to values that are "reserved for historic 
> reasons" without further explanation.  This leads me to:
> 
> ‑ The document does not describe (ignores?) 22 years of conscious design 
> decisions around the two versions (revisions?) of extension field 
> syntax, which Dave Mills and I have previous spent 3+ years' time and 
> effort (10 document revisions) in documenting, in 
> draft‑stenn‑ntp‑extension‑fields.

There are different opinions on the design and documentation of the extension
fields, I'm afraid.
I frequently had to use the source code as the documentation left too many
details unanswered.
An many of the extension fields were (MHO) "stiched with a hot needle" (or
"quick and dirty" if you prefer that phrase), blocking further extensions.

> 
> ‑ Without documented recognition of the underlying design decisions of 
> NTP Extension Fields and the guidance/expectations/safeguards that 
> design codifies, there seems to be little hope that future extension 
> field work will be done in a way that will safely evolve in a way that 
> is easily implementable or can be relied upon to be compatible.  This 

I agree, but _where_ should such documentation be put? In the registry?
If it's so complex that it needs a long story to explain, it clearly indicates
that it is too complex IMHO.

> lack of documentation about the expected layout of NTP Extension Fields 
> simply opens the door to chaos, or at least sub‑par decisions.

Should the layout of the fields be added to the registry?

Sorry Harlan, you message dod not help much to reduce the confusion that
undoubtedly is there.

Regards,
Ulrich


> 
> H
> 
> On 7/29/2022 1:41 PM, Karen O'Donoghue wrote:
>> You are always free to send comments, but we cannot wait indefinitely 
>> for your contribution. At this stage, no one has raised any concerns 
>> with the document.
>> 
>> Karen
>> 
>> *From: *Harlan Stenn <stenn@nwtime.org>
>> *Date: *Friday, July 29, 2022 at 4:08 PM
>> *To: *Karen O'Donoghue <odonoghue@isoc.org>, ntp@ietf.org <ntp@ietf.org>
>> *Subject: *Re: [Ntp] Quick review of WGLC for status change for 
>> draft‑ietf‑ntp‑update‑registries
>> 
>> I can still send them, if it will be good for anything.
>> 
>> And the point remains that *nobody* else saw any of the problems with
>> the document.
>> 
>> H
>> 
>> On 7/29/2022 12:19 PM, Karen O'Donoghue wrote:
>>> Harlan,
>>> 
>>> There were no negative comments received. You had indicated that you 
>>> were going to provide comments, but these comments were never received.
>>> 
>>> Regards,
>>> 
>>> Karen
>>> 
>>> *From: *ntp <ntp‑bounces@ietf.org> on behalf of Harlan Stenn 
>>> <stenn@nwtime.org>
>>> *Date: *Friday, July 29, 2022 at 3:08 PM
>>> *To: *ntp@ietf.org <ntp@ietf.org>
>>> *Subject: *Re: [Ntp] Quick review of WGLC for status change for 
>>> draft‑ietf‑ntp‑update‑registries
>>> 
>>> Very sad and sorry to hear this.
>>> 
>>> Were no comments received that point out the problems with the document?
>>> 
>>> On 7/29/2022 11:30 AM, Karen O'Donoghue wrote:
>>>> NTP working group,
>>>> 
>>>> The Updating the NTP Registries draft has passed WGLC; however, during 
>>>> the shepherd writeup process, we identified that it should be Standards 
>>>> track instead of Informational. Rich has updated/uploaded a new version 
>>>> of the draft that addresses this and a few editorial issues raised by 
>>>> Dieter. Given the change in status, we would like to issue a very short 
>>>> review of the WGLC to see if there are any concerns regarding the change

>>>> in document type. Please respond if you have any questions or concerns 
>>>> by Friday 5 August.
>>>> 
>>>> https://datatracker.ietf.org/doc/draft‑ietf‑ntp‑update‑registries/ 
>> <https://datatracker.ietf.org/doc/draft‑ietf‑ntp‑update‑registries/>
>>> <https://datatracker.ietf.org/doc/draft‑ietf‑ntp‑update‑registries/ 
>> <https://datatracker.ietf.org/doc/draft‑ietf‑ntp‑update‑registries/>>
>>>> <https://datatracker.ietf.org/doc/draft‑ietf‑ntp‑update‑registries/ 
>>> <https://datatracker.ietf.org/doc/draft‑ietf‑ntp‑update‑registries/ 
>> <https://datatracker.ietf.org/doc/draft‑ietf‑ntp‑update‑registries/>>>
>>>> 
>>>> Thanks everyone!
>>>> 
>>>> Karen
>>>> 
>>>> 
>>>> _______________________________________________
>>>> ntp mailing list
>>>> ntp@ietf.org 
>>>> https://www.ietf.org/mailman/listinfo/ntp 
>> <https://www.ietf.org/mailman/listinfo/ntp>
>>> <https://www.ietf.org/mailman/listinfo/ntp 
>> <https://www.ietf.org/mailman/listinfo/ntp>>
>>> 
>>> ‑‑ 
>>> Harlan Stenn <stenn@nwtime.org>
>>> http://networktimefoundation.org 
>> <http://networktimefoundation.org><http://networktimefoundation.org 
>> <http://networktimefoundation.org>> ‑ be
>>> a member!
>>> 
>>> _______________________________________________
>>> ntp mailing list
>>> ntp@ietf.org 
>>> https://www.ietf.org/mailman/listinfo/ntp 
>> <https://www.ietf.org/mailman/listinfo/ntp>
>>> <https://www.ietf.org/mailman/listinfo/ntp 
>> <https://www.ietf.org/mailman/listinfo/ntp>>
>>> 
>> 
>> ‑‑ 
>> Harlan Stenn <stenn@nwtime.org>
>> http://networktimefoundation.org <http://networktimefoundation.org>‑ be 
>> a member!
>> 
> 
> ‑‑ 
> Harlan Stenn <stenn@nwtime.org>
> http://networktimefoundation.org ‑ be a member!
> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp