IETF Logo Mail Archive

Re: [Ntp] I-D Action: draft-ietf-ntp-update-registries-09.txt

Miroslav Lichvar <mlichvar@redhat.com> Mon, 11 December 2023 14:48 UTC

Return-Path: <mlichvar@redhat.com>
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 46F6DC14CF18 for <ntp@ietfa.amsl.com>; Mon, 11 Dec 2023 06:48:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com
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 M29E8NiqBDgv for <ntp@ietfa.amsl.com>; Mon, 11 Dec 2023 06:48:56 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (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 9677DC14EB17 for <ntp@ietf.org>; Mon, 11 Dec 2023 06:48:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1702306135; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=3bDF1+z+vCDryd+MLPQY+bkTSrwr3+XPISCLoWjVXqg=; b=FRi3DMPEO0a6easU8/LLaCP/WQh3EO7Td80Z+uvh2DdD206ynxS8LXJH0oocXRAyFCMsMx 1BSJRlbdrc8VYYrAX58P9EW/t3LR0vW+3qOT8vaLYngH2jKlmTn+WvYXas2qqLC+jbNKMU q7rc6kUrlYKjEsj6aLEhXxOyP/g3pMI=
Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-263-8NP2-pJbMxW1gDrobRszXw-1; Mon, 11 Dec 2023 09:48:51 -0500
X-MC-Unique: 8NP2-pJbMxW1gDrobRszXw-1
Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (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 mimecast-mx02.redhat.com (Postfix) with ESMTPS id 0DDDB8370EE; Mon, 11 Dec 2023 14:39:34 +0000 (UTC)
Received: from localhost (unknown [10.43.135.229]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 54C2D8065; Mon, 11 Dec 2023 14:39:33 +0000 (UTC)
Date: Mon, 11 Dec 2023 15:39:32 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Hal Murray <halmurray@sonic.net>
Cc: "Windl, Ulrich" <u.windl@ukr.de>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "ntp@ietf.org" <ntp@ietf.org>
Message-ID: <ZXcfJDIJ7_33LqJ9@localhost>
References: <u.windl@ukr.de> <f519a82b72f943188cd02935c983d576@ukr.de> <20231207082443.8C0B728C1C3@107-137-68-211.lightspeed.sntcca.sbcglobal.net> <ZXcV2OhqQKrKqm3k@localhost>
MIME-Version: 1.0
In-Reply-To: <ZXcV2OhqQKrKqm3k@localhost>
X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.5
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/WOuqwVGUSEc6qBQDIw2S9tSOq0k>
Subject: Re: [Ntp] I-D Action: draft-ietf-ntp-update-registries-09.txt
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, 11 Dec 2023 14:48:59 -0000

On Mon, Dec 11, 2023 at 02:59:52PM +0100, Miroslav Lichvar wrote:
> On Thu, Dec 07, 2023 at 12:24:43AM -0800, Hal Murray wrote:
> > > If the extension field requires a MAC, the extension field specification MUST
> > > define the algorithm to be used to create the MAC and the length of the MAC
> > > thus created. An extension field MAY allow for the use of more than one
> > > algorithm, in which case the information about which algorithm was used MUST
> > > be included in the extension field itself.
> > 
> > In modern practice, there is no need for the algorithm on the wire.  When you are setting up a shared key, in addition to the keyid and key itself, you have to agree on the algorithm.
> 
> That section is about potential extension fields requiring a MAC. IIRC
> there is no such thing yet.

On second thought, that's probably meant to cover Autokey, which needs
few exchanges with extension fields to start.

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email