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

Harlan Stenn <stenn@nwtime.org> Tue, 09 August 2022 09:11 UTC

Return-Path: <stenn@nwtime.org>
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 932BDC15AB6B for <ntp@ietfa.amsl.com>; Tue, 9 Aug 2022 02:11:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=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 3Z_36ccRQeBI for <ntp@ietfa.amsl.com>; Tue, 9 Aug 2022 02:11:13 -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 E295BC1594A9 for <ntp@ietf.org>; Tue, 9 Aug 2022 02:11:13 -0700 (PDT)
Received: from [10.208.75.149] (071-084-168-128.res.spectrum.com [71.84.168.128]) (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 4M26kT3Sj3zMP3d; Tue, 9 Aug 2022 09:11:13 +0000 (UTC)
Message-ID: <c109d057-bcce-862a-e264-69523f232fed@nwtime.org>
Date: Tue, 09 Aug 2022 02:11:11 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0
Content-Language: en-US
To: ntp@ietf.org
References: <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> <62F0E9D3020000A10004C2EC@gwsmtp.uni-regensburg.de> <2d66fa3e-f750-e3d2-511e-594fa40d993d@nwtime.org> <62F0F4C7020000A10004C310@gwsmtp.uni-regensburg.de> <8faf7c64-8896-97ca-fa2e-2d762c7da1d8@nwtime.org> <YvEIf3g+Jjm27pUz@localhost> <f6b2b8ce-c4f8-72d9-8004-2bb13e1176e4@nwtime.org> <YvIUeUAkpXR7/lDS@localhost>
From: Harlan Stenn <stenn@nwtime.org>
In-Reply-To: <YvIUeUAkpXR7/lDS@localhost>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/XiegiXz-FT5z-nZC4PoEXBLOyDM>
Subject: Re: [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: Tue, 09 Aug 2022 09:11:19 -0000

On 8/9/2022 1:02 AM, Miroslav Lichvar wrote:
> On Mon, Aug 08, 2022 at 06:48:28PM -0700, Harlan Stenn wrote:
>> On 8/8/2022 5:58 AM, Miroslav Lichvar wrote:
>>> If you allow short extension fields, you will not be able to detect
>>> whether a request contains an unknown extension field or an Autokey
>>> MAC using an old cookie. The protocol may be able recover, but that's
>>> not how things should be done.
>>>
>>> Here is an example:
>>>
>>> 04 1b 00 14 cc e2 c8 47 71 95 79 64 c4 71 e8 72 7e bf fb cd
>>>
>>> Which of the two is it?
>>>
>>
>> More context, please.
>>
>> What is that set of bytes?
> 
> It's the UDP data following the NTP header.

I don't do this stuff in my head as well as I used to.

Is there a symmetric key for keyID 1051?  If so, what hash algorithm was 
used?

I'm not seeing that it's a valid EF (either V1 or V2).

But again, I don't do these things in my head as well as I used to.

-- 
Harlan Stenn <stenn@nwtime.org>
http://networktimefoundation.org - be a member!