[TLS] Re: Codepoint registration for algorithms enough?

Ilari Liusvaara <ilariliusvaara@welho.com> Wed, 30 September 2026 06:24 UTC

Received: from smtp.dnamail.fi (sender103.dnamail.fi [83.102.40.157]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by mx.ietf.org (Postfix) with ESMTPS id 44B554B for <tls@ietf.org>; Wed, 30 Sep 2026 06:24:03 +0000 (UTC)
Authentication-Results: mx.ietf.org; dkim=pass header.d=welho.com header.s=2025-03 header.b=CRP9bxxf; dmarc=pass (policy=none) header.from=welho.com; spf=pass (mx.ietf.org: domain of ilariliusvaara@welho.com designates 83.102.40.157 as permitted sender) smtp.mailfrom=ilariliusvaara@welho.com
Received: from localhost (localhost [127.0.0.1]) by smtp.dnamail.fi (Postfix) with ESMTP id 05B44409A3AD for <tls@ietf.org>; Wed, 30 Sep 2026 09:23:56 +0300 (EEST)
X-Virus-Scanned: X-Virus-Scanned: amavis at smtp.dnamail.fi
Received: from smtp.dnamail.fi ([83.102.40.157]) by localhost (dmail-psmtp02.s.dnaip.fi [127.0.0.1]) (amavis, port 10024) with ESMTP id KxcrimehSSOy for <tls@ietf.org>; Wed, 30 Sep 2026 09:23:55 +0300 (EEST)
Received: from LK-Perkele-VII2 (87-92-117-27.bb.dnainternet.fi [87.92.117.27]) (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) (Authenticated sender: hliusvaa@dnamail.internal) by smtp.dnamail.fi (Postfix) with ESMTPSA id 7975740979C5 for <tls@ietf.org>; Wed, 30 Sep 2026 09:23:55 +0300 (EEST)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.dnamail.fi 7975740979C5
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=welho.com; s=2025-03; t=1790749435; bh=cYd0gDRnH6EzjE7NEvR2uR6eSwzvkuVZ8aBYclg6b+I=; h=Date:From:To:Subject:References:In-Reply-To:From; b=CRP9bxxfTkCUDQDj0qU5CGwZKXCI0PpKHalHWru++6CJVosoETGHPUQWiM7eY8qTn amQI+VnjSXSSyQTWfx3gxi0PDDxZSzwAtgCsgCK1R2CxP9VBWUXkAaz+xUbNlUFoB6 yqHbVWsa81kwB3ZN8fKu6wttDq5k2CA2uINYjEKjPS0m8w02gdBqDnrLfqZdUHro5S oihL3JFWAhyjUSKSYaDAbFSfjZKsT9RxnQS6AFIKvT+c+4GW+bZxUx6FISLWWyBvGX hxhYfcvCvAiidaA6BSDH3AUrwfQ+jiqjfiacSrbkMAieenGeA/2j5aLpoE9eYndtNF O8u4HlVO1N5iA==
Date: Wed, 30 Sep 2026 09:23:55 +0300
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: TLS List <tls@ietf.org>
Message-ID: <aryq-7BSXoo_s7pz@LK-Perkele-VII2.locald>
References: <CACsn0cmJkDmfXVbyimvNpr2NgpooazgZ8sNobfZ7dCQVaSwtdQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
In-Reply-To: <CACsn0cmJkDmfXVbyimvNpr2NgpooazgZ8sNobfZ7dCQVaSwtdQ@mail.gmail.com>
Sender: ilariliusvaara@welho.com
X-Spamd-Bar: /
Message-ID-Hash: RU76O3X6S72ZWJYWJALFOOHFPG6T4RST
X-Message-ID-Hash: RU76O3X6S72ZWJYWJALFOOHFPG6T4RST
X-MailFrom: ilariliusvaara@welho.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-tls.ietf.org-0; header-match-tls.ietf.org-1; header-match-tls.ietf.org-2; header-match-tls.ietf.org-3; header-match-tls.ietf.org-4; header-match-tls.ietf.org-5; header-match-tls.ietf.org-6; header-match-tls.ietf.org-7; header-match-tls.ietf.org-8; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.10
Precedence: list
Subject: [TLS] Re: Codepoint registration for algorithms enough?
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/HuiYdx0lRTimRPdEEKLnqY355b8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Owner: <mailto:tls-owner@ietf.org>
List-Post: <mailto:tls@ietf.org>
List-Subscribe: <mailto:tls-join@ietf.org>
List-Unsubscribe: <mailto:tls-leave@ietf.org>

On Tue, Sep 29, 2026 at 02:53:57PM -0700, Watson Ladd wrote:
> Dear TLS WG,
> 
> Is a codepoint registration all that we need for composite certs to
> work in TLS pointing to the doc in LAMPS? I'm trying to understand
> what content we would need to have here and why.

AFAICT, other than the registration stuff, mostly just interoperability
and security considerations. Prominent part of security considerations
is downgrade attacks (to both traditional and standalone).




-Ilari