IETF Logo Mail Archive

Re: [Ntp] [EXT] Re: Experimental/Private EF area: was Re: Registries document

Miroslav Lichvar <mlichvar@redhat.com> Tue, 01 August 2023 07:09 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 7E009C151717 for <ntp@ietfa.amsl.com>; Tue, 1 Aug 2023 00:09:10 -0700 (PDT)
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_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=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 yf0q1Hona3Lp for <ntp@ietfa.amsl.com>; Tue, 1 Aug 2023 00:09:06 -0700 (PDT)
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 0FCA3C14CE42 for <ntp@ietf.org>; Tue, 1 Aug 2023 00:09:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1690873745; 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=+d4OIg+Y494Mpr6yen74WxqRKgWG9Aq2jLeNmLzbLyc=; b=NWVIeFhwqSS05FNpjQgy+kG9fWhLENoI7ucPt5Rotc5CaLm63d0Fk4J1yPwL67bWIecgQm 15Ya0xI9LAJU8yw1CHgo+HZIr3NrZ5C6D8q0apDFksQi4vGEBeWRABs9VVezdJmv1qBSA4 I6lR7n0SwRT/0v7rJ7rt4FcZHfnKAXI=
Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-49-lPsGtV1yMmC76cIYcOlfJw-1; Tue, 01 Aug 2023 03:09:03 -0400
X-MC-Unique: lPsGtV1yMmC76cIYcOlfJw-1
Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 4F9D681DA5D; Tue, 1 Aug 2023 07:09:03 +0000 (UTC)
Received: from localhost (unknown [10.43.135.229]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 75C36F784E; Tue, 1 Aug 2023 07:09:02 +0000 (UTC)
Date: Tue, 01 Aug 2023 09:09:01 +0200
From: Miroslav Lichvar <mlichvar@redhat.com>
To: "Windl, Ulrich" <u.windl@ukr.de>
Cc: "Salz, Rich" <rsalz@akamai.com>, Harlan Stenn <stenn@ntp.org>, Harlan Stenn <stenn@nwtime.org>, "ntp@ietf.org" <ntp@ietf.org>
Message-ID: <ZMivjTvEm5vDmKTn@localhost>
References: <664a52a9-08a9-d755-7f2c-5e7b9e3c9667@nwtime.org> <72448798-1D9F-4391-B3A6-131CE9783132@akamai.com> <d53b7d81-08bb-9159-33e7-9d0e21cca7d8@ntp.org> <EA171472-63A2-468E-AE6B-D655403058D0@akamai.com> <055e2897-143a-e19c-9c1b-b1953c4ea2c9@ntp.org> <795cbd64-5637-131f-b287-8649a3db145c@ntp.org> <ZMeh8WnbrAKDPx0Z@localhost> <C1B8DD5F-01F5-4776-AF70-A3C3A62E7E9B@akamai.com> <ZMfH8Brt3mOHhZ3R@localhost> <fa017fc1105a4405aafa2848b414adb9@ukr.de>
MIME-Version: 1.0
In-Reply-To: <fa017fc1105a4405aafa2848b414adb9@ukr.de>
X-Scanned-By: MIMEDefang 3.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/GfH4L98dNBJiDjagNGWr0F4ZdOg>
Subject: Re: [Ntp] [EXT] Re: Experimental/Private EF area: was Re: Registries document
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, 01 Aug 2023 07:09:10 -0000

On Tue, Aug 01, 2023 at 06:41:36AM +0000, Windl, Ulrich wrote:
> Actually I think the big mistake made in the past was to add the whole word into the IANA registry when the word is interpreted to consist of four or five fields.

Yes, that's what the authors of RFC5906 should have done, but they
have not and it's too late to fix that.

> IMHO the correct option would have been to register the "Code"s and maybe the "Field Type"s (as per RFC 5906, Figure 7: NTPv4 Extension Field Format).

I think it would be just the version value (01 - Autokey v1, 02 -
Autokey v2). The code subfield is specific to the protocol, which
other protocols don't need to know.

-- 
Miroslav Lichvar

v2.30.2 | Report a Bug | By Email | System Status