[TLS] Re: Fwd: New Version Notification for draft-barnes-tls-this-could-have-been-an-email-00.txt

Toerless Eckert <tte@cs.fau.de> Wed, 25 February 2026 18:55 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
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 444A4BE1D51B for <tls@mail2.ietf.org>; Wed, 25 Feb 2026 10:55:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=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 (2048-bit key) header.d=cs.fau.de
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 Ine2QzjJ1WtK for <tls@mail2.ietf.org>; Wed, 25 Feb 2026 10:55:46 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:40]) (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 E9EF9BE1D508 for <tls@ietf.org>; Wed, 25 Feb 2026 10:55:45 -0800 (PST)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (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 faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4fLkLc46Qvz1RCDW; Wed, 25 Feb 2026 19:55:36 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.fau.de; s=r20250630-faui40; t=1772045738; 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=R9UNTofcr7tGpL/hlnp1WOCn7lPhG27d8Ai5A7V7Vec=; b=qSSmLcfIEn+/KZvSyyezB2pUiKbTYj0N+1A8l9zar9o6AMtizbgmTjIHjFmIkjloIcVegL zlxsdpredc2w0ImRopppBzpffQ2TNVpUD6g6NkQRbf4R651lKG07s0aWvlC75eM08rhKrF 4VOmcxr+5QYiMl9GYXyFf9PFtaPcvTIRRzsn70YJTmQ7jS4+CuhcxTn0aHJcHnNO95oYkP 9kemVHMim/6PHU5zCRO8EkCZz8uUaGBW/IbAy3CouG5xDhOFSQJ4ERPppaoola1gb/dYzU 5HABRvwSmVa3wqwPbPZV3jMgFT+o6146wWtBtbCwIhnxduE0lO0mF8eQZfhnJw==
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4fLkLc3VNWzl3B4; Wed, 25 Feb 2026 19:55:36 +0100 (CET)
Date: Wed, 25 Feb 2026 19:55:36 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: "Bellebaum, Thomas" <thomas.bellebaum@aisec.fraunhofer.de>
Message-ID: <aZ9FqNjpZa4yKwpG@faui48e.informatik.uni-erlangen.de>
References: <e48c1ea8667a71a71a483d51b4d4835fe9b88f4e.camel@aisec.fraunhofer.de> <579c10bc-6569-48e8-9c2a-ae70a1e3aee5@cs.tcd.ie> <aZ4Ihix3kTWRzhMe@faui48e.informatik.uni-erlangen.de> <aZ5hHiFM60zaboSU@chardros.imrryr.org> <CABcZeBOhA2W9NRzmDPQ=j6mxdSnxa4PcZqmcm6kMU6XzvjzKgQ@mail.gmail.com> <aZ6N2LsudVF3ZMLe@chardros.imrryr.org> <CAFR824yhx0cqnguP1+EL=jdcxCP5Bfj49wwevD7m69zU1yq6pA@mail.gmail.com> <4d95af906c2cb2c94847e8dbdc481e37815a2329.camel@aisec.fraunhofer.de> <CAFR824zTeWqD07vP-sMPdbZWj50wKjy=1UFXKTEeXUc1heTFQQ@mail.gmail.com> <112699ae39579c684cf4e35e2f54c6215d88d073.camel@aisec.fraunhofer.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <112699ae39579c684cf4e35e2f54c6215d88d073.camel@aisec.fraunhofer.de>
Message-ID-Hash: JEHBJMI365EBFH3X4SU5CV2MYTENY72G
X-Message-ID-Hash: JEHBJMI365EBFH3X4SU5CV2MYTENY72G
X-MailFrom: eckert@i4.informatik.uni-erlangen.de
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
CC: "tls@ietf.org" <tls@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [TLS] Re: Fwd: New Version Notification for draft-barnes-tls-this-could-have-been-an-email-00.txt
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/S0Dmgz5Lm7LL5MVMZDCe-p4nhOM>
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>

+1 for more explicit statements about the use case in which the cyphersuite is
deemed to be applicable and maybe even preferrable over the alternative.

But it would be good to keep the discussion about the cyphersuite draft constrained
to mail thread with it in the title. This thread here is about the meta thread
for another draft about what to do in TLS in general and not only this specific
case.

Cheers
    Toerless

On Wed, Feb 25, 2026 at 09:39:50AM +0000, Bellebaum, Thomas wrote:
> > I am happy to cut down the Motivations to 'nothing', I thought I was  
> > obligated to say 'something'
> 
> Saying 'nothing' in the draft is advocacy too, because it says something to publish an RFC in the first place.
> My main fear here is that people would start making up their own rationalizations for the existence of this RFC-to-be. After all, "the TLS WG would have published it for *some* reason", most likely because "it's just a good idea in general".
> 
> The point of saying something is to be explicit about what our motivations are; to advocate for its use only under certain conditions rather than broadly. Put plainly:
> 
> - If we think the only reason for deploying this is CNSA 2.0 and alike, we should say so.
> - If we think there are other good reasons with limited scope, we should say so.
> - If we think others are safer with hybrids, we should say so.
> 
> I believe this explicitness is the preferable way to limit advocacy, not saying less.
> 
> -- TBB
> 
> P.S. Of course, resolving these 'If's is the point of much discussion on this list.



-- 
---
tte@cs.fau.de