IETF Logo Mail Archive

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

Miroslav Lichvar <mlichvar@redhat.com> Mon, 27 November 2023 14:10 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 81DE8C151087 for <ntp@ietfa.amsl.com>; Mon, 27 Nov 2023 06:10:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.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_HI=-5, RCVD_IN_MSPIKE_H3=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=ham 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 OVFdnHHaUm1A for <ntp@ietfa.amsl.com>; Mon, 27 Nov 2023 06:10:47 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.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 EC48FC151081 for <ntp@ietf.org>; Mon, 27 Nov 2023 06:10:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1701094245; 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=fZsiwO8p5s64h2K3ppoX26dfdn7DGLOpDtJMn+0cGYo=; b=Km5jc+YavRpsF3n8RqO/skerXox92W6Ga9V4Lmy1BLs9xjgH+3PSayzn5qJt90vC2QrGZZ Eri1TZXdrhCbP9aEB8Ns1ocTrBcOSL2MJX9RgrE60rw4IZQ6KR3W8mnz43gi/Tc9yOrvuG 5xKdrbcdiAPydcccgLR5BZkUwF+Ok2c=
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-308-pI7oElmfPSWbJzcTaE61zw-1; Mon, 27 Nov 2023 09:10:44 -0500
X-MC-Unique: pI7oElmfPSWbJzcTaE61zw-1
Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (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 EA1D81019C83; Mon, 27 Nov 2023 14:10:43 +0000 (UTC)
Received: from localhost (unknown [10.43.135.229]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 5815E492BE7; Mon, 27 Nov 2023 14:10:43 +0000 (UTC)
Date: Mon, 27 Nov 2023 15:10:42 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Hal Murray <halmurray@sonic.net>
Cc: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, "ntp@ietf.org" <ntp@ietf.org>
Message-ID: <ZWSjYi2It4s3d2Rm@localhost>
References: <rsalz=40akamai.com@dmarc.ietf.org> <ED05CB35-6EEC-4BE3-9A13-9B8978AA8587@akamai.com> <20231127025215.B19BF28C1C3@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
MIME-Version: 1.0
In-Reply-To: <20231127025215.B19BF28C1C3@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.9
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/08KmeOKtHCkWjHdufVyEJmz4qms>
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, 27 Nov 2023 14:10:47 -0000

On Sun, Nov 26, 2023 at 06:52:15PM -0800, Hal Murray wrote:
> Shared key MACs have a 4 byte key number and 16 or 20 bytes of MAC.  The key 
> number space was shared by autokey and manual assignments.  The manual mode 
> was restricted to the lower 65K.

There is at least one implementation that doesn't support autokey and
can assign symmetric keys in the full 32-bit range following RFC 5905.

> So sites that are not using autokey don't 
> need the at least 28 byte length restriction from RFC 7822 for the last 
> extension.

What extension fields would they use? IIRC everything specified for
NTPv4 has last extension at least 28 octets. I don't like the idea of
site-specific parsing of NTP packets. Think of tcpdump/wireshark.

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email