Return-Path: 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 80534BAFD002 for ; Fri, 20 Feb 2026 17:38:50 -0800 (PST) X-Virus-Scanned: amavisd-new at ietf.org X-Spam-Flag: NO X-Spam-Score: -4.398 X-Spam-Level: X-Spam-Status: No, score=-4.398 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_DNSWL_MED=-2.3, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=dukhovni.org 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 ihEFcIVyDKOW for ; Fri, 20 Feb 2026 17:38:49 -0800 (PST) Received: from chardros.imrryr.org (chardros.imrryr.org [144.6.86.210]) (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 26B45BAFCFFD for ; Fri, 20 Feb 2026 17:38:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dukhovni.org; i=@dukhovni.org; q=dns/txt; s=f8320d6e; t=1771637925; h=date : from : to : subject : message-id : reply-to : references : mime-version : content-type : in-reply-to : content-transfer-encoding : from; bh=ae8Z8x577a8ZrIM8I/YGkr88U+sYqkFU34G+f0VSRZg=; b=YIzakvws1JiWeqXVDmu9jgu/gI67tLjmXGzlJ9bgnn+BfFCT/lRanETzREoJXkfCXs7wR HXcSWnmheWny2oo0cmOeQqjL+LTqS0vfSbgJ1vHkEe5vo2AgPJ0eH58fPMStjXg18Zn2hNk WWwujmOpeKr4pR8TarGNzFSSuX9zyn8= Received: by chardros.imrryr.org (Postfix, from userid 1000) id 5993B938E13; Sat, 21 Feb 2026 12:38:45 +1100 (AEDT) Date: Sat, 21 Feb 2026 12:38:45 +1100 From: Viktor Dukhovni To: tls@ietf.org Message-ID: References: <2caab265-00ba-4078-b6d0-3a178dabaa61@tu-dresden.de> <93af0689-4bd3-4f6b-afaf-41869d27fa4d@app.fastmail.com> <7e6727a1-c994-43df-a16b-078bd8995717@tu-dresden.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Mail-Followup-To: Content-Transfer-Encoding: quoted-printable Message-ID-Hash: KTZZQM6HN37PZCFQGDYNFNGKYPQFLTZB X-Message-ID-Hash: KTZZQM6HN37PZCFQGDYNFNGKYPQFLTZB X-MailFrom: ietf-dane@dukhovni.org 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 Reply-To: tls@ietf.org Subject: =?utf-8?q?=5BTLS=5D_Re=3A_WG_Last_Call=3A_draft-ietf-tls-mlkem-07_=28Ends_20?= =?utf-8?q?26-02-27=29?= List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: I support publication as a stable reference for the already allocated code point that sports multiple implementations. At least for OpenSSL, I don't expect publication to shift the needle from "implemented" to "enabled by default" (in clients and servers). The pure ML-KEM groups are not included in the default supported groups list and there are no plans to change that. For a pure ML-KEM group to be used as the source of the key agreement shared secret it needs to be explicitly enabled on **both** ends and preferred by whichever side's preference order is taken into account by the server. Meanwhile, the X25519MLKEM768 hybrid has been enabled by default for almost a year, and will surely continue to be far more common in practice. --=20 Viktor. =F0=9F=87=BA=F0=9F=87=A6 =D0=A1=D0=BB=D0=B0=D0=B2=D0=B0 =D0=A3= =D0=BA=D1=80=D0=B0=D1=97=D0=BD=D1=96!