Re: [TLS] heads-up: ALPN ID allocation for NTP security with "Recommended" as "Y"

Martin Thomson <mt@lowentropy.net> Wed, 11 March 2020 00:09 UTC

Return-Path: <mt@lowentropy.net>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 313E73A0B2B for <tls@ietfa.amsl.com>; Tue, 10 Mar 2020 17:09:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=anCmp2oZ; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=f4QQ2YRf
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i76rphTq3d-q for <tls@ietfa.amsl.com>; Tue, 10 Mar 2020 17:09:15 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA70B3A0B2A for <tls@ietf.org>; Tue, 10 Mar 2020 17:09:15 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 77FE821F18 for <tls@ietf.org>; Tue, 10 Mar 2020 20:09:14 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Tue, 10 Mar 2020 20:09:14 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=OGavssTv7PYVftbikAX4W26ximp14pB MeHezCVr/yNw=; b=anCmp2oZ9YK7gnzS1fAQzl7rGbzbbqnpmnedW6KGiXeVVzH VsUg1g9goUSfWjpRp1v9rBXTXPwwLk2U93OLKslg62Kg486+hF24s4U2OxSDXTj6 qqUzPkBopJNY51A3/U/QAZGIFhABTz54vhEdPVM+uYMsnJ/NJQWW8Tsr2m50gaPC i6qsEuwQm8k3HOuKpftpo9/Mmd/yOXGCVLp91yTZtsiRyzgPww9OVMTq6eY+99cD yoQUKPfOOZ4OawH51b5GdvV72npehPmYdyBJvarmTIFjYFrH447z/jFvPn2zkkcG XFbBwiTiFjXDRqotXxUIAdzNVfJT/fbG4tAi9gg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=OGavss Tv7PYVftbikAX4W26ximp14pBMeHezCVr/yNw=; b=f4QQ2YRffh3vav7Yw4VKGs 4zu76sXtxjhV0MGpWZ9szabMZreLYOocbF08rd9kwF4LWDUAyZJRPpF5am/DOX7M RRNU/OpzGE6KB9iKTrfpvNsvJy46T9tn6/mD65v/CNu7xAudhIxhIlHu+gD1cLoV lQ0vE7eajcL3ZhOTdn5Q1IcvzyNX0N0O/Qrj5KACyf1QFGooRXBo1rxCmaOFmI8g RUbU75uMSdxm12BLoFHx1VuY4qKUDHWxJwwSDzKx9adAu4JZy0FWdcRdqpEhsyss xWH888oCcV5sFHO8tZzTHm0NxDzmujn8cTV/slgKwVG6kg8A34RkqbzDIOedsGpg ==
X-ME-Sender: <xms:KixoXmx25bK5dNTovyQTdTZ4yuM2KPWBUvni37sZWgnKYtsQp3n5eA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedruddvuddgudekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderreejnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmh epmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvght
X-ME-Proxy: <xmx:KixoXuHe2eTA5v5tbCipKWyIwgbDIJz1Qp0EptvM2BaPuanEHaBlgg> <xmx:KixoXjtFv4wcqnM-CNaa_F81STAqg4yk7A01sk-1tsXGU_CHRvIfKA> <xmx:KixoXmC5tfRv8--gffQO5nJNkjlGL7G8l9ARDh_sGXrmDAuq123_sQ> <xmx:KixoXktU2C57hYRyiAddz7hhc4LnwffwvfSjm5S81hubjSajR5OjGQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 3E06EE00B8; Tue, 10 Mar 2020 20:09:14 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-991-g5a577d3-fmstable-20200305v3
Mime-Version: 1.0
Message-Id: <21fbb472-6aa8-4bdc-bf34-70fa95c5681c@www.fastmail.com>
In-Reply-To: <20200310234524.GH3439@akamai.com>
References: <20200310234524.GH3439@akamai.com>
Date: Wed, 11 Mar 2020 11:08:53 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: tls@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/9pwJw7ZV3htP3arKnnw0Ttjorfo>
Subject: Re: [TLS] =?utf-8?q?heads-up=3A_ALPN_ID_allocation_for_NTP_security_?= =?utf-8?q?with_=22Recommended=22_as_=22Y=22?=
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Mar 2020 00:09:17 -0000

On Wed, Mar 11, 2020, at 10:45, Benjamin Kaduk wrote:
> For purposes of increased visibility, I note that
> draft-ietf-ntp-using-nts-for-ntp is making an ALPIN ID registration and
> requesting to be marked as "Recommended" in the registry.  The
> high-level summary of the NTS-KE protocol is to do a TLS handshake and
> run a single request/response negotiation over it, using an exporter to
> produce keys to be used to secure NTP traffic (over separate UDP
> connections).

That sounds like a worthwhile use of a codepoint.

(Is TLS the de-facto owner of ALPN? There are some issues being discussed elsewhere that might affect future registrations.)