[TLS] Re: Working Group Last Call for Use of ML-DSA in TLS 1.3

Robert Relyea <rrelyea@redhat.com> Wed, 15 April 2026 18:11 UTC

Return-Path: <rrelyea@redhat.com>
X-Original-To: tls@mail2.ietf.org
Delivered-To: tls@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id C6475DD0EDD6 for <tls@mail2.ietf.org>; Wed, 15 Apr 2026 11:11:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1776276696; bh=z17postoCMkFkYGwaIbhWHSK2m32e+Y80sxALw2tGhM=; h=Date:Subject:To:References:From:In-Reply-To; b=mtrjtQiLZe9rI8B3yGJeNCoS6h0zOrBFiQomrMtJGrv+iriSNt363xWssdnAOQfax ryopyVJ5Xq7Qk4V97u24EJ9ZGunQwsN1lawsGNWx0iYSwIeqNgvghhMMjuYCEOewrz xNXNhdVJGinD1sV17tjIRbs5LetVDtKRwS6tgadA=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id onF8RV3uVrzK for <tls@mail2.ietf.org>; Wed, 15 Apr 2026 11:11:36 -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 ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id A7C7DDD0EC76 for <tls@ietf.org>; Wed, 15 Apr 2026 11:11:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1776276683; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=KaPiXaEVmQCXxm6/5lQyR4VbE2pHtdIzftPw2bk3Ffg=; b=FjM8rIjL1MTD/l+HfbbaiJeySkFHJndqLV4qq6uqJ4meAI3vhp3317WWNbnlQrSW6SY6tr Dpl7WpS0c/OW8eR2No/HDjYaWqHo0guiAgmjry/lmvjY/VZ4kdb1ud1IBny6VJe2knhPBN VKU0G+0d1wcJaFUyi2EMgscpQQt96MM=
Received: from mail-oa1-f72.google.com (mail-oa1-f72.google.com [209.85.160.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-61-VKXvjQutNF22u8NPFN1UcA-1; Wed, 15 Apr 2026 14:11:21 -0400
X-MC-Unique: VKXvjQutNF22u8NPFN1UcA-1
X-Mimecast-MFC-AGG-ID: VKXvjQutNF22u8NPFN1UcA_1776276680
Received: by mail-oa1-f72.google.com with SMTP id 586e51a60fabf-40ed781f705so10393479fac.0 for <tls@ietf.org>; Wed, 15 Apr 2026 11:11:21 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1776276680; x=1776881480; h=in-reply-to:from:content-language:references:to:subject:user-agent :mime-version:date:message-id:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=KaPiXaEVmQCXxm6/5lQyR4VbE2pHtdIzftPw2bk3Ffg=; b=spQey2vxYZN3udbPyTgRAaFRPatRZMVqmnqvCCBInd/UpgD72i7oaKiVXCP7ocCnG2 1IDtuHBTzaBvdGDHYAZilvtWVWWcy62m9RY9zSWAwPzeq8z9fVXgKR1zRNf/m5pfvZB4 gRAHY/4dUwPgnUKHPuQo++B/XOidvBqTtc3tiv43PkM0t/XSac9T4zKmbhUWMhYfrmTV rUaE+JUD6JImlp25oJtpHlBLqRjcV1oYMmCRwDsBrP2d54VnxAfqTtY8WeRjSuvuniEd /8I+P0SO/fAMpMEEfXQAHb6Y0z4kW+M0lOS4B+DlslWqma+e2wNpkLvF8BV/I4lrFuUX YGMA==
X-Gm-Message-State: AOJu0YzP4WH2nrXrtFSqpQHKxmLkYz87cvXlh74hYPjMvrfhERdyYeO2 yLmINy7fN63FwMMcMCEEI6fBJiCEIaHtpfLU6UET7Y/aa9IHjMIBhJZfkRUy3oL5wdKydX0R/EI j64CrgXvVHlhk1wRPbHXdPWbFy1mmk3QRWE/gf09rNleClvp1QMIVMffzCKYnNe8o478vx5KDNy sxBeP9IJU/g+BglH+MKp2He9sZKNU=
X-Gm-Gg: AeBDiesg+HfDLydpV9eK+/uA7rl9Wky3+sCGKJSCeRTFfr07vCFEeZAWXXjTXfh7b9Y 9gbwDgubE6JKzxkonRwIMUNN54fUFUHQ5J42a68U8iOlrSGSHExqE/wBS4MlW7tdR6ui9NMAbZX MvNeczlh3t5YGLml9YdIyi93RZRoMx1YGJ4lkRpAyf4CB16Nk3cHHIgDFkSdS4W9nPJ1qaJh7rb hxM6oaa5cCQa7aeQ9l9KRROmUuiEJIpY/irbKi2F8uyTTB1MFHlB9JzBuSjn85pOsjlNsIM+DM0 JjLS9ud8ZwCQai4UBmvLFM5DdJGD34EOD0x8gkOI4ReeWHfoDVXNr30CZXqcysFfVKbbhasPRXq YIPbdkajnc3NMnGjSPS7Vb67NxH+Zlsyvv7erOPAwZS9oKlQdZ3dyJIyMq1nwyoQUTiu7UA==
X-Received: by 2002:a05:6820:1389:b0:68a:a429:e564 with SMTP id 006d021491bc7-68be57782b4mr10832854eaf.9.1776276680329; Wed, 15 Apr 2026 11:11:20 -0700 (PDT)
X-Received: by 2002:a05:6820:1389:b0:68a:a429:e564 with SMTP id 006d021491bc7-68be57782b4mr10832834eaf.9.1776276679733; Wed, 15 Apr 2026 11:11:19 -0700 (PDT)
Received: from [192.168.1.172] (c-24-23-245-90.hsd1.ca.comcast.net. [24.23.245.90]) by smtp.gmail.com with ESMTPSA id 586e51a60fabf-42666b87009sm2093666fac.3.2026.04.15.11.11.18 for <tls@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 15 Apr 2026 11:11:19 -0700 (PDT)
Message-ID: <e29c13b2-8dd7-4e1e-a03d-a8788d1a6aff@redhat.com>
Date: Wed, 15 Apr 2026 11:11:18 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: tls@ietf.org
References: <16CF0FDA-7263-461A-9F2B-D37DBEAF5DD9@sn3rd.com> <AS4PR07MB8825B07414A64356A9F5848989582@AS4PR07MB8825.eurprd07.prod.outlook.com> <69dfbd7a.050a0220.42b04.eb0fSMTPIN_ADDED_BROKEN@mx.google.com> <CAMjbhoWJ4XvUt74QY-+JiE_LjGjHd-C4AkajrF8RNXKTPDQaaA@mail.gmail.com>
From: Robert Relyea <rrelyea@redhat.com>
In-Reply-To: <CAMjbhoWJ4XvUt74QY-+JiE_LjGjHd-C4AkajrF8RNXKTPDQaaA@mail.gmail.com>
X-Mimecast-Spam-Score: 0
X-Mimecast-MFC-PROC-ID: j6aQtdwGTCrieZxA9suQuxmUHZSxaAe7ljRkT9XqFUw_1776276680
X-Mimecast-Originator: redhat.com
Content-Type: multipart/alternative; boundary="------------Byav0w3HZv1MqCADrMkCPRnP"
Content-Language: en-US
Message-ID-Hash: K3XNTITF7WAD4QN7JWKINLZ4EYXZ6NAZ
X-Message-ID-Hash: K3XNTITF7WAD4QN7JWKINLZ4EYXZ6NAZ
X-MailFrom: rrelyea@redhat.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tls.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: Working Group Last Call for Use of ML-DSA in TLS 1.3
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/7NTlWPrO6-pHkZZwGbpLG1x_uVE>
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 4/15/26 10:11 AM, Bas Westerbaan wrote:
>
>     If amost all TLS cerificates live less than 2 or 3 years, or even
>     just months, it seems that the risk to use pure PQ certificates is
>     much less. This may be possible as ACME is getting popular now.
>
>
> In case you're worried about a weak algorithm, then it's not the 
> lifetime of the certificate that's important, but rather the lifetime 
> of the root certificate. Or rather: the ability to update the roots 
> that a client trusts. These considerations, of course, are not 
> specific to ML-DSA.

If you are worried about the 'lifetime' of the root, we are already in 
trouble because existing algorithms have root certs with very long 
lifetimes. The effective lifetimes of these roots are really tied to 
time it takes to effectively revoke them. In the use case of the web, 
the demonstrated revocation time is roughly multiple days to weeks. 
Other use cases may be able to revoke these certs as quickly (the root 
cert in your imbedded device with no firmware update, for instance - in 
that case it's effectively the lifetime of the device).

bob