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

Danny Mayer <mayer@pdmconsulting.net> Sun, 14 August 2022 17: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 588EDC14F732 for <ntp@ietfa.amsl.com>; Sun, 14 Aug 2022 10:55:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level:
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01] autolearn=no 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 PvU_WHNlcnzd for <ntp@ietfa.amsl.com>; Sun, 14 Aug 2022 10:55:18 -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 6D330C14F733 for <ntp@ietf.org>; Sun, 14 Aug 2022 10:55:14 -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 4M5Q6l04v7zMNZR; Sun, 14 Aug 2022 17:55:10 +0000 (UTC)
Message-ID: <a500eea8-e6a1-c10f-2385-3a05fb0e9638@pdmconsulting.net>
Date: Sun, 14 Aug 2022 13:55:09 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.12.0
Content-Language: en-US
To: Miroslav Lichvar <mlichvar@redhat.com>, Harlan Stenn <stenn@nwtime.org>
Cc: ntp@ietf.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> <YvDWC27qKnODlD52@localhost> <0b57b7db-772e-f5e6-e6a0-a433673f3d77@nwtime.org> <YvED7T5R0UsRWbv3@localhost> <b64c6a0a-ea2e-0a19-4bb9-38bfaa2e5032@nwtime.org> <YvIUIu1LaloEjJMb@localhost>
From: Danny Mayer <mayer@pdmconsulting.net>
In-Reply-To: <YvIUIu1LaloEjJMb@localhost>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/Swbjdh9RX-qE7EQc-Qi-Wkuu0FE>
Subject: Re: [Ntp] 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: Sun, 14 Aug 2022 17:55:21 -0000

On 8/9/22 4:00 AM, Miroslav Lichvar wrote:
> On Mon, Aug 08, 2022 at 06:46:13PM -0700, Harlan Stenn wrote:
> I'm curious about the collision with an NTS extension field. I suspect 
> that
>> was simply a result of poor programming on the implementor's side, but I
>> could be wrong.
> The value was chosen by the first NTS implementation. As the Autokey
> values used by ntpd were not documented anywhere, we didn't realize
> there was a conflict until it was too late.

Are you saying that noone looked at RFC 5906 Section 13 IANA Consideration?

It took me 3 months working with Dave Mills to get that done. It should 
have been in the IANA registry.

Danny